myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Kienenberger <>
Subject Re: Release checklist and voting checklist
Date Thu, 23 Aug 2012 17:02:27 GMT
Yes, I wasn't saying that this is something that the release manager
needs to do.

I was saying that this is something each person voting on the release
should do to verify the release.

Maybe something will change and the automated process won't catch it.

On Thu, Aug 23, 2012 at 12:57 PM, Leonardo Uribe <> wrote:
> Hi
> I use the wiki pages as a checklist of the release procedure. In that
> way, for the next release I copy the previous one and then I update
> the release numbers and follow the process.
> The only thing new on the list is do mvn apache-rat:check. The
> remaining points are checked by nexus, or the artifacts are generated
> automatically.
> regards,
> Leonardo Uribe
> 2012/8/23 Mike Kienenberger <>:
>> Well, I see now that while the "Proposed Release Announcement" section
>> was empty, the actual release announcement was posted at the end --
>> not sure how I missed that.
>> So the only thing that needs attention is whether we should add those
>> explicit "things to check" to the vote email.
>> On Thu, Aug 23, 2012 at 9:50 AM, Mike Kienenberger <> wrote:
>>> A recent Apache email discussed releases, and lead me to the following
>>> email.   I was particularly interested in the "some things to check
>>> before voting" section which I think we should incorporate into our
>>> own voting messages.   [Continued after the inline message below....]
>>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>>> Discussion thread for vote on <version> release, with SVN source tag
>>> (r1370332).
>>> For more information on the release process, check out
>>> Some of the things to check before voting are:
>>>   - does "mvn apache-rat:check" pass on the source
>>>   - can you build the contents of source release zip and SVN tag
>>>   - do all of the staged jars/wars/zips contain the required LICENSE and
>>> NOTICE files
>>>   - are all of the staged jars/wars/zips signed and the signature verifiable
>>>   - is the signing key in the project's KEYS file and on a public server
>>> (i.e.
>>> --
>>> Francesco Chicchiriccò
>>> ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Member
>>> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
>>> I looked around at our own site, and found Tobago's release checklist
>>> page [1] which has a release checklist, a voting email template, and a
>>> release template.   It was also the most obvious result of a Google
>>> search on "myfaces release checklist."
>>> [1]
>>> Our general Myfaces release information is referenced from the CWiki
>>> "Release a MyFaces Project" page[2] with specific release notes for a
>>> specific version stored on the wiki, such as the Myfaces Core Release
>>> 2.1.8 page located here[5].
>>> [2]
>>> [3]
>>> The core release notes are great, although I think we should probably
>>> put the release announcement in there.  Right now the two I looked at
>>> only have placeholder text rather than an actual example announcement.
>>>   I'll go ahead and do that for 2.1.8 and 2.1.1 on the wiki as these
>>> are the ones most likely to be used a template for new releases.
>>> I'd like to suggest that we also add text to these wiki documents
>>> similar to the Syncope voting email above listing out things to check
>>> before voting.   What do you think?

View raw message