From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-apps@cygwin.com
Cc: Achim Gratz <Stromeko@nexgo.de>
Subject: Re: [Attn. Maintainers] Perl 5.26.1
Date: Fri, 29 Sep 2017 18:26:00 -0000 [thread overview]
Message-ID: <f33fa5df-5e6d-5582-d174-5e24120f6275@dronecode.org.uk> (raw)
In-Reply-To: <874lrs6mg8.fsf@Rainer.invalid>
On 24/09/2017 18:22, Achim Gratz wrote:
> Ken Brown writes:
>> On 9/24/2017 11:59 AM, Achim Gratz wrote:
>>> Please build and prepare packages meant for release to Cygwin with this
>>> Perl version, but preferrably do no yet actually upload.
>>
>> Have you decided yet how you want to handle the upgrade when the time
>> comes? I think last time you asked people to upload a !perl file
>> instead of !ready, and then you coordinated with Jon to change all the
>> !perl files to !ready at the appropriate time.
>
> The mechanisms on sourceware have substantially changed since then, so I
> don't know what's the appropriate solution this time around. One
> possibility could be to simply stop the calm updates until everybody
> gives their go and then resume it so it picks up everything in one go.
> But again, Jon or Yaakov probably have a better idea.
Doing the same thing again should be fine.
next prev parent reply other threads:[~2017-09-29 18:26 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-17 20:05 [Attn. Maintainers] Perl 5.26.1-RC1 Achim Gratz
2017-09-18 17:18 ` Ken Brown
2017-09-18 18:00 ` Achim Gratz
2017-09-18 20:00 ` Ken Brown
2017-09-25 21:21 ` Yaakov Selkowitz
2017-09-26 8:23 ` Ken Brown
2017-09-18 17:52 ` Achim Gratz
2017-09-19 6:11 ` Yaakov Selkowitz
2017-09-19 17:35 ` Achim Gratz
2017-09-24 9:09 ` Marco Atzeri
2017-09-24 9:25 ` Achim Gratz
2017-09-24 17:24 ` Marco Atzeri
2017-09-29 20:48 ` Marco Atzeri
2017-09-30 8:15 ` Achim Gratz
2017-09-24 15:59 ` [Attn. Maintainers] Perl 5.26.1 Achim Gratz
2017-09-24 17:16 ` Ken Brown
2017-09-24 17:22 ` Achim Gratz
2017-09-29 18:26 ` Jon Turney [this message]
2017-09-26 16:45 ` Achim Gratz
2017-09-29 18:06 ` Yaakov Selkowitz
2017-09-30 8:52 ` Achim Gratz
2017-09-30 15:25 ` Ken Brown
2017-10-02 20:39 ` Achim Gratz
2017-10-02 21:20 ` Ken Brown
2017-10-03 2:36 ` Brian Inglis
2017-10-03 6:35 ` Achim Gratz
2017-09-30 21:13 ` Marco Atzeri
2017-10-01 4:47 ` Marco Atzeri
2017-10-02 20:41 ` Achim Gratz
2017-09-30 22:49 ` Alexey Sokolov
2017-10-01 8:13 ` Achim Gratz
2017-10-09 16:41 ` Ken Brown
2017-09-26 16:50 ` Achim Gratz
2017-09-26 18:56 ` Achim Gratz
2017-09-26 20:42 ` Achim Gratz
2017-09-26 22:15 ` Yaakov Selkowitz
2017-09-27 4:51 ` Achim Gratz
2017-09-27 6:46 ` [Attn. Maintainers] Perl 5.26.1 (prepare for release) Achim Gratz
2017-09-30 20:30 ` Marco Atzeri
2017-10-04 17:24 ` Achim Gratz
2017-10-12 19:32 ` Achim Gratz
2017-10-12 20:34 ` Ken Brown
2017-10-13 18:02 ` Achim Gratz
2017-10-18 18:20 ` [Attn. Maintainers] Perl 5.26.1 (release is imminent) Achim Gratz
2017-10-18 20:21 ` Ken Brown
2017-10-18 22:16 ` David Rothenberger
2017-10-23 17:17 ` Yaakov Selkowitz
2017-10-23 17:38 ` Jon Turney
2017-10-23 18:03 ` Ken Brown
2017-10-23 18:37 ` Jon Turney
2017-10-19 6:04 ` Marco Atzeri
2017-10-19 15:00 ` Yaakov Selkowitz
2017-10-19 17:15 ` Achim Gratz
2017-10-23 17:47 ` Yaakov Selkowitz
2017-10-24 8:37 ` Adam Dinwoodie
2017-10-23 19:20 ` Achim Gratz
2017-10-24 16:22 ` Ken Brown
2017-10-24 18:45 ` Achim Gratz
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=f33fa5df-5e6d-5582-d174-5e24120f6275@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=Stromeko@nexgo.de \
--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).