You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Stefan Sperling <st...@elego.de> on 2012/05/05 12:48:23 UTC

Re: We need a new 1.7.5 release manager (was: Re: 1.7.5 in one/two weeks?)

On Wed, Apr 25, 2012 at 11:50:16AM +0200, Stefan Sperling wrote:
> On Wed, Apr 25, 2012 at 11:49:53AM +0300, Daniel Shahaf wrote:
> > I don't know when we're cutting 1.7.5, but I'm stepping down from the RM
> > hot seat.  (I can no longer commit to having the time for that.)
> 
> Will anyone else step up to run the 1.7.5 release?
> 
> Please help enlarge the RM ecosystem! The RM is currently rated as
> "Critically Endangered" species by IUCN.

So we really have nobody who is even remotely interested in volunteering
for this task? In that case, I would step in and try to roll a release
during the next 2 weeks. However, I'd strongly prefer having additional
release managers. It is not hard and doesn't take much time. The major
effort is reading related documentation in HACKING and learning how
to drive the release.py script.

Re: We need a new 1.7.5 release manager (was: Re: 1.7.5 in one/two weeks?)

Posted by Stephen Butler <sb...@elego.de>.
On May 7, 2012, at 1:26 , Stefan Sperling wrote:

> On Sun, May 06, 2012 at 10:34:53PM +0200, Stephen Butler wrote:
>> OK, I'll volunteer.  ATM I'm still learning what release.py does, but I'll try
>> to get up to speed this week.
>> 
>> Steve
> 
> Thanks! But Philip already volunteered to run 1.7.5. You could run 1.7.6 :)

Sounds good!

Re: We need a new 1.7.5 release manager (was: Re: 1.7.5 in one/two weeks?)

Posted by Stefan Sperling <st...@elego.de>.
On Sun, May 06, 2012 at 10:34:53PM +0200, Stephen Butler wrote:
> OK, I'll volunteer.  ATM I'm still learning what release.py does, but I'll try
> to get up to speed this week.
> 
> Steve

Thanks! But Philip already volunteered to run 1.7.5. You could run 1.7.6 :)

Re: We need a new 1.7.5 release manager (was: Re: 1.7.5 in one/two weeks?)

Posted by Stephen Butler <sb...@elego.de>.
On May 5, 2012, at 12:48 , Stefan Sperling wrote:

> On Wed, Apr 25, 2012 at 11:50:16AM +0200, Stefan Sperling wrote:
>> On Wed, Apr 25, 2012 at 11:49:53AM +0300, Daniel Shahaf wrote:
>>> I don't know when we're cutting 1.7.5, but I'm stepping down from the RM
>>> hot seat.  (I can no longer commit to having the time for that.)
>> 
>> Will anyone else step up to run the 1.7.5 release?
>> 
>> Please help enlarge the RM ecosystem! The RM is currently rated as
>> "Critically Endangered" species by IUCN.
> 
> So we really have nobody who is even remotely interested in volunteering
> for this task? In that case, I would step in and try to roll a release
> during the next 2 weeks. However, I'd strongly prefer having additional
> release managers. It is not hard and doesn't take much time. The major
> effort is reading related documentation in HACKING and learning how
> to drive the release.py script.


OK, I'll volunteer.  ATM I'm still learning what release.py does, but I'll try
to get up to speed this week.

Steve

Re: 1.7.5 next week

Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Stefan Sperling wrote on Sat, May 05, 2012 at 13:46:12 +0200:
> On Sat, May 05, 2012 at 12:29:25PM +0100, Philip Martin wrote:
> > Yes, I'll do it.  I'll roll a 1.7.5 some time next week.
>  
> Thanks so much Philip!

+1

Re: 1.7.5 next week

Posted by Stefan Sperling <st...@elego.de>.
On Sat, May 05, 2012 at 12:29:25PM +0100, Philip Martin wrote:
> Yes, I'll do it.  I'll roll a 1.7.5 some time next week.
 
Thanks so much Philip!

1.7.5 next week

Posted by Philip Martin <ph...@wandisco.com>.
Stefan Sperling <st...@elego.de> writes:

> On Wed, Apr 25, 2012 at 11:50:16AM +0200, Stefan Sperling wrote:
>> On Wed, Apr 25, 2012 at 11:49:53AM +0300, Daniel Shahaf wrote:
>> > I don't know when we're cutting 1.7.5, but I'm stepping down from the RM
>> > hot seat.  (I can no longer commit to having the time for that.)
>> 
>> Will anyone else step up to run the 1.7.5 release?
>> 
>> Please help enlarge the RM ecosystem! The RM is currently rated as
>> "Critically Endangered" species by IUCN.
>
> So we really have nobody who is even remotely interested in volunteering
> for this task? In that case, I would step in and try to roll a release
> during the next 2 weeks. However, I'd strongly prefer having additional
> release managers. It is not hard and doesn't take much time. The major
> effort is reading related documentation in HACKING and learning how
> to drive the release.py script.

Yes, I'll do it.  I'll roll a 1.7.5 some time next week.

-- 
uberSVN: Apache Subversion Made Easy
http://www.uberSVN.com