Corinna Vinschen writes:
Or Eric. I'm not sure how this !perl thingy is supposed to work since
the tags are handled by upset...
The idea was that when every maintainer has said he's ready, someone
goes into the server just after the updater has run and moves all !perl
to !ready, so that an
On Jul 28 08:40, Marco Atzeri wrote:
On 7/28/2015 7:43 AM, Achim Gratz wrote:
Adam Dinwoodie writes:
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
On Jul 28 18:17, Achim Gratz wrote:
Corinna Vinschen writes:
Or Eric. I'm not sure how this !perl thingy is supposed to work since
the tags are handled by upset...
The idea was that when every maintainer has said he's ready, someone
goes into the server just after the updater has run and
David Rothenberger writes:
I've already built and uploaded new subversion packages. I will rebuild
net-snmp by Sunday at the latest. I can easily put a !perl file in the
top-level release directories if that's the decision. I will ensure that
there are no other packages in the release areas
On Jul 28 12:36, Ken Brown wrote:
On 7/28/2015 12:23 PM, Eric Blake wrote:
On 07/28/2015 05:18 AM, Corinna Vinschen wrote:
One more thing that we'll have to solve one way or the other. I still
hope that one maintainer with full sourceware access will be able to
post the !ready cookies all at
On 7/28/2015 12:40 PM, Corinna Vinschen wrote:
On Jul 28 12:36, Ken Brown wrote:
On 7/28/2015 12:23 PM, Eric Blake wrote:
On 07/28/2015 05:18 AM, Corinna Vinschen wrote:
One more thing that we'll have to solve one way or the other. I still
hope that one maintainer with full sourceware access
On 7/28/2015 12:23 PM, Eric Blake wrote:
On 07/28/2015 05:18 AM, Corinna Vinschen wrote:
One more thing that we'll have to solve one way or the other. I still
hope that one maintainer with full sourceware access will be able to
post the !ready cookies all at the same time.
Corinna or Yaakov,
On Jul 28 10:23, Eric Blake wrote:
On 07/28/2015 05:18 AM, Corinna Vinschen wrote:
One more thing that we'll have to solve one way or the other. I still
hope that one maintainer with full sourceware access will be able to
post the !ready cookies all at the same time.
Corinna or Yaakov,
Achim Gratz wrote:
That would give two more days for maintainers to upload, which would be
OK. The only difference would be that every maintainer needs to ensure
that posting the cookies in the top-level release directories is OK. At
the moment we're stuck anyway as long as David and Yaakov
On 07/28/2015 05:18 AM, Corinna Vinschen wrote:
One more thing that we'll have to solve one way or the other. I still
hope that one maintainer with full sourceware access will be able to
post the !ready cookies all at the same time.
Corinna or Yaakov, that I am aware.
Or Eric. I'm not
On 7/28/2015 7:43 AM, Achim Gratz wrote:
Adam Dinwoodie writes:
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.
Adam Dinwoodie writes:
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.
Unfortunately, none of the folks with full access to
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
13 matches
Mail list logo
