I had a look to the release checklist. Make sure that you are not referencing any SNAPSHOT version (dependencies and plugins) otherwise the release will fail => OK
Make sure that you update the xdocs/changes.xml file to reflect your release => no changes.xml file yet. Should we add that in 0.1 or in 0.2.? Make sure that all your files contain a ASF licence header (look at the RAT report when in doubt, generated with mvn site) => mvn rat:check leads to a build failure with "too many unlicensed files: 199", looks quite strange. I'd love if someone had a look at this, in my opinion most classes and resources contains the ASF license header. Make sure that the LICENSE and NOTICE files are present and correct - especially that the year is correct in the NOTICE file. => should be OK Make sure that you make a test build using a clean checkout => OK Make sure that there are no major bugs in JIRA => OK Make sure to add all missing committers and contributers => No contributers and committers page yet. Should we add that in 0.1 or in 0.2.? On 24 February 2011 11:11, Chapuis Bertil <bchap...@agimem.com> wrote: > Ok, I will wait for the advices. > > > On 24 February 2011 11:04, Thorsten Scherler <scher...@gmail.com> wrote: > >> On Thu, 2011-02-24 at 10:25 +0100, Chapuis Bertil wrote: >> > ... >> > >> > Do I run the mvn release:prepare without the dry run parameter to see >> the >> > magic in action? ;-) >> >> I just wrote to the general incubator list to get advice about when to >> use the plugin. In my understanding we need to first do some RC, no? >> >> Maybe you can try to do a "0.1-RC1-incubator" release first? >> >> salu2 >> -- >> Thorsten Scherler <thorsten.at.apache.org> >> codeBusters S.L. - web based systems >> <consulting, training and solutions> >> http://www.codebusters.es/ >> >> > > > -- > Bertil Chapuis > Agimem Sàrl > http://www.agimem.com > > -- Bertil Chapuis Agimem Sàrl http://www.agimem.com
