I would say the most important thing would be to get the legal parts in a good state.
For guide, I would start with : - http://www.apache.org/dev/#releases For actual steps, here is what I have used in other projects (which include building, staging, signing, etc): https://github.com/apache/bahir/blob/master/dev/release-build.sh On Tue, Mar 13, 2018 at 11:21 AM, bernard metzler <bmetz...@gmx.ch> wrote: > Dear Mentors, > > Looks like we are getting close to a point where we think the code > base is good for a first release. I just searched around a little > to see what is needed from an administrative point of view. What > I found is an overwhelming amount of information, starting > at https://incubator.apache.org/guides/releasemanagement.html > > So, what I understand is, we have to follow some formal policies > applicable to all ASF project releases > (http://www.apache.org/legal/release-policy.html) plus setting up > the code base in a staged area (which would be > https://dist.apache.org/repos/dist/dev/incubator/crail/ - which > does not yet exist?), and finally go through a PMC voting procedure, > as described at > https://incubator.apache.org/guides/releasemanagement.html > > > Is there anything else I am missing? > > Thank you! > Bernard. > -- Luciano Resende http://twitter.com/lresende1975 http://lresende.blogspot.com/
