+1 to release I've ran our selenium tests against 6.2.0-SNAPSHOT, which contains the same code as 6.1.0 and all tests pass. I've checked the release, and the files look ok and it builds fine.
About WICKET-4789, it's a regression against 6.1.0, so I guess it should be fixed, but I see no reason to delay 6.1.0 for this issue as the usecase really is a cornercase. We can always do a 6.1.1 release next week with a fix for this issue, perhaps with one or two other issues that might surface. Best regards, Emond On Wednesday 26 September 2012 15:26:04 Martijn Dashorst wrote: > All, > > It's been hard work, but I have managed to *finally* create a release > candidate of Wicket 6.1.0. The release has been created by a script, > but I doubt it is reusable by anyone not running the same > configuration as myself (Mac OS X Mountain Lion, homebrew > installations of gpg, gpg-agent, etc) > > Please download the source distributions found on my people.apache.org > distribution area linked below. > > I have included the signatures for both the source archives. This vote > lasts for 72 hours minimum. > > [ ] Yes, release Apache Wicket 6.1.0 > [ ] No, don't release Apache Wicket 6.1.0, because ... > > Distributions, changelog, keys and signatures can be found at: > > http://people.apache.org/~dashorst/wicket-6.1.0 > > Signature for apache-wicket-6.1.0.tar.gz: > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.12 (Darwin) > > iEYEABECAAYFAlBi+38ACgkQJBX8W/xy/UWrYwCdHWH/7QmqYQcqL1FdXS2E0BCR > Ph8AoKKEJPUr8uhgnn86kl6I5NfURDZJ > =SMVj > -----END PGP SIGNATURE----- > > Signature for apache-wicket-6.1.0.zip: > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.12 (Darwin) > > iEYEABECAAYFAlBi+38ACgkQJBX8W/xy/UXpyACgivkLLUH3YFJXX5ol2NtLgL0h > kPwAnRjsDq8EZvGmv8/VkDFAPf8yEui7 > =jxFi > -----END PGP SIGNATURE----- > > Martijn
