Anyone else have favorite issues they'd like to get in before I cut a release? If not, I try to get started with the release process Friday.
On Fri, Apr 9, 2010 at 9:59 AM, Bryan Duxbury <br...@rapleaf.com> wrote: > Yeah, this sounds like a good time to pull the trigger. > > Can everyone go through JIRA and decide what, if any, issues *must* be > fixed before we push out 0.3? There are lots of issues tagged as fix for > 0.3. > > > On Fri, Apr 9, 2010 at 9:13 AM, Todd Lipcon <t...@cloudera.com> wrote: > >> It would actually be an 0.3.0 - we skipped 0.1.0 due to an aborted release >> last year. >> >> Bryan, any interest in leading this up? I think you've contributed a >> number >> of Java fixes in the last few weeks. >> >> I'm happy to review an rc, but don't have bandwidth to be release manager >> again. >> >> -Todd >> >> On Fri, Apr 9, 2010 at 9:11 AM, Joe Schaefer <joe_schae...@yahoo.com> >> wrote: >> >> > A few months have passed since thrift's first >> > release, and since the project is only at 0.1.0 >> > it would be good to expose more of the latest >> > developments to end users. >> > >> > Any reasons why thrift shouldn't cut a new release >> > in April? >> > >> > >> > >> > >> >> >> -- >> Todd Lipcon >> Software Engineer, Cloudera >> > >
