Hey Krishnan and Ismaël! Thanks for bumping this -- I've been looking through JIRA, git and pull requests to see what we need to do.
The doc that Ismaël mentions is an OK how-to, but it's still a bit rough in places. It goes from the assumption that we already have a branch ready, or a good idea of all the commits that need to be added to it. What actually needs to be done is a bit subjective. There's not really a list of prerequisites before creating a branch, but this is what I've been doing: 1) Go through all the commits on master that aren't on the branch and see if there are any bug-fixes or important dependency version bumps that should be cherry-picked. As an example, https://github.com/apache/avro/commit/4a298ad6dce730c4f323b9c739b810ac06d4ec3b makes some changes in the build image that are probably necessary for 1.10. 2) Go through all of the resolved JIRA for 1.10.1 and make sure they're on the branch. As an example, https://issues.apache.org/jira/browse/AVRO-2891 was merged to master and marked as fixed in 1.10.1 (but it hasn't been cherry-picked). 3) Go through the unresolved JIRA for 1.10.1 and see if they can be either fixed now, or moved to a later version. For example, https://issues.apache.org/jira/browse/AVRO-2945 probably should be done and is an easy doc fix. 4) Go through all unresolved JIRA without a fix version and see if any Critical or Blocker bugs are actually critical or block the release. 5) Go through the open PR, review and merge the bug fixes that are in a good state. This is pretty important for the community -- if we can't review them fast, we can at least review them for the release! I probably missed a couple of useful steps, don't hesitate to speak up -- I wouldn't mind adding them to the release guide! Krishnan, if you would like to help out, that would be fine by me! I would have been better off following someone else for the first time. I'm almost always available on the ASF slack (http://s.apache.org/slack-invite) at UTC+1 work hours. All my best, Ryan On Wed, Nov 4, 2020 at 2:51 PM Ismaël Mejía <ieme...@gmail.com> wrote: > Krishnan You can take a look at > https://cwiki.apache.org/confluence/display/AVRO/How+To+Release For steps > that > could help to reproduce the build. > > A really important contribution is to try to update in any of the projects > where > you use Avro to use the latest version (the one being voted) and report if > any > potential issue or regression. If you use Avro in a Java project with > maven you > can do this by adding the URL that corresponds to the artifacts being > voted. > > <repository> > <id>avro-release-repo</id> > <name>Avro Release Repo</name> > <url> > https://repository.apache.org/content/repositories/orgapacheavro-1142/ > </url> > </repository> > > On Tue, Nov 3, 2020 at 7:01 PM Krishnan Sundaram <krishnan1...@gmail.com> > wrote: > > > > Hi all, > > > > Is there a documented process for creating a new release? Something which > > lists the steps involved including prerequisites, quality gates, etc. > which > > would help volunteers? > > > > Thanks, > > Krishnan > > > > On Wed, Oct 14, 2020 at 2:16 AM Ryan Skraba <r...@skraba.com> wrote: > > > > > Hello, great timing! > > > > > > I'd definitely like to see a new release. A minor 1.10.1 bug fix > release > > > would probably be reassuring -- it looks like the idea of bumping the > Avro > > > version in some downstream projects is getting a bit more traction. I > > > don't have any strong opinion yet whether 1.11.0 is ready or necessary. > > > > > > I just set AVRO-2817 to 1.10.1 since it breaks a Hive unit test. > There's a > > > couple of other unresolved bugs to go through for 1.10.1, and it would > be > > > great (as always) to catch up on any PRs that just need a bit of > attention. > > > > > > I had the pleasure of working with the 1.9.2 release :D I'd be > pleased to > > > either volunteer for 1.10.1 or to help out if anyone else wants to > give it > > > a try! > > > > > > All my best, Ryan > > > > > > > > > > > > > > > On Wed, Oct 14, 2020 at 8:08 AM Sean Busbey <bus...@apache.org> wrote: > > > > > > > Hi folks! > > > > > > > > It's been a while since our last release. We've had some nice stuff > > > > land and we should get those contributions into releases so they are > > > > more widely available. > > > > > > > > Is there anything that I should consider a blocker on a 1.10.1 minor > > > > release off of branch-1.10? > > > > > > > > How about our next major release for 1.11.0? Is all the python 2 > > > > removal clean up in place now? > > > > > > > > Any volunteers available to lead things through our release process > > > > for either of these? > > > > > > > > -busbey > > > > > > > >
