Hi Peter, Thanks for the checklist. I've run the rat report and corrected a couple of bits. I'm not two sure what the last two files are for and how their licenses affect ASF.
I've attached the report, does anyone have any idea what I'm supposed to do with them? The command I used was; java -jar $RAT/apache-rat-0.7.jar -d src -e *.mf > rat.report It is okay to exclude the manifest files, isn't it? Cheers, Tom On Sat, May 21, 2011 at 12:21 PM, Peter Firmstone <[email protected]> wrote: > Niclas Hedhman wrote: >> >> On Fri, May 20, 2011 at 6:31 AM, Jukka Zitting <[email protected]> >> wrote: >> >>> >>> Is this a vote to have a vote on a release? ;-) >>> >> >> Funny, isn't it? >> >> >>> >>> Anyway, releases are always good, go for it! +1 >>> >> >> Just remember, this is NOT a release vote. After the release artifacts >> are produced and presented, the community (any user can also help) >> double-checks it and votes for a release of those artifacts. >> >> Cheers >> > > The release process is from memory (I've got it written down), guess I'd > better tend to it soon, unless someone else has the time: > > 1. Check out the current trunk > 2. Run Rat report tool on current trunk. > 3. Fix any license issues reported by Rat. > 4. Have all committers add their signatures to the Keys file. > 5. Branch the current trunk > 6. Checkout and build the branch. > 7. Build the branch and release artifacts > 8. Post the release artifacts along with rat reports and message digests > 9. Those willing can download the release artifacts and test on their > hardware. > 10. Vote on the release artifacts. > 11. If the vote passes, post release artifacts, move previous release > to archives. > > Peter. >
