Release manager?

[Johan Oskarsson <jo...@oskarsson.nu>]

Hi all,

I was going to ask for the latest 0.1.0 release news, but will instead
suggest that the project should assign a primary release manager.

The release manager would be a committer that would spend some of his
time initiating the release process and make sure it doesn't stall. He
would organize votes and poke the right people/lists to make sure the
release it is taken through the necessary steps.

What do people think?

/Johan

Re: Release manager?

[Michael Greene <mi...@gmail.com>]

I think this sounds like a really good idea too.  We have code we want
to ship, let's find someone with the drive to put it out there so we
can start thinking about our second release :)

Michael

On Tue, Jul 21, 2009 at 9:36 AM, Bryan Duxbury<br...@rapleaf.com> wrote:
> I think this sounds like a great idea.
>
> On Jul 21, 2009, at 3:25 AM, Johan Oskarsson wrote:
>
>> Hi all,
>>
>> I was going to ask for the latest 0.1.0 release news, but will instead
>> suggest that the project should assign a primary release manager.
>>
>> The release manager would be a committer that would spend some of his
>> time initiating the release process and make sure it doesn't stall. He
>> would organize votes and poke the right people/lists to make sure the
>> release it is taken through the necessary steps.
>>
>> What do people think?
>>
>> /Johan
>
>

RE: Release manager?

[Upayavira <uv...@odoko.co.uk>]

On Tue, 2009-07-21 at 07:39 -0700, Chad Walters wrote:
> +1. David has been unofficially providing this role but I think he has
> been busier with other things. Anyone want to volunteer?
> 
> I think we have had a number of +1 votes on 0.1.0 RC2. Does anyone
> want to do an official tabulation of the votes and then declare the
> release? I am not 100% sure but I think all the other official Apache
> process requirements have been completed so that might actually be the
> last step we need before making the release official.

Once the project has voted to release (and that vote should be on a
source tarball), we need to put that release to the Incubator PMC (on
general@incubator.a.o). The first release is always a challenge, as
folks there take a good look over the release, and may make comments
that will require a further tarball to be produced.

Perhaps you could short-circuit some of this by preparing a tarball and
asking them what they'd make of it. Only vote when folks say it looks
good.

Second releases are usually much more straight-forward as the worst
issues have already been dealt with.

Upayavira

Re: Release manager?

[David Reiss <dr...@facebook.com>]

One thing I know we have to do is to check the status of all of our
software grants and ICLAs.  The one from Facebook does not cover
third-party contributions to Thrift.

--David

Chad Walters wrote:
> +1. David has been unofficially providing this role but I think he has been busier with other things. Anyone want to volunteer?
> 
> I think we have had a number of +1 votes on 0.1.0 RC2. Does anyone want to do an official tabulation of the votes and then declare the release? I am not 100% sure but I think all the other official Apache process requirements have been completed so that might actually be the last step we need before making the release official.
> 
> Chad
> ________________________________________
> From: Bryan Duxbury [bryan@rapleaf.com]
> Sent: Tuesday, July 21, 2009 7:36 AM
> To: thrift-dev@incubator.apache.org
> Subject: Re: Release manager?
> 
> I think this sounds like a great idea.
> 
> On Jul 21, 2009, at 3:25 AM, Johan Oskarsson wrote:
> 
>> Hi all,
>>
>> I was going to ask for the latest 0.1.0 release news, but will instead
>> suggest that the project should assign a primary release manager.
>>
>> The release manager would be a committer that would spend some of his
>> time initiating the release process and make sure it doesn't stall. He
>> would organize votes and poke the right people/lists to make sure the
>> release it is taken through the necessary steps.
>>
>> What do people think?
>>
>> /Johan
> 

RE: Release manager?

[Chad Walters <Ch...@microsoft.com>]

+1. David has been unofficially providing this role but I think he has been busier with other things. Anyone want to volunteer?

I think we have had a number of +1 votes on 0.1.0 RC2. Does anyone want to do an official tabulation of the votes and then declare the release? I am not 100% sure but I think all the other official Apache process requirements have been completed so that might actually be the last step we need before making the release official.

Chad
________________________________________
From: Bryan Duxbury [bryan@rapleaf.com]
Sent: Tuesday, July 21, 2009 7:36 AM
To: thrift-dev@incubator.apache.org
Subject: Re: Release manager?

I think this sounds like a great idea.

On Jul 21, 2009, at 3:25 AM, Johan Oskarsson wrote:

> Hi all,
>
> I was going to ask for the latest 0.1.0 release news, but will instead
> suggest that the project should assign a primary release manager.
>
> The release manager would be a committer that would spend some of his
> time initiating the release process and make sure it doesn't stall. He
> would organize votes and poke the right people/lists to make sure the
> release it is taken through the necessary steps.
>
> What do people think?
>
> /Johan

Re: Release manager?

[Bryan Duxbury <br...@rapleaf.com>]

I think this sounds like a great idea.

On Jul 21, 2009, at 3:25 AM, Johan Oskarsson wrote:

> Hi all,
>
> I was going to ask for the latest 0.1.0 release news, but will instead
> suggest that the project should assign a primary release manager.
>
> The release manager would be a committer that would spend some of his
> time initiating the release process and make sure it doesn't stall. He
> would organize votes and poke the right people/lists to make sure the
> release it is taken through the necessary steps.
>
> What do people think?
>
> /Johan