[Vote] Release Apache Wicket 6.0.0-beta2

[Martin Grigorov-4]

This vote is to release Apache Wicket 6.0.0-beta2

Git repo
http://git-wip-us.apache.org/repos/asf/wicket.git

Branch name
build/wicket-6.0.0-beta2

Archived and signed Git repo
http://people.apache.org/~mgrigorov/wicket-6.0.0-beta2/

Changelog
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310561&version=12320343

This vote ends Wednesday, May 16th at 19:00 (GMT+1)

Please test the release and offer your vote.

The Wicket team!

[Papegaaij]

-1 due to the incorrect versioning of wicket-atmosphere. For wicket-atmosphere
to get some public attention (the author of Atmosphere wants to announce it),
it needs a real version.

Emond

On Sunday 13 May 2012 18:51:11 Martin Grigorov wrote:

> This vote is to release Apache Wicket 6.0.0-beta2
>
> Git repo
> http://git-wip-us.apache.org/repos/asf/wicket.git
>
> Branch name
> build/wicket-6.0.0-beta2
>
> Archived and signed Git repo
> http://people.apache.org/~mgrigorov/wicket-6.0.0-beta2/
>
> Changelog
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310561&ve
> rsion=12320343
>
> This vote ends Wednesday, May 16th at 19:00 (GMT+1)
>
> Please test the release and offer your vote.
>
> The Wicket team!

[Martin Grigorov-4]

+1 to release it

tested most of wicket-examples

the broken module is not in the staging repo. i.e. there wont be
0.1-SNAPSHOT in Maven central

On Mon, May 14, 2012 at 3:06 PM, Emond Papegaaij
<[hidden email]> wrote:

> -1 due to the incorrect versioning of wicket-atmosphere. For wicket-atmosphere
> to get some public attention (the author of Atmosphere wants to announce it),
> it needs a real version.
>
> Emond
>
> On Sunday 13 May 2012 18:51:11 Martin Grigorov wrote:
>> This vote is to release Apache Wicket 6.0.0-beta2
>>
>> Git repo
>> http://git-wip-us.apache.org/repos/asf/wicket.git
>>
>> Branch name
>> build/wicket-6.0.0-beta2
>>
>> Archived and signed Git repo
>> http://people.apache.org/~mgrigorov/wicket-6.0.0-beta2/
>>
>> Changelog
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310561&ve
>> rsion=12320343
>>
>> This vote ends Wednesday, May 16th at 19:00 (GMT+1)
>>
>> Please test the release and offer your vote.
>>
>> The Wicket team!

--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

[Martijn Dashorst]

On Tue, May 15, 2012 at 9:43 AM, Martin Grigorov <[hidden email]> wrote:
> the broken module is not in the staging repo. i.e. there wont be
> 0.1-SNAPSHOT in Maven central

The whole idea is that we release these modules as part of our normal
releases to give them exposure. Therefore rerolling the release with
proper 0.1 versioning for the experimentals is necessary IMO.

Martijn

[Igor Vaynberg-2]

if the whole idea is to release these modules why move wicket-cdi in
there and disable its releasing?

-igor

On Tue, May 15, 2012 at 12:51 AM, Martijn Dashorst
<[hidden email]> wrote:
> On Tue, May 15, 2012 at 9:43 AM, Martin Grigorov <[hidden email]> wrote:
>> the broken module is not in the staging repo. i.e. there wont be
>> 0.1-SNAPSHOT in Maven central
>
> The whole idea is that we release these modules as part of our normal
> releases to give them exposure. Therefore rerolling the release with
> proper 0.1 versioning for the experimentals is necessary IMO.
>
> Martijn

[Martin Grigorov-4]

wicket-cdi is more mature, imo it may be included directly with 6.x version

but I think that new modules like wicket-atmo can have their own
release cycle until they are included in the big group. there is no
reason why wicket-atmo:0.2 should wait for 6.0.0-beta3

but of course this will add some more pain in the release process

On Tue, May 15, 2012 at 4:30 PM, Igor Vaynberg <[hidden email]> wrote:

