+1 from me too. Big thanks to Bryan for volunteering.

-Todd

On Tue, Apr 27, 2010 at 2:51 PM, Joe Schaefer <joe_schae...@yahoo.com>wrote:

> Great idea, +1!
>
>
>
> ----- Original Message ----
> > From: Mark Slee <ms...@facebook.com>
> > To: "thrift-dev@incubator.apache.org" <thrift-dev@incubator.apache.org>
> > Sent: Tue, April 27, 2010 5:49:32 PM
> > Subject: Thrift Release Process
> >
> > Hi all,
>
> Wanted to start a quick discussion around Thrift's release
> > process. We have a consistent amount of general activity on the JIRA and
> in
> > commits, but we don't yet have a consistent release process. This is the
> biggest
> > issue keeping Thrift from graduating from the Incubator and becoming a
> > full-fledged Apache project.
>
> My sense is that most of Thrift's dev
> > community doesn't personally mind working against trunk or out of
> git-branches,
> > etc. Our lack of releases seems to be more a result of prioritization
> than
> > philosophy. After a bit of discussion amongst the project committee, an
> idea
> > that came up was to nominate a release manager who can be officially in
> charge
> > of driving regular releases.  The rest of us just need to commit to
> > supporting that role by being responsive and willing to tolerate the
> occasional
> > extra task around release time. In the steady-state it sounds like we'd
> like to
> > do quarterly releases. In the short-term, we might like to release more
> > frequently (monthly or bimonthly) to demonstrate that we can both execute
> and
> > maintain this process.
>
> Bryan Duxbury has volunteered for the release
> > manager role. Given his solid work and help getting our initial releases
> done I
> > think this is an ideal fit.
>
> Before we commit to this plan, wanted to
> > solicit feedback from the dev list. Are folks on board with this idea?
> Any
> > alternate ideas? I'm assuming this is pretty non-controversial and we
> won't need
> > to do a formal vote, but would love to get any feedback on
> > this.
>
> Cheers,
> Mark
>
>
>
>


-- 
Todd Lipcon
Software Engineer, Cloudera

Reply via email to