Hi, just a reminder - I think we have to discuss about point 3. before starting the release.
> Hi all, > > I have several questions to the release build scripts, because I saw some > changes in the master made by Martijn > (https://github.com/apache/wicket/commit/f82fd1c39aa1db708c8a7d510b75aeffb3d6e39e): > > 1. Should we also change the build scripts in 6.x / 7.x in addition to master > to be more generic? > > 2. Can we remove all other outdated scripts of other branches, too? > > 3. There are some changes I don't understand in the master: > > https://github.com/apache/wicket/blob/f82fd1c39aa1db708c8a7d510b75aeffb3d6e39e/build-versions.py#L46 > > I changed the name explicit to "org.apache.wicket.experimental.wicket8" so > that there are independent version of wicket7 / wicket8 - it has been > switched back to wicket7. > > https://github.com/apache/wicket/blob/f82fd1c39aa1db708c8a7d510b75aeffb3d6e39e/release.sh#L266 > > The branch is master, not wicket-7.x. kind regards Tobias > Am 29.06.2016 um 07:28 schrieb Sven Meier <[email protected]>: > > Me too +1 > > Sven > >> On 28.06.2016 21:12, Andrea Del Bene wrote: >> another +1 >> >>> On 28/06/2016 14:46, Tobias Soloschenko wrote: >>> +1 from me, too. >>> >>> kind regards >>> >>> Tobias >>> >>>> Am 28.06.2016 um 13:13 schrieb Martin Grigorov <[email protected]>: >>>> >>>> +1 to cut 8.0.0-M1 now. >>>> >>>> >>>> Martin Grigorov >>>> Wicket Training and Consulting >>>> https://twitter.com/mtgrigorov >>>> >>>> On Tue, Jun 28, 2016 at 1:10 PM, Martijn Dashorst < >>>> [email protected]> wrote: >>>> >>>>> I see some API improvements happening, is it prudent to fire the >>>>> release process or wait for some stabilization? >>>>> >>>>> Martijn >>>>> >>>>> -- >>>>> Become a Wicket expert, learn from the best: http://wicketinaction.com >
