Done.
The announcement will follow once Maven and the mirrors are updated.

Martin Grigorov
Wicket Training and Consulting


On Tue, Feb 4, 2014 at 10:54 PM, Martijn Dashorst <
[email protected]> wrote:

> Now *that* is a good way to check if folks are paying attention!
>
> As for voting, if you have +3 binding you can release, esp. Since this is
> just a version bump.
>
> Martijn
>
> > On 4 feb. 2014, at 20:43, Martin Grigorov <[email protected]> wrote:
> >
> > Wow, this is a grande #FAIL !!!
> > Why no one told me that 1.4.22 is already out since one year :-)
> > I didn't check because I was sure that the last 1.4.x is 1.4.21.
> > Trying to release it I see that there is 1.4.22 and the voted one should
> > have been named 1.4.23
> >
> > I guess I have to rebuild and and then re-vote it for another 3 days ?
> >
> > Martin Grigorov
> > Wicket Training and Consulting
> >
> >
> > On Tue, Feb 4, 2014 at 8:33 PM, Martin Grigorov <[email protected]
> >wrote:
> >
> >> The vote has passed with 3 binding +1s.
> >> Thank you!
> >>
> >> Martin Grigorov
> >> Wicket Training and Consulting
> >>
> >>
> >> On Fri, Jan 31, 2014 at 6:31 PM, Andrea Del Bene <[email protected]
> >wrote:
> >>
> >>> +1
> >>>> +1
> >>>>
> >>>> -igor
> >>>>
> >>>>
> >>>> On Thu, Jan 30, 2014 at 5:00 AM, Martin Grigorov <
> [email protected]
> >>>> wrote:
> >>>>
> >>>>> This vote is to release Apache Wicket 1.4.22
> >>>>>
> >>>>> Git repo
> >>>>> http://git-wip-us.apache.org/repos/asf/wicket.git
> >>>>>
> >>>>> Branch name
> >>>>> build/wicket-1.4.22
> >>>>>
> >>>>> Archived and signed Git repo
> >>>>> https://dist.apache.org/repos/dist/dev/wicket/1.4.22/
> >>>>>
> >>>>> Staging Maven repo:
> >>>
> https://repository.apache.org/content/repositories/orgapachewicket-1001/
> >>>>>
> >>>>> Changelog
> >>>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310561&version=12324070
> >>>>>
> >>>>> This vote ends Tuesday, February 4 at 14:00 (GMT+2)
> >>>>>
> >>>>> Please test the release and offer your vote.
> >>>>>
> >>>>> The Wicket team!
> >>
>

Reply via email to