You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by Igor Vaynberg <ig...@gmail.com> on 2012/01/16 20:04:06 UTC
[vote] release Wicket 1.5.4.1
This vote is to release wicket 1.5.4.1 (vote for 1.5.4 failed)
Branch
http://git-wip-us.apache.org/repos/asf/wicket/?p=wicket.git;a=shortlog;h=refs/heads/build/wicket-1.5.4.1
Artifacts
http://people.apache.org/~ivaynberg/wicket-1.5.4.1/dist/
Maven repo
https://repository.apache.org/content/repositories/orgapachewicket-079/
Changelog
https://issues.apache.org/jira/secure/IssueNavigator.jspa?jqlQuery=fixVersion+%3D+%221.5.4%22+AND+project+%3D+WICKET
This vote ends Thursday, January 19th at 11:00am (GMT-8)
Please test the release and offer your vote.
The Wicket team!
Re: [vote] release Wicket 1.5.4.1
Posted by Martin Grigorov <mg...@apache.org>.
I see no problem with -1, -2, ... suffixes.
I prefer to not touch the successfully voted branch.
Renaming 1.5.4-rc1 to 1.5.4 will require additional testing that the
packaging is OK
On Tue, Jan 24, 2012 at 11:33 AM, Emond Papegaaij
<em...@topicus.nl> wrote:
> Perhaps we should do it the other way around and release 1.5.4-rc1, which gets
> renamed to 1.5.4 if the vote passes?
>
> On Tuesday 24 January 2012 11:29:21 Martin Grigorov wrote:
>> Hi,
>>
>> I think we did a mistake with reusing 1.5.4 as version. I realize it now...
>> Many of us use corporate Maven proxies (Nexus, Artefactory, ...). I
>> can easily remove ~/.m2/repository/org/apache/wicket/* locally but I
>> cannot do this for my employer's Nexus installation. It is managed by
>> a dedicated team.
>> I'm not 100% certain but I think our Nexus currently uses 1.5.4 from
>> the first build.
>> I'll write a ticket to our Nexus admins to delete the jars and
>> re-download them. You may do the same if this applies to your company
>> too.
>> In the future I prefer to use 1.5.4-1, 1.5.4-2, etc. for such re-builds.
>>
>> On Tue, Jan 17, 2012 at 11:22 AM, Emond Papegaaij
>>
>> <em...@topicus.nl> wrote:
>> > -1
>> >
>> > I'm sorry to have to cancel this release again, but 1.5.4 contains a
>> > regression introduced with WICKET-4256 (see WICKET-4340). If render
>> > permissions are revoked on a page, the user will see an empty page,
>> > instead of an AccessDeniedPage.
>> >
>> > I found this regression debugging a failing testcase in wicket-security
>> > this morning. It turns out this change got backported to 1.5.x and
>> > 1.4.x as well.
>> >
>> > Regarding the version number, I'd prefer the release to be numbered
>> > 1.5.4. We do not need to concern our users with the fact that we failed
>> > to release at the first go. The few people that actually tested 1.5.4
>> > will have to nuke their repo's, but that's the risk of testing releases
>> > that did not actually got released. Also, 1.5.4.1 is not a valid maven
>> > version number, see
>> > http://mojo.codehaus.org/versions-maven-plugin/version-rules.html
>> >
>> > Emond
>> >
>> > On Monday 16 January 2012 11:04:06 Igor Vaynberg wrote:
>> >> This vote is to release wicket 1.5.4.1 (vote for 1.5.4 failed)
>> >>
>> >> Branch
>> >> http://git-wip-us.apache.org/repos/asf/wicket/?p=wicket.git;a=shortlog
>> >> ;h=ref s/heads/build/wicket-1.5.4.1
>> >>
>> >> Artifacts
>> >> http://people.apache.org/~ivaynberg/wicket-1.5.4.1/dist/
>> >>
>> >> Maven repo
>> >> https://repository.apache.org/content/repositories/orgapachewicket-079
>> >> /
>> >>
>> >> Changelog
>> >> https://issues.apache.org/jira/secure/IssueNavigator.jspa?jqlQuery=fix
>> >> Versio n+%3D+%221.5.4%22+AND+project+%3D+WICKET
>> >>
>> >> This vote ends Thursday, January 19th at 11:00am (GMT-8)
>> >>
>> >> Please test the release and offer your vote.
>> >>
>> >> The Wicket team!
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
Re: [vote] release Wicket 1.5.4.1
Posted by Emond Papegaaij <em...@topicus.nl>.
Perhaps we should do it the other way around and release 1.5.4-rc1, which gets
renamed to 1.5.4 if the vote passes?
On Tuesday 24 January 2012 11:29:21 Martin Grigorov wrote:
> Hi,
>
> I think we did a mistake with reusing 1.5.4 as version. I realize it now...
> Many of us use corporate Maven proxies (Nexus, Artefactory, ...). I
> can easily remove ~/.m2/repository/org/apache/wicket/* locally but I
> cannot do this for my employer's Nexus installation. It is managed by
> a dedicated team.
> I'm not 100% certain but I think our Nexus currently uses 1.5.4 from
> the first build.
> I'll write a ticket to our Nexus admins to delete the jars and
> re-download them. You may do the same if this applies to your company
> too.
> In the future I prefer to use 1.5.4-1, 1.5.4-2, etc. for such re-builds.
>
> On Tue, Jan 17, 2012 at 11:22 AM, Emond Papegaaij
>
> <em...@topicus.nl> wrote:
> > -1
> >
> > I'm sorry to have to cancel this release again, but 1.5.4 contains a
> > regression introduced with WICKET-4256 (see WICKET-4340). If render
> > permissions are revoked on a page, the user will see an empty page,
> > instead of an AccessDeniedPage.
> >
> > I found this regression debugging a failing testcase in wicket-security
> > this morning. It turns out this change got backported to 1.5.x and
> > 1.4.x as well.
> >
> > Regarding the version number, I'd prefer the release to be numbered
> > 1.5.4. We do not need to concern our users with the fact that we failed
> > to release at the first go. The few people that actually tested 1.5.4
> > will have to nuke their repo's, but that's the risk of testing releases
> > that did not actually got released. Also, 1.5.4.1 is not a valid maven
> > version number, see
> > http://mojo.codehaus.org/versions-maven-plugin/version-rules.html
> >
> > Emond
> >
> > On Monday 16 January 2012 11:04:06 Igor Vaynberg wrote:
> >> This vote is to release wicket 1.5.4.1 (vote for 1.5.4 failed)
> >>
> >> Branch
> >> http://git-wip-us.apache.org/repos/asf/wicket/?p=wicket.git;a=shortlog
> >> ;h=ref s/heads/build/wicket-1.5.4.1
> >>
> >> Artifacts
> >> http://people.apache.org/~ivaynberg/wicket-1.5.4.1/dist/
> >>
> >> Maven repo
> >> https://repository.apache.org/content/repositories/orgapachewicket-079
> >> /
> >>
> >> Changelog
> >> https://issues.apache.org/jira/secure/IssueNavigator.jspa?jqlQuery=fix
> >> Versio n+%3D+%221.5.4%22+AND+project+%3D+WICKET
> >>
> >> This vote ends Thursday, January 19th at 11:00am (GMT-8)
> >>
> >> Please test the release and offer your vote.
> >>
> >> The Wicket team!
Re: [vote] release Wicket 1.5.4.1
Posted by Martin Grigorov <mg...@apache.org>.
There is no problem.
Apparently Maven copies the creation time of all files.
The artefacts were deployed at the staging repo at 18 Jan and few days
later they were copied to central, proxies, ... with the same ctime.
On Tue, Jan 24, 2012 at 12:20 PM, Martin Grigorov <mg...@apache.org> wrote:
> On Tue, Jan 24, 2012 at 12:07 PM, Martijn Dashorst
> <ma...@gmail.com> wrote:
>> The issue is testing through the corporate nexus. How can they get the
>> 1.5.4 artifact from a non-published repository?
>
> This is true.
> Now I have no idea how our Nexus contains 1.5.4 downloaded at 18.1.2012 :-)
>
> In my ~/.m2/settings.xml I have named repositories and 'central'
> points to our Nexus, not to the official Maven repo.
> There is no repo with name '*' in my settings.xml and see no way how
> Wicket's staging Maven repo can be proxied. I agree with you, Martijn.
>
> 18 Jan is OK since this is the last build, but I cannot explain how it
> get in the proxy repo before the official release of Wicket.
>
>>
>> Martijn
>>
>> On Tue, Jan 24, 2012 at 10:29 AM, Martin Grigorov <mg...@apache.org> wrote:
>>> Hi,
>>>
>>> I think we did a mistake with reusing 1.5.4 as version. I realize it now...
>>> Many of us use corporate Maven proxies (Nexus, Artefactory, ...). I
>>> can easily remove ~/.m2/repository/org/apache/wicket/* locally but I
>>> cannot do this for my employer's Nexus installation. It is managed by
>>> a dedicated team.
>>> I'm not 100% certain but I think our Nexus currently uses 1.5.4 from
>>> the first build.
>>> I'll write a ticket to our Nexus admins to delete the jars and
>>> re-download them. You may do the same if this applies to your company
>>> too.
>>> In the future I prefer to use 1.5.4-1, 1.5.4-2, etc. for such re-builds.
>>>
>>> On Tue, Jan 17, 2012 at 11:22 AM, Emond Papegaaij
>>> <em...@topicus.nl> wrote:
>>>> -1
>>>>
>>>> I'm sorry to have to cancel this release again, but 1.5.4 contains a
>>>> regression introduced with WICKET-4256 (see WICKET-4340). If render
>>>> permissions are revoked on a page, the user will see an empty page, instead of
>>>> an AccessDeniedPage.
>>>>
>>>> I found this regression debugging a failing testcase in wicket-security this
>>>> morning. It turns out this change got backported to 1.5.x and 1.4.x as well.
>>>>
>>>> Regarding the version number, I'd prefer the release to be numbered 1.5.4. We
>>>> do not need to concern our users with the fact that we failed to release at
>>>> the first go. The few people that actually tested 1.5.4 will have to nuke
>>>> their repo's, but that's the risk of testing releases that did not actually
>>>> got released. Also, 1.5.4.1 is not a valid maven version number, see
>>>> http://mojo.codehaus.org/versions-maven-plugin/version-rules.html
>>>>
>>>> Emond
>>>>
>>>> On Monday 16 January 2012 11:04:06 Igor Vaynberg wrote:
>>>>> This vote is to release wicket 1.5.4.1 (vote for 1.5.4 failed)
>>>>>
>>>>> Branch
>>>>> http://git-wip-us.apache.org/repos/asf/wicket/?p=wicket.git;a=shortlog;h=ref
>>>>> s/heads/build/wicket-1.5.4.1
>>>>>
>>>>> Artifacts
>>>>> http://people.apache.org/~ivaynberg/wicket-1.5.4.1/dist/
>>>>>
>>>>> Maven repo
>>>>> https://repository.apache.org/content/repositories/orgapachewicket-079/
>>>>>
>>>>> Changelog
>>>>> https://issues.apache.org/jira/secure/IssueNavigator.jspa?jqlQuery=fixVersio
>>>>> n+%3D+%221.5.4%22+AND+project+%3D+WICKET
>>>>>
>>>>> This vote ends Thursday, January 19th at 11:00am (GMT-8)
>>>>>
>>>>> Please test the release and offer your vote.
>>>>>
>>>>> The Wicket team!
>>>
>>>
>>>
>>> --
>>> Martin Grigorov
>>> jWeekend
>>> Training, Consulting, Development
>>> http://jWeekend.com
>>
>>
>>
>> --
>> Become a Wicket expert, learn from the best: http://wicketinaction.com
>
>
>
> --
> Martin Grigorov
> jWeekend
> Training, Consulting, Development
> http://jWeekend.com
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
Re: [vote] release Wicket 1.5.4.1
Posted by Martin Grigorov <mg...@apache.org>.
On Tue, Jan 24, 2012 at 12:07 PM, Martijn Dashorst
<ma...@gmail.com> wrote:
> The issue is testing through the corporate nexus. How can they get the
> 1.5.4 artifact from a non-published repository?
This is true.
Now I have no idea how our Nexus contains 1.5.4 downloaded at 18.1.2012 :-)
In my ~/.m2/settings.xml I have named repositories and 'central'
points to our Nexus, not to the official Maven repo.
There is no repo with name '*' in my settings.xml and see no way how
Wicket's staging Maven repo can be proxied. I agree with you, Martijn.
18 Jan is OK since this is the last build, but I cannot explain how it
get in the proxy repo before the official release of Wicket.
>
> Martijn
>
> On Tue, Jan 24, 2012 at 10:29 AM, Martin Grigorov <mg...@apache.org> wrote:
>> Hi,
>>
>> I think we did a mistake with reusing 1.5.4 as version. I realize it now...
>> Many of us use corporate Maven proxies (Nexus, Artefactory, ...). I
>> can easily remove ~/.m2/repository/org/apache/wicket/* locally but I
>> cannot do this for my employer's Nexus installation. It is managed by
>> a dedicated team.
>> I'm not 100% certain but I think our Nexus currently uses 1.5.4 from
>> the first build.
>> I'll write a ticket to our Nexus admins to delete the jars and
>> re-download them. You may do the same if this applies to your company
>> too.
>> In the future I prefer to use 1.5.4-1, 1.5.4-2, etc. for such re-builds.
>>
>> On Tue, Jan 17, 2012 at 11:22 AM, Emond Papegaaij
>> <em...@topicus.nl> wrote:
>>> -1
>>>
>>> I'm sorry to have to cancel this release again, but 1.5.4 contains a
>>> regression introduced with WICKET-4256 (see WICKET-4340). If render
>>> permissions are revoked on a page, the user will see an empty page, instead of
>>> an AccessDeniedPage.
>>>
>>> I found this regression debugging a failing testcase in wicket-security this
>>> morning. It turns out this change got backported to 1.5.x and 1.4.x as well.
>>>
>>> Regarding the version number, I'd prefer the release to be numbered 1.5.4. We
>>> do not need to concern our users with the fact that we failed to release at
>>> the first go. The few people that actually tested 1.5.4 will have to nuke
>>> their repo's, but that's the risk of testing releases that did not actually
>>> got released. Also, 1.5.4.1 is not a valid maven version number, see
>>> http://mojo.codehaus.org/versions-maven-plugin/version-rules.html
>>>
>>> Emond
>>>
>>> On Monday 16 January 2012 11:04:06 Igor Vaynberg wrote:
>>>> This vote is to release wicket 1.5.4.1 (vote for 1.5.4 failed)
>>>>
>>>> Branch
>>>> http://git-wip-us.apache.org/repos/asf/wicket/?p=wicket.git;a=shortlog;h=ref
>>>> s/heads/build/wicket-1.5.4.1
>>>>
>>>> Artifacts
>>>> http://people.apache.org/~ivaynberg/wicket-1.5.4.1/dist/
>>>>
>>>> Maven repo
>>>> https://repository.apache.org/content/repositories/orgapachewicket-079/
>>>>
>>>> Changelog
>>>> https://issues.apache.org/jira/secure/IssueNavigator.jspa?jqlQuery=fixVersio
>>>> n+%3D+%221.5.4%22+AND+project+%3D+WICKET
>>>>
>>>> This vote ends Thursday, January 19th at 11:00am (GMT-8)
>>>>
>>>> Please test the release and offer your vote.
>>>>
>>>> The Wicket team!
>>
>>
>>
>> --
>> Martin Grigorov
>> jWeekend
>> Training, Consulting, Development
>> http://jWeekend.com
>
>
>
> --
> Become a Wicket expert, learn from the best: http://wicketinaction.com
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
Re: [vote] release Wicket 1.5.4.1
Posted by Martijn Dashorst <ma...@gmail.com>.
The issue is testing through the corporate nexus. How can they get the
1.5.4 artifact from a non-published repository?
Martijn
On Tue, Jan 24, 2012 at 10:29 AM, Martin Grigorov <mg...@apache.org> wrote:
> Hi,
>
> I think we did a mistake with reusing 1.5.4 as version. I realize it now...
> Many of us use corporate Maven proxies (Nexus, Artefactory, ...). I
> can easily remove ~/.m2/repository/org/apache/wicket/* locally but I
> cannot do this for my employer's Nexus installation. It is managed by
> a dedicated team.
> I'm not 100% certain but I think our Nexus currently uses 1.5.4 from
> the first build.
> I'll write a ticket to our Nexus admins to delete the jars and
> re-download them. You may do the same if this applies to your company
> too.
> In the future I prefer to use 1.5.4-1, 1.5.4-2, etc. for such re-builds.
>
> On Tue, Jan 17, 2012 at 11:22 AM, Emond Papegaaij
> <em...@topicus.nl> wrote:
>> -1
>>
>> I'm sorry to have to cancel this release again, but 1.5.4 contains a
>> regression introduced with WICKET-4256 (see WICKET-4340). If render
>> permissions are revoked on a page, the user will see an empty page, instead of
>> an AccessDeniedPage.
>>
>> I found this regression debugging a failing testcase in wicket-security this
>> morning. It turns out this change got backported to 1.5.x and 1.4.x as well.
>>
>> Regarding the version number, I'd prefer the release to be numbered 1.5.4. We
>> do not need to concern our users with the fact that we failed to release at
>> the first go. The few people that actually tested 1.5.4 will have to nuke
>> their repo's, but that's the risk of testing releases that did not actually
>> got released. Also, 1.5.4.1 is not a valid maven version number, see
>> http://mojo.codehaus.org/versions-maven-plugin/version-rules.html
>>
>> Emond
>>
>> On Monday 16 January 2012 11:04:06 Igor Vaynberg wrote:
>>> This vote is to release wicket 1.5.4.1 (vote for 1.5.4 failed)
>>>
>>> Branch
>>> http://git-wip-us.apache.org/repos/asf/wicket/?p=wicket.git;a=shortlog;h=ref
>>> s/heads/build/wicket-1.5.4.1
>>>
>>> Artifacts
>>> http://people.apache.org/~ivaynberg/wicket-1.5.4.1/dist/
>>>
>>> Maven repo
>>> https://repository.apache.org/content/repositories/orgapachewicket-079/
>>>
>>> Changelog
>>> https://issues.apache.org/jira/secure/IssueNavigator.jspa?jqlQuery=fixVersio
>>> n+%3D+%221.5.4%22+AND+project+%3D+WICKET
>>>
>>> This vote ends Thursday, January 19th at 11:00am (GMT-8)
>>>
>>> Please test the release and offer your vote.
>>>
>>> The Wicket team!
>
>
>
> --
> Martin Grigorov
> jWeekend
> Training, Consulting, Development
> http://jWeekend.com
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Re: [vote] release Wicket 1.5.4.1
Posted by Martin Grigorov <mg...@apache.org>.
Hi,
I think we did a mistake with reusing 1.5.4 as version. I realize it now...
Many of us use corporate Maven proxies (Nexus, Artefactory, ...). I
can easily remove ~/.m2/repository/org/apache/wicket/* locally but I
cannot do this for my employer's Nexus installation. It is managed by
a dedicated team.
I'm not 100% certain but I think our Nexus currently uses 1.5.4 from
the first build.
I'll write a ticket to our Nexus admins to delete the jars and
re-download them. You may do the same if this applies to your company
too.
In the future I prefer to use 1.5.4-1, 1.5.4-2, etc. for such re-builds.
On Tue, Jan 17, 2012 at 11:22 AM, Emond Papegaaij
<em...@topicus.nl> wrote:
> -1
>
> I'm sorry to have to cancel this release again, but 1.5.4 contains a
> regression introduced with WICKET-4256 (see WICKET-4340). If render
> permissions are revoked on a page, the user will see an empty page, instead of
> an AccessDeniedPage.
>
> I found this regression debugging a failing testcase in wicket-security this
> morning. It turns out this change got backported to 1.5.x and 1.4.x as well.
>
> Regarding the version number, I'd prefer the release to be numbered 1.5.4. We
> do not need to concern our users with the fact that we failed to release at
> the first go. The few people that actually tested 1.5.4 will have to nuke
> their repo's, but that's the risk of testing releases that did not actually
> got released. Also, 1.5.4.1 is not a valid maven version number, see
> http://mojo.codehaus.org/versions-maven-plugin/version-rules.html
>
> Emond
>
> On Monday 16 January 2012 11:04:06 Igor Vaynberg wrote:
>> This vote is to release wicket 1.5.4.1 (vote for 1.5.4 failed)
>>
>> Branch
>> http://git-wip-us.apache.org/repos/asf/wicket/?p=wicket.git;a=shortlog;h=ref
>> s/heads/build/wicket-1.5.4.1
>>
>> Artifacts
>> http://people.apache.org/~ivaynberg/wicket-1.5.4.1/dist/
>>
>> Maven repo
>> https://repository.apache.org/content/repositories/orgapachewicket-079/
>>
>> Changelog
>> https://issues.apache.org/jira/secure/IssueNavigator.jspa?jqlQuery=fixVersio
>> n+%3D+%221.5.4%22+AND+project+%3D+WICKET
>>
>> This vote ends Thursday, January 19th at 11:00am (GMT-8)
>>
>> Please test the release and offer your vote.
>>
>> The Wicket team!
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
Re: [vote] release Wicket 1.5.4.1
Posted by Martijn Dashorst <ma...@gmail.com>.
what he said.
Martijn
On Tue, Jan 17, 2012 at 10:22 AM, Emond Papegaaij
<em...@topicus.nl> wrote:
> -1
>
> I'm sorry to have to cancel this release again, but 1.5.4 contains a
> regression introduced with WICKET-4256 (see WICKET-4340). If render
> permissions are revoked on a page, the user will see an empty page, instead of
> an AccessDeniedPage.
>
> I found this regression debugging a failing testcase in wicket-security this
> morning. It turns out this change got backported to 1.5.x and 1.4.x as well.
>
> Regarding the version number, I'd prefer the release to be numbered 1.5.4. We
> do not need to concern our users with the fact that we failed to release at
> the first go. The few people that actually tested 1.5.4 will have to nuke
> their repo's, but that's the risk of testing releases that did not actually
> got released. Also, 1.5.4.1 is not a valid maven version number, see
> http://mojo.codehaus.org/versions-maven-plugin/version-rules.html
>
> Emond
>
> On Monday 16 January 2012 11:04:06 Igor Vaynberg wrote:
>> This vote is to release wicket 1.5.4.1 (vote for 1.5.4 failed)
>>
>> Branch
>> http://git-wip-us.apache.org/repos/asf/wicket/?p=wicket.git;a=shortlog;h=ref
>> s/heads/build/wicket-1.5.4.1
>>
>> Artifacts
>> http://people.apache.org/~ivaynberg/wicket-1.5.4.1/dist/
>>
>> Maven repo
>> https://repository.apache.org/content/repositories/orgapachewicket-079/
>>
>> Changelog
>> https://issues.apache.org/jira/secure/IssueNavigator.jspa?jqlQuery=fixVersio
>> n+%3D+%221.5.4%22+AND+project+%3D+WICKET
>>
>> This vote ends Thursday, January 19th at 11:00am (GMT-8)
>>
>> Please test the release and offer your vote.
>>
>> The Wicket team!
--
Become a Wicket expert, learn from the best: http://wicketinaction.com
Re: [vote] release Wicket 1.5.4.1
Posted by Emond Papegaaij <em...@topicus.nl>.
-1
I'm sorry to have to cancel this release again, but 1.5.4 contains a
regression introduced with WICKET-4256 (see WICKET-4340). If render
permissions are revoked on a page, the user will see an empty page, instead of
an AccessDeniedPage.
I found this regression debugging a failing testcase in wicket-security this
morning. It turns out this change got backported to 1.5.x and 1.4.x as well.
Regarding the version number, I'd prefer the release to be numbered 1.5.4. We
do not need to concern our users with the fact that we failed to release at
the first go. The few people that actually tested 1.5.4 will have to nuke
their repo's, but that's the risk of testing releases that did not actually
got released. Also, 1.5.4.1 is not a valid maven version number, see
http://mojo.codehaus.org/versions-maven-plugin/version-rules.html
Emond
On Monday 16 January 2012 11:04:06 Igor Vaynberg wrote:
> This vote is to release wicket 1.5.4.1 (vote for 1.5.4 failed)
>
> Branch
> http://git-wip-us.apache.org/repos/asf/wicket/?p=wicket.git;a=shortlog;h=ref
> s/heads/build/wicket-1.5.4.1
>
> Artifacts
> http://people.apache.org/~ivaynberg/wicket-1.5.4.1/dist/
>
> Maven repo
> https://repository.apache.org/content/repositories/orgapachewicket-079/
>
> Changelog
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?jqlQuery=fixVersio
> n+%3D+%221.5.4%22+AND+project+%3D+WICKET
>
> This vote ends Thursday, January 19th at 11:00am (GMT-8)
>
> Please test the release and offer your vote.
>
> The Wicket team!
Re: [vote] release Wicket 1.5.4.1
Posted by Martin Grigorov <mg...@apache.org>.
+1
On Tue, Jan 17, 2012 at 2:35 AM, Jeremy Thomerson
<je...@wickettraining.com> wrote:
> +1
>
> On Mon, Jan 16, 2012 at 2:39 PM, Peter Ertl <pe...@gmx.org> wrote:
>
>> +1 working here
>>
>> Am 16.01.2012 um 20:04 schrieb Igor Vaynberg:
>>
>> > This vote is to release wicket 1.5.4.1 (vote for 1.5.4 failed)
>> >
>> > Branch
>> >
>> http://git-wip-us.apache.org/repos/asf/wicket/?p=wicket.git;a=shortlog;h=refs/heads/build/wicket-1.5.4.1
>> >
>> > Artifacts
>> > http://people.apache.org/~ivaynberg/wicket-1.5.4.1/dist/
>> >
>> > Maven repo
>> > https://repository.apache.org/content/repositories/orgapachewicket-079/
>> >
>> > Changelog
>> >
>> https://issues.apache.org/jira/secure/IssueNavigator.jspa?jqlQuery=fixVersion+%3D+%221.5.4%22+AND+project+%3D+WICKET
>> >
>> > This vote ends Thursday, January 19th at 11:00am (GMT-8)
>> >
>> > Please test the release and offer your vote.
>> >
>> > The Wicket team!
>>
>>
>
>
> --
> Jeremy Thomerson
> http://wickettraining.com
> *Need a CMS for Wicket? Use Brix! http://brixcms.org*
--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com
Re: [vote] release Wicket 1.5.4.1
Posted by Jeremy Thomerson <je...@wickettraining.com>.
+1
On Mon, Jan 16, 2012 at 2:39 PM, Peter Ertl <pe...@gmx.org> wrote:
> +1 working here
>
> Am 16.01.2012 um 20:04 schrieb Igor Vaynberg:
>
> > This vote is to release wicket 1.5.4.1 (vote for 1.5.4 failed)
> >
> > Branch
> >
> http://git-wip-us.apache.org/repos/asf/wicket/?p=wicket.git;a=shortlog;h=refs/heads/build/wicket-1.5.4.1
> >
> > Artifacts
> > http://people.apache.org/~ivaynberg/wicket-1.5.4.1/dist/
> >
> > Maven repo
> > https://repository.apache.org/content/repositories/orgapachewicket-079/
> >
> > Changelog
> >
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?jqlQuery=fixVersion+%3D+%221.5.4%22+AND+project+%3D+WICKET
> >
> > This vote ends Thursday, January 19th at 11:00am (GMT-8)
> >
> > Please test the release and offer your vote.
> >
> > The Wicket team!
>
>
--
Jeremy Thomerson
http://wickettraining.com
*Need a CMS for Wicket? Use Brix! http://brixcms.org*
Re: [vote] release Wicket 1.5.4.1
Posted by Peter Ertl <pe...@gmx.org>.
+1 working here
Am 16.01.2012 um 20:04 schrieb Igor Vaynberg:
> This vote is to release wicket 1.5.4.1 (vote for 1.5.4 failed)
>
> Branch
> http://git-wip-us.apache.org/repos/asf/wicket/?p=wicket.git;a=shortlog;h=refs/heads/build/wicket-1.5.4.1
>
> Artifacts
> http://people.apache.org/~ivaynberg/wicket-1.5.4.1/dist/
>
> Maven repo
> https://repository.apache.org/content/repositories/orgapachewicket-079/
>
> Changelog
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?jqlQuery=fixVersion+%3D+%221.5.4%22+AND+project+%3D+WICKET
>
> This vote ends Thursday, January 19th at 11:00am (GMT-8)
>
> Please test the release and offer your vote.
>
> The Wicket team!