I feel this can be public so allow me to reply this to the dev list. Before reading my reply. [1] is a good official answer.
Below is my supplement. In general, release manager do the following things: 1. Define the scope What feature/bugs need to be included/fixed in the specific release and what don't. Typically anything is still working under the apache way. So community consensus over any others. The release process is facilitated via JIRA. The umbrella ticket BIGTOP-2945 is what we need to maintained. For those issues required to be fixed in 1.3. You can specifically link it as blocker of BIGTOP-2945. For those bugs that block the release, you can highlight them and ask community to provide support. 2. Drive things forward and meet the schedule Just like typical project execution, RM needs to make sure a release has good quality and is released on time. From time to time, RM also needs to identify blockers, redefine the scope, compromise to reality and do trade-offs. 3. Produce release binaries This includes source code release, bigtop testing util jars, and binary convenient artifacts. The source code release is the major part which comply with Apache policy. In addition to make user's life easier, we'll publish jars and artifacts. We have a comprehensive release guide for this with scripts ready[2]. And most importantly, it's the community to work on a release together. So ask for help when in doubt; ask for help if needed. We're around. Folks please help me to add more items if I missed something. This can be converted into a doc later. [1] http://www.apache.org/dev/release-publishing.html [2] https://cwiki.apache.org/confluence/display/BIGTOP/How+to+release Evans Jun HE <[email protected]> 於 2018年8月3日 週五 下午3:26寫道： > Hi, Evans, > > Thank you very much to name me as the 1.3 RM. > Not sure if this requires PMC approvement. Assume PMC agrees with this, > could you pls let me know what the process is the to make a release and > what responsibily RM should take? > Consider the target date is before ApacheCon, I may need to work out a > plan asap. > > Again thanks for your trust and kind support! :) > > Regards, > > Jun >
