public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Adam Dinwoodie <adam@dinwoodie.org>
To: cygwin-apps@cygwin.com
Subject: Uploading packages built against Perl 5.2.2 [Was: [ITA] Perl distributions (in preparation of Perl 5.22)]
Date: Mon, 27 Jul 2015 22:43:00 -0000	[thread overview]
Message-ID: <20150727224314.GL14466@dinwoodie.org> (raw)
In-Reply-To: <87bnfr3zwe.fsf@Rainer.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
> testers.

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
release.

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.

  parent reply	other threads:[~2015-07-27 22:43 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-25 10:03 [ITA] Perl distributions (in preparation of Perl 5.22) Achim Gratz
2015-05-25 15:24 ` Achim Gratz
2015-05-29 19:26 ` Achim Gratz
2015-05-29 19:44   ` Yaakov Selkowitz
2015-05-29 19:46     ` Yaakov Selkowitz
2015-05-29 19:57       ` Achim Gratz
2015-05-29 20:43         ` Yaakov Selkowitz
2015-05-29 20:55           ` Achim Gratz
2015-05-29 19:50     ` Achim Gratz
2015-05-31 16:00   ` Marco Atzeri
2015-05-31 18:59     ` Achim Gratz
2015-06-22 16:59 ` Achim Gratz
2015-06-22 21:46   ` Marco Atzeri
2015-06-23  5:38     ` Achim Gratz
2015-07-02 21:13     ` Marco Atzeri
2015-07-03  5:36       ` Achim Gratz
2015-06-26 23:09   ` Yaakov Selkowitz
2015-06-30  3:05     ` Yaakov Selkowitz
2015-06-30  5:04       ` Achim Gratz
2015-07-04 10:46       ` Achim Gratz
2015-07-04 12:31         ` Marco Atzeri
2015-07-04 19:34         ` David Rothenberger
2015-07-05  6:02           ` Achim Gratz
2015-07-05 13:26             ` Ken Brown
2015-07-05 18:32               ` Yaakov Selkowitz
2015-07-05 19:44                 ` Achim Gratz
2015-07-05 20:01                 ` Ken Brown
2015-07-27 22:43             ` Adam Dinwoodie [this message]
2015-07-28  5:43               ` Uploading packages built against Perl 5.2.2 [ Achim Gratz
2015-07-28  6:40                 ` Marco Atzeri
2015-07-28 11:18                   ` Corinna Vinschen
2015-07-28 16:18                     ` Achim Gratz
2015-07-28 16:36                       ` Corinna Vinschen
2015-07-28 17:06                       ` David Rothenberger
2015-07-28 17:20                         ` Achim Gratz
2015-07-28 16:23                     ` Eric Blake
2015-07-28 16:36                       ` Ken Brown
2015-07-28 16:40                         ` Corinna Vinschen
2015-07-28 17:31                           ` Ken Brown
2015-07-28 16:37                       ` Corinna Vinschen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150727224314.GL14466@dinwoodie.org \
    --to=adam@dinwoodie.org \
    --cc=cygwin-apps@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).