Is there a reason why 7.0.0.-M1 is used as RELEASE? I use
<version>RELEASE</version> to get released version as soon as possible, but
M1 somewhat feels like an RC.. ?


On Tue, Apr 29, 2014 at 10:22 PM, Martin Grigorov <[email protected]>wrote:

> I've renamed version 7.0.0 to 7.0.0-M1.
> It will be easy to get a list of tickets that have "Fix version" any of
> 7.0.0-M1, ..., 7.0.0 later.
>
> I've also created 7.0.0-M2 that should be used for fixed tickets from now
> on.
>
> Martin Grigorov
> Wicket Training and Consulting
>
>
> On Tue, Apr 29, 2014 at 11:23 AM, Martijn Dashorst <
> [email protected]> wrote:
>
> > probably a good idea... Does that make it more difficult to track what
> > went into 7.0 as a whole? Or do we collapse m1-mX when 7.0 goes final?
> >
> > Martijn
> >
> >
> > On Sun, Apr 27, 2014 at 8:15 PM, Martin Grigorov <[email protected]>
> > wrote:
> > > Should we change the "Fix version" from 7.0.0 to 7.0.0-M1 for better
> > > tracking what will be in the next release ?
> > >
> > > Martin Grigorov
> > > Wicket Training and Consulting
> > >
> > >
> > > On Sun, Apr 27, 2014 at 9:13 PM, Andrea Del Bene <[email protected]
> > >wrote:
> > >
> > >> +1 to release
> > >>
> > >>  Yes, it does - https://issues.apache.org/jira/browse/WICKET-5572
> > >>> But the fix will be in the next release
> > >>>
> > >>> Martin Grigorov
> > >>> Wicket Training and Consulting
> > >>>
> > >>>
> > >>> On Sun, Apr 27, 2014 at 8:42 PM, Andrea Del Bene <
> [email protected]
> > >>> >wrote:
> > >>>
> > >>>  +1 if the problem with demo application has been solved.
> > >>>>
> > >>>>   We need one more binding +1 vote to pass or a -1 with a reason why
> > to
> > >>>> fail
> > >>>>
> > >>>>> the release.
> > >>>>> Please vote!
> > >>>>>
> > >>>>> Martin Grigorov
> > >>>>> Wicket Training and Consulting
> > >>>>>
> > >>>>>
> > >>>>> On Wed, Apr 23, 2014 at 11:37 PM, Martin Grigorov <
> > [email protected]
> > >>>>>
> > >>>>>> wrote:
> > >>>>>>
> > >>>>>   +1 to release
> > >>>>>
> > >>>>>> tested:
> > >>>>>> - build from source (mvn clean install)
> > >>>>>> - random wicket-examples
> > >>>>>> - run grunt to test the JS
> > >>>>>> - wicketstuff (mvn clean test)
> > >>>>>> - wicket-bootstrap
> > >>>>>> -- mvn clean install PASSES
> > >>>>>> -- the demo application fails with:
> > >>>>>> java.lang.IllegalStateException
> > >>>>>> at org.apache.wicket.MarkupContainer.dequeue(
> > >>>>>> MarkupContainer.java:2134)
> > >>>>>> at org.apache.wicket.MarkupContainer.dequeue(
> > >>>>>> MarkupContainer.java:2046)
> > >>>>>> at
> > >>>>>> org.apache.wicket.MarkupContainer.addedComponent(
> > >>>>>> MarkupContainer.java:958)
> > >>>>>> at org.apache.wicket.MarkupContainer.add(MarkupContainer.java:187)
> > >>>>>>
> > >>>>>> I will debug it soon.
> > >>>>>>
> > >>>>>>
> > >>>>>>    Martin Grigorov
> > >>>>>> Wicket Training and Consulting
> > >>>>>>
> > >>>>>>
> > >>>>>> On Mon, Apr 21, 2014 at 7:34 PM, Igor Vaynberg <
> > >>>>>> [email protected]>
> > >>>>>> wrote:
> > >>>>>>
> > >>>>>>   +1 to release
> > >>>>>>
> > >>>>>>> -igor
> > >>>>>>>
> > >>>>>>> On Sun, Apr 20, 2014 at 1:44 PM, Martijn Dashorst
> > >>>>>>> <[email protected]> wrote:
> > >>>>>>>
> > >>>>>>>  WOW. This is the first of many votes to come for our first
> Wicket
> > 7
> > >>>>>>>> release train. It took some work, but I managed to manipulate
> our
> > >>>>>>>> projects, Maven and its release plugin to generate the right
> > release
> > >>>>>>>> version numbers for the right projects.
> > >>>>>>>>
> > >>>>>>>> Known issue:
> > >>>>>>>>
> > >>>>>>>> Wicket Atmosphere version mismatch between wicket 6 and 7
> > >>>>>>>>
> > >>>>>>>> It appears that wicket-experimental/wicket-atmosphere has
> version
> > >>>>>>>> 0.10
> > >>>>>>>> if we release 7.0.0-M1 **right now**.
> > >>>>>>>>
> > >>>>>>>> Now I don't have a clear view if atmosphere in master is up to
> > date
> > >>>>>>>> with 0.18 from Wicket 6.15.
> > >>>>>>>>
> > >>>>>>>> I think it ultimately doesn't **yet**. If 7.x/atmosphere:0.10 is
> > on
> > >>>>>>>> the same patch level as 6.x/atmosphere/0.10, then we have parity
> > in
> > >>>>>>>> versions. If 7.x/atmosphere:0.10 is on the same patch level as
> > >>>>>>>> 6.x/atmosphere/0.18, we can fix the numbering scheme in 7.0.0-M2
> > >>>>>>>>
> > >>>>>>>>
> > >>>>>>>> So here it goes:
> > >>>>>>>>
> > >>>>>>>> ============================================================
> > >>>>>>>> ============
> > >>>>>>>>
> > >>>>>>>> This is a vote to release Apache Wicket 7.0.0-M1
> > >>>>>>>>
> > >>>>>>>> Please download the source distributions found in our staging
> area
> > >>>>>>>> linked below.
> > >>>>>>>>
> > >>>>>>>> I have included the signatures for both the source archives.
> This
> > >>>>>>>> vote
> > >>>>>>>> lasts for 72 hours minimum.
> > >>>>>>>>
> > >>>>>>>> [ ] Yes, release Apache Wicket 7.0.0-M1
> > >>>>>>>> [ ] No, don't release Apache Wicket 7.0.0-M1, because ...
> > >>>>>>>>
> > >>>>>>>> Distributions, changelog, keys and signatures can be found at:
> > >>>>>>>>
> > >>>>>>>>       https://dist.apache.org/repos/dist/dev/wicket/7.0.0-M1
> > >>>>>>>>
> > >>>>>>>> Staging repository:
> > >>>>>>>>
> > >>>>>>>>
> > >>>>>>>>   https://repository.apache.org/content/repositories/
> > >>>>>>>>
> > >>>>>>> orgapachewicket-1018
> > >>>>>>>
> > >>>>>>>  The binaries are available in the above link, as are a staging
> > >>>>>>>> repository for Maven. Typically the vote is on the source, but
> > should
> > >>>>>>>> you find a problem with one of the binaries, please let me
> know, I
> > >>>>>>>> can
> > >>>>>>>> re-roll them some way or the other.
> > >>>>>>>>
> > >>>>>>>> Release notes:
> > >>>>>>>>
> > >>>>>>>>    - Wicket 7 requires Java 7 at a minimum
> > >>>>>>>>    - Wicket 7 requires at least a servlet 3 compatible container
> > >>>>>>>>    - Migration guide: http://s.apache.org/wicket7migrate
> > >>>>>>>>
> > >>>>>>>> ============================================================
> > >>>>>>>> ============
> > >>>>>>>>
> > >>>>>>>> The signatures for the source release artefacts:
> > >>>>>>>>
> > >>>>>>>> apache-wicket-7.0.0-M1.tar.gz.asc
> > >>>>>>>>
> > >>>>>>>> -----BEGIN PGP SIGNATURE-----
> > >>>>>>>> Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
> > >>>>>>>> Comment: GPGTools - https://gpgtools.org
> > >>>>>>>>
> > >>>>>>>> iEYEABECAAYFAlNUK4wACgkQJBX8W/xy/UXKbgCdHzMcgjCtDXTJsLLUwHEGNWUJ
> > >>>>>>>> ZwwAoNCbquGqNMzYY9tMi+lflzH4MqcP
> > >>>>>>>> =x14q
> > >>>>>>>> -----END PGP SIGNATURE-----
> > >>>>>>>>
> > >>>>>>>> apache-wicket-7.0.0-M1.zip.asc
> > >>>>>>>>
> > >>>>>>>> -----BEGIN PGP SIGNATURE-----
> > >>>>>>>> Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
> > >>>>>>>> Comment: GPGTools - https://gpgtools.org
> > >>>>>>>>
> > >>>>>>>> iEYEABECAAYFAlNUK4wACgkQJBX8W/xy/UXUfQCg1EU8S+Z5mdy7svWlK1WwMAG3
> > >>>>>>>> tWwAoJr6egOay7UNi8HCH2cOBZekOO0j
> > >>>>>>>> =AVEj
> > >>>>>>>> -----END PGP SIGNATURE-----
> > >>>>>>>>
> > >>>>>>>>
> > >>
> >
> >
> >
> > --
> > Become a Wicket expert, learn from the best: http://wicketinaction.com
> >
>

Reply via email to