+1 release
On 11/2/08, Frank Bille <[EMAIL PROTECTED]> wrote: > Hey all, > > I have build the first release candidate of version 1.4 and put it on my > p.a.o account for you to test. > > Distribution: > http://people.apache.org/~frankbille/releases/apache-wicket-1.4-rc1/dist/ > > Maven repo: > http://people.apache.org/~frankbille/releases/apache-wicket-1.4-rc1/m2-repo/ > > RAT log: > http://people.apache.org/~frankbille/releases/apache-wicket-1.4-rc1/apache-wicket-1.4-rc1.rat.log > > The artifacts has been build and signed by me, so use this KEYS file to > verify that they have not been modified along the way: > http://people.apache.org/~frankbille/releases/apache-wicket-1.4-rc1/dist/KEYS > > > It's the usual procedure: We, as a community (and specially the PMC members) > are to make sure that the release is solid both technically but also > legally. Therefore if you have the time here some examples on what to test > in the release: > > - Run "mvn clean install" in the distribution to make sure that it builds, > tests run without failures and installs correctly in you environment. > - Run "mvn jetty:run" in the wicket-examples directory in the distribution > to run a jetty server with the examples. Then point a browser to > http://localhost:8080/wicket-examples and click around. The more > browsers/operating system combinations the better. > - Look through the RAT log to see if there is anything that looks wrong in > terms of which files should have a license header. > - Verify the signatures of the files matches my public key. > - Try out the maven repo with your project to see if it works as expected. > - Look through the distribution in general to see that it looks as expected > and that the files there contain what is expected (this is a bit vague, but > follow your intuition. And no, it's not a mistake that the javadocs are not > included in the dist) > > > [ ] Yes release Apache Wicket 1.4 RC1 > [ ] No, don't release because.... > > > Regards, > Frank >
