On Wed, May 23, 2012 at 6:02 PM, Martijn Dashorst <[email protected]> wrote: > On Wed, May 23, 2012 at 4:30 PM, Martin Grigorov <[email protected]> wrote: >> Maybe you should do this in a branch. >> It seems it will take you some time until you are ready with the new >> release procedure. >> >> With this commit I think the currently used release.sh scripts wont be >> able to create the .tar.gz and .zip for Apache downloads >> (http://archive.apache.org/dist/wicket/). > > The current release scripts depend on Java 5 AFAICT, at least they > claim to do so (mvn5). They should not work in the first place.
mvn5 is an alias to something that runs on *your* machine, so it could be anything. I made two releases so far. > >> I suggest to drop the old release scripts once we have the new one >> stabilized, i.e. after few releases. > > Dropping them altogether should be good enough for trunk. Wicket 1.5 > can still use them though. But when we will have -beta2 ? It is just ridiculous that the vote has been canceled because of a simple change in the version of wicket-atmosphere, and almost two weeks later we do not move at all ... I'm not sure whether you realize but this just frustrates me. If there is another reason not to release -beta2 then please let me know. Otherwise I suggest to set manually the version of wicket-atmosphere to 0.1, do the release as before, then set it to 0.2-SNAPSHOT and then you will have your time to rework the release procedure. > > Martijn -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com
