Hi Nandor, Others, I appreciate the patience. My day job is taking more time of my day these days. There is a lot the community can do. One thing that will help any release manager is checking if any Jira needs to be on branch-1.7. If there are any patches missing, then please let the release manager know prior to the branching since that helps a lot. You can also look at the jira to see if anything has been missed. There is a wiki on how to release[1]. The wiki talks on how to release mainly. But one can test the code by doing the verification on the steps. If you have any questions, please feel free to reach out to me.
[1]:https://cwiki.apache.org/confluence/display/AVRO/How+To+Release -Suraj Acharya On Wed, Oct 18, 2017 at 12:38 AM, Nandor Kollar <[email protected]> wrote: > Hi Suraj, > > Though I'm not a committer, I'd be happy to help you with the release > (verification, or anything else you need help with, and I can also do it)! > By the way, is there a wiki about the steps required for an Avro release? > > Thanks, > Nandor > > On Fri, Oct 13, 2017 at 3:00 AM, Suraj Acharya <[email protected]> wrote: > > > Hi, > > > > I have done the cleanup of all the requirements needed for the release of > > Apache Avro-1.7.8[1]. > > The 1.7 branch is building. > > All the required cherry-picks are in the branch-1.7. > > Does anyone want to be a release manager? A minimum requirement is you > need > > to be a committer to the project. > > > > If no one is interested in it, I will work on it this week and try to > get a > > release going in the next week. Just wanted to see if anyone is > interested. > > Thanks a lot for the patience with this release. > > > > [1]: https://issues.apache.org/jira/browse/AVRO-1998 > > > > If you have any questions feel free to reach out to me. > > > > Thanks > > Suraj Acharya > > >
