Here are a couple of examples of other Java projects. As Noah stated, we must have a source jar to vote on.
[4] http://camel.apache.org/release-guide.html [5] http://rave.apache.org/release-management.html We should prepare the same type of documentation in the MetaModel wiki or site. Also, when calling for votes please prefix the e-mail with [VOTE] rather than Vote | . I missed the first vote because I didn't see it. On Wed, Dec 4, 2013 at 9:07 AM, Noah Slater <[email protected]> wrote: > Ah, okay. This is the first time I've been involved in a release vote > that deals with Maven Artifacts. > > Could you explain to me what's going on here? I see a bunch of top > level directories that seem to correspond to modules. Inside these > modules, I see that there are sigs and hashes. > > How will we distribute MetaModel? Is it in this form? In some sort of > repository that a CLI tool can fetch from. (Like how you might publish > deb or rpm files.) > > Or will there be a single file that you can download, unarchive, and > install? > > I see an files like this: > > MetaModel-mongodb-4.0.0-incubating-javadoc.jar > MetaModel-mongodb-4.0.0-incubating-javadoc.jar.asc > MetaModel-mongodb-4.0.0-incubating-javadoc.jar.asc.md5 > MetaModel-mongodb-4.0.0-incubating-javadoc.jar.asc.sha1 > MetaModel-mongodb-4.0.0-incubating-javadoc.jar.md5 > MetaModel-mongodb-4.0.0-incubating-javadoc.jar.sha1 > > There should be no reason to have .asc.md5 and .asc.sha1. Is this a > configuration error? > > As for release procedure and test procedure, I think it would be good > for the project to create: > > 1) A wiki page that documents how to prepare a release for Apache > MetaModel. There is no central Apache release procedure. The docs you > reference are intended as guides. Each project is expected to document > any project-specific steps or practices. > > One thing you could do, for example, is link to the doc, as you did in > this thread, but also include the various steps needed to discuss the > release, vote on the release, publish the release, announce the > release, and promote the release. > > Some projects even go so far as to keep email templates in an admin > repository so that going through each of the steps is as easy as > following a step by step procedure, and copying and pasting text. > > Here's a reference release procedure: > > http://wiki.apache.org/couchdb/Release_Procedure > > Note that CouchDB does not use Maven, so the details are different. > But this gives you an impression of what sort of stuff we might want > to cover in ours. > > 2) A wiki page that documents how to test a release. I've never tested > a Maven release, so I don't know what I should do here. Are there unit > tests? How do I run them? > > Here's another reference doc: > > http://wiki.apache.org/couchdb/Test_procedure > > Note: I do not think these docs need to be done before we can make our > first release. But it would be nice to look at them soon. > > On 4 December 2013 14:16, Ankit Kumar <[email protected]> wrote: > > Hi Noah, > > > > The release procedure followed is standard Apache release process. I have > > followed steps as documented here: - > > > > http://www.apache.org/dev/publishing-maven-artifacts.html#dev-env > > > > Since there were not any project specific setting/steps I did not make a > > new WIKI. > > > > I shared the public key link as that was in the Vote thread template I > > received from Henry. My key ID is B68FA0EF. > > > > Regarding the artifacts, the link I shared is the staging repository link > > under which all the artifacts are available as jar/archives etc and they > > are signed by my key. This is what comes out automatically by the Apache > > release process. In the first attempt Vote thread received some feedback > > remarks from Arvind but he did mention the signature and md5 checks > passed > > on the artifacts. > > > > P.S. Excuse me if I don't really understand you as this is the first > time I > > do an Apache release. > > > > Regards > > Ankit > > > > > > On Wed, Dec 4, 2013 at 12:48 PM, Noah Slater <[email protected]> wrote: > > > >> Do you have your release procedure written down on the wiki somewhere? > >> I'd like to look at it. > >> > >> We should prepare some test instructions on the wiki and link to that > >> too, so people voting know what to check for. > >> > >> > https://people.apache.org/keys/committer/ankitkumar2711.asc > >> > >> I would prefer it if you gave the key ID and let me fetch it myself > >> with gpg --recv-keys. > >> > >> > > >> > https://repository.apache.org/content/repositories/orgapachemetamodel-010/ > >> > >> We cannot vote on this. We can only vote on a prepared source > >> artefact, like a zip file. This file is what should be signed by your > >> GPG key. > >> > >> You mention "release artefact" in your email though, so maybe I am > >> missing something? > >> > >> Thanks! > >> > >> On 3 December 2013 16:05, Ankit Kumar <[email protected]> wrote: > >> > Hi All, > >> > > >> > Please vote on releasing the following candidate as Apache > >> > Metamodel(incubating) version 4.0.0. > >> > This will be the first incubator release for MetaModel project in > Apache. > >> > NOTE: This release contains fixes for issues as reported in the first > >> > release attempt vote thread. > >> > > >> > The tag to be voted on is v4.0.0-incubating : > >> > > >> > https://git-wip-us.apache.org/repos/asf?p=incubator-metamodel.git;a=tag;h=refs/tags/MetaModel-4.0.0-incubating > >> > > >> > > >> > Release artifacts are signed with the following key: > >> > https://people.apache.org/keys/committer/ankitkumar2711.asc > >> > > >> > The staging repository for this release can be found at: > >> > > >> > https://repository.apache.org/content/repositories/orgapachemetamodel-010/ > >> > > >> > Please vote on releasing this package as Apache MetaModel > >> 4.0.0-incubating. > >> > The vote is open until <6th December 2013 16:00 CET> and passes if a > >> > majority of at least 3 IPMC votes are cast. > >> > > >> > [ ] +1 Release this package as Apache MetaModel 4.0.0-incubating > >> > [ ] -1 Do not release this package because ... > >> > > >> > > >> > Regards > >> > Ankit > >> > >> > >> > >> -- > >> Noah Slater > >> https://twitter.com/nslater > >> > > > > -- > Noah Slater > https://twitter.com/nslater >
