This is the mail archive of the
mailing list for the Cygwin project.
Uploading packages built against Perl 5.2.2 [Was: [ITA] Perl distributions (in preparation of Perl 5.22)]
- From: Adam Dinwoodie <adam at dinwoodie dot org>
- To: cygwin-apps at cygwin dot com
- Date: Mon, 27 Jul 2015 23:43:14 +0100
- Subject: Uploading packages built against Perl 5.2.2 [Was: [ITA] Perl distributions (in preparation of Perl 5.22)]
- Authentication-results: sourceware.org; auth=none
- References: <87a8wt3rg0 dot fsf at Rainer dot invalid> <87mvzrfzlp dot fsf at Rainer dot invalid> <1435360174 dot 11720 dot 34 dot camel at cygwin dot com> <1435633541 dot 5276 dot 7 dot camel at cygwin dot com> <87pp488aki dot fsf at Rainer dot invalid> <5598352D dot 8030603 at acm dot org> <87bnfr3zwe dot fsf at Rainer dot invalid>
On Sun, Jul 05, 2015 at 08:02:41AM +0200, Achim Gratz wrote:
> David Rothenberger writes:
> > I've rebuilt the package as curr and not test and uploaded to my area. I
> > did not create the !ready file.
> > Is this the right way to do this? Or should I release a test package?
> As long as you remember what you did it's going to be OK. A test
> package might only be needed if someone else asks for it or you need
Is there a consensus on the way to upload files ready for Perl 5.22 to
be made available? The Git packages are ready to go, but I'm not sure
if I should be uploading them without a !ready file, or as a test
Or is the idea just that we're going to try to coordinate the many
maintainers worldwide to all release at the same time on Friday? As
that'll mean it doesn't matter that there's no consensus, it just seems
like it'll also be inordinately painful, too.