avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Doug Cutting <cutt...@apache.org>
Subject Re: Avro release cadence
Date Thu, 26 Jun 2014 20:58:14 GMT
On Thu, Jun 26, 2014 at 8:59 AM, Sean Busbey <busbey@cloudera.com> wrote:
> How much of this work can a non-committer take on?

If you take on much of it you'll likely be made a committer!

Someone needs to follow up on all the "Patch Available" in Jira to
decide if they're ready to be committed.  Comments like, "+1 This
works for me, has tests, conforms to style, and all-in-all looks it
would make an improvement to the project", or "This can't be committed
as is because..." go a long ways towards getting issues resolved.
Even better is to post a version of the patch that can be committed.

Someone needs to test all the projects, running './build.sh clean test
dist' from the top-level.  This often fails due to, e.g., problems in
licensing that have crept in that are identified by RAT.

Once all that's established then actually creating the release
candidate and calling the vote is pretty easy.  This is best done by a
committer, since it involves creating SVN tags, updates to the CHANGES
file, etc.


View raw message