No need to be embarrassed, there is a wide variety of docs but that's partially because things tend to vary by community and most of those docs aren't authoritative.
There are a few things the ASF requires, some of which might be flexible while you're in the incubator (largely depending on your mentors and the IPMC): * Source artifact must exist * Source artifact must correspond to some version control commit * All artifact must adhere to LICENSE/NOTICE policies * All artifacts must be signed and have checksums (atleast md5, preferably also sha*) * [VOTE] thread must be called on dev@ with pointers to the above and a period of >= 72hrs Since you're incubating, after you have the above you then need a [VOTE] by the IPMC, which is done on general@incubator. Some pointers that might help: * The Incubator guide to releasing while incubating: http://incubator.apache.org/guides/releasemanagement.html * I recently wrote a draft release guide for Apache Yetus that covers what tools you'll need and the process step-by-step: https://issues.apache.org/jira/browse/YETUS-226 There are some differences; namely Yetus is a TLP so it has its own staging and release areas and doesn't need an IPMC vote. Most importantly, it includes pointers to ASF guides on generating and publishing GPG keys. If it doesn't give enough guidance I'd be interested in feedback. On Tue, Feb 23, 2016 at 9:01 PM, Puja Valiyil <puja...@gmail.com> wrote: > David and I tried to compile a process for creating a release -- we didn't > get that far. The main thing blocking us at this point is the whole > process for signing a release, no one we knew had a public key and then > David and I got lost/confused when trying to generate and register one. > All of this sounds borderline embarrassing since there is a lot of > documentation out there but we didn't have time to fully digest it in > time. > I'm also not clear on what else we would need to do besides run mvn > release, like compile release notes, etc. I'm sorry if there's a lot of > documentation exactly detailing what we need to do. > Other than that, I think we've made a lot of progress as a community this > past month. We've had a lot of new contributors, had a lot of new bugs > reported by new end users, and have closed out a lot of issues. > > On Tue, Feb 23, 2016 at 3:18 PM, Sean Busbey <bus...@apache.org> wrote: > >> Heya Rya! >> >> We're about 5-6 weeks from our next scheduled turn for the IPMC's board >> report. >> >> How are folks doing? The project sounds a bit quiet to me, but I'm not >> sure how much of that is me being sure to look in the right places. >> >> To Review, here are your self-identified three most important objectives: >> >> 1. Populate the website for the project >> 2. Expand the "how to" document to explain the ways new contributors can >> become involved in the project, so we increase the size of the >> community. >> 3. Become familiar with the release process and have a first release as >> part of the Apache Foundation >> >> At least to me, numbers 1 and 3 seem like big barriers to getting new >> folks brought in. Anyone have a list of the blockers keeping us from >> those two? I tried searching the jira for relevant tickets, but didn't >> find any. >> >> -Sean >>
