Hi all, I'm working on a release for log4cxx and have some questions about the process itself:
1. KEYS in dist-repo There's a KEYS file at the root of our dist-repo, do I need to get added there with my signing key? I've added it wherever the docs told me, KEYS in project repo, home.apache.org, LDAP, public keyserver etc., but I can't remember reading about that file. Additionally, some projects like log4net have an additional KEYS file in their folder, log4j doesn't. Should the file of my project be added in my folder as well? https://dist.apache.org/repos/dist/release/logging/ 2. Maven distribution Am I correct in assuming that while log4cxx uses Maven to build, it is not creating Maven distribution files? So I don't need to follow the heavy stuff documented below? http://www.apache.org/dev/publishing-maven-artifacts.html 3. Release candidates vs. not "mvn release:prepare" asks for tag names and such and defaults to using that of the releases version, instead of things like RC1 etc. During my local tests I simply reverted and deleted the tags etc. But in case of a formal release process where people could veto against a release, is that still a good approach? What I don't understand is, if I create some RC1 using Maven and the vote passes and such, how do I get an actual non-RC1 release? The RC1 is committed in the pom.xml and part of the released tag and there can't be changed easily anymore. 4. When to call for a vote? I think I'm technically able to create the release: Things build, I have the dist files, am able to sign etc. Do I first create the release with its tag, sign the files and call then for a vote? Or am I only tagging, calling for a vote and if that passes actually sign and upload things? Or is the vote actually the first thing even before tagging and such? From the docs I have the feeling that I need to create the release by tagging, signing the dist files and call than for a vote: > WHAT IS A VALID RELEASE PACKAGE? > SIGNING RELEASE ARTIFACTS > VOTING TO RELEASE > DISTRIBUTION http://www.apache.org/dev/release-publishing.html 5. Who distributes my files? As per the docs, either one has write access to the dist repo oneself or a PMC needs to upload the files. I don't have that access, so how are my signed files distributed to a POMC so that one can upload them in the dist-repo? Do I need to use the dist-dev-repo? I do have write access in there. https://dist.apache.org/repos/dist/dev/logging/ Thanks for your input! Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning E-Mail: [email protected] AM-SoFT IT-Systeme http://www.AM-SoFT.de/ Telefon...........05151- 9468- 55 Fax...............05151- 9468- 88 Mobil..............0178-8 9468- 04 AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