> if the whole idea is to release these modules why move wicket-cdi in
> there and disable its releasing?
>
> -igor
>
> On Tue, May 15, 2012 at 12:51 AM, Martijn Dashorst
> <[hidden email]> wrote:
>> On Tue, May 15, 2012 at 9:43 AM, Martin Grigorov <[hidden email]> wrote:
>>> the broken module is not in the staging repo. i.e. there wont be
>>> 0.1-SNAPSHOT in Maven central
>>
>> The whole idea is that we release these modules as part of our normal
>> releases to give them exposure. Therefore rerolling the release with
>> proper 0.1 versioning for the experimentals is necessary IMO.
>>
>> Martijn

--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

[Martin Grigorov-4]

Any progress on a solution for the problem with the release of
wicket-atmosphere module ?

On Tue, May 15, 2012 at 4:37 PM, Martin Grigorov <[hidden email]> wrote:

> wicket-cdi is more mature, imo it may be included directly with 6.x version
>
> but I think that new modules like wicket-atmo can have their own
> release cycle until they are included in the big group. there is no
> reason why wicket-atmo:0.2 should wait for 6.0.0-beta3
>
> but of course this will add some more pain in the release process
>
> On Tue, May 15, 2012 at 4:30 PM, Igor Vaynberg <[hidden email]> wrote:
>> if the whole idea is to release these modules why move wicket-cdi in
>> there and disable its releasing?
>>
>> -igor
>>
>> On Tue, May 15, 2012 at 12:51 AM, Martijn Dashorst
>> <[hidden email]> wrote:
>>> On Tue, May 15, 2012 at 9:43 AM, Martin Grigorov <[hidden email]> wrote:
>>>> the broken module is not in the staging repo. i.e. there wont be
>>>> 0.1-SNAPSHOT in Maven central
>>>
>>> The whole idea is that we release these modules as part of our normal
>>> releases to give them exposure. Therefore rerolling the release with
>>> proper 0.1 versioning for the experimentals is necessary IMO.
>>>
>>> Martijn
>
>
>
> --
> Martin Grigorov
> jWeekend
> Training, Consulting, Development
> http://jWeekend.com

--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

[Martijn Dashorst]

I strive to build a release tomorrow, but family might interfere (it's
a holiday tomorrow).

Martijn

On Wed, May 16, 2012 at 5:13 PM, Martin Grigorov <[hidden email]> wrote:

> Any progress on a solution for the problem with the release of
> wicket-atmosphere module ?
>
> On Tue, May 15, 2012 at 4:37 PM, Martin Grigorov <[hidden email]> wrote:
>> wicket-cdi is more mature, imo it may be included directly with 6.x version
>>
>> but I think that new modules like wicket-atmo can have their own
>> release cycle until they are included in the big group. there is no
>> reason why wicket-atmo:0.2 should wait for 6.0.0-beta3
>>
>> but of course this will add some more pain in the release process
>>
>> On Tue, May 15, 2012 at 4:30 PM, Igor Vaynberg <[hidden email]> wrote:
>>> if the whole idea is to release these modules why move wicket-cdi in
>>> there and disable its releasing?
>>>
>>> -igor
>>>
>>> On Tue, May 15, 2012 at 12:51 AM, Martijn Dashorst
>>> <[hidden email]> wrote:
>>>> On Tue, May 15, 2012 at 9:43 AM, Martin Grigorov <[hidden email]> wrote:
>>>>> the broken module is not in the staging repo. i.e. there wont be
>>>>> 0.1-SNAPSHOT in Maven central
>>>>
>>>> The whole idea is that we release these modules as part of our normal
>>>> releases to give them exposure. Therefore rerolling the release with
>>>> proper 0.1 versioning for the experimentals is necessary IMO.
>>>>
>>>> Martijn
>>
>>
>>
>> --
>> Martin Grigorov
>> jWeekend
>> Training, Consulting, Development
>> http://jWeekend.com
>
>
>
> --
> Martin Grigorov
> jWeekend
> Training, Consulting, Development
> http://jWeekend.com

--
Become a Wicket expert, learn from the best: http://wicketinaction.com