You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by Martijn Dashorst <ma...@gmail.com> on 2007/01/29 23:36:50 UTC

Practice 1.3-beta1 release using 1.2.5

However, I'll publish the distributions before I deploy to an external
repository. Say that we do the final on monday, after *we* checked the
release (better practice our skills at that with this release)?

I'll do the release using our old distribution packages. Can anyone
download those and check them with rat? We will get a lot of errors,
but the idea is that we follow the ASF release methodology.

Which steps are needed?
 - build release
 - sign release (mvn pgp?)
 - check release (rat, manual?)
 - release release

Martijn

On 1/29/07, Martijn Dashorst <ma...@gmail.com> wrote:
> Fixing the pom is part of the release process. So that can't be done upfront.
>
> Martijn
>
> On 1/29/07, Johan Compagner <jc...@gmail.com> wrote:
> > aren't there any any any other really really need to have fixes?
> > (except now have the right pom also ;) )
> >
> > because i really hope that 1.2 could be finished then!
> >
> > johan
> >
> >
> > On 1/29/07, Martijn Dashorst <ma...@gmail.com> wrote:
> > >
> > > It is almost februari and we need some time to resolve a vote (and
> > > prepare a release). This is a vote to release the 1.2.5 Wicket branch
> > > on sourceforge, to fix some nasty hairy bugs out there. Are all issues
> > > resolved for 1.2.5?
> > >
> > > Release Notes - Wicket - Version 1.2.5
> > >
> > > Bug:
> > > * [WICKET-188] - Header contribution is sometimes not rendered after the
> > > request
> > > * [WICKET-218] - Removing comments from markup can fail
> > > * [WICKET-242] - Modal Window always creates new cookies
> > >
> > > The release would be performed this weekend (first weekend of Februari).
> > >
> > > [ ] yes, bug-b-gone my Wicket
> > > [ ] no, I still have some critters to deal with
> > >
> > > PS. is 1.2.x already under the bamboo build umbrella?
> > >
> > > Martijn
> > >
> > > --
> > > Vote for Wicket at the
> > > http://www.thebeststuffintheworld.com/vote_for/wicket
> > > Wicket 1.2.4 is as easy as 1-2-4. Download Wicket now!
> > > http://wicketframework.org
> > >
> >
> >
>
>
> --
> Vote for Wicket at the http://www.thebeststuffintheworld.com/vote_for/wicket
> Wicket 1.2.4 is as easy as 1-2-4. Download Wicket now!
> http://wicketframework.org
>


-- 
Vote for Wicket at the http://www.thebeststuffintheworld.com/vote_for/wicket
Wicket 1.2.4 is as easy as 1-2-4. Download Wicket now!
http://wicketframework.org

Re: Practice 1.3-beta1 release using 1.2.5

Posted by Eelco Hillenius <ee...@gmail.com>.
On 2/3/07, Martijn Dashorst <ma...@gmail.com> wrote:
> That was the vote for (last monday).

Yeah, but not with a lot of results it looked like, so I wanted to
help a bit keeping the idea of practicing alive?

Eelco

Re: Practice 1.3-beta1 release using 1.2.5

Posted by Martijn Dashorst <ma...@gmail.com>.
That was the vote for (last monday).

On 2/2/07, Eelco Hillenius <ee...@gmail.com> wrote:
> On 1/29/07, Martijn Dashorst <ma...@gmail.com> wrote:
> > However, I'll publish the distributions before I deploy to an external
> > repository. Say that we do the final on monday, after *we* checked the
> > release (better practice our skills at that with this release)?
> >
> > I'll do the release using our old distribution packages. Can anyone
> > download those and check them with rat? We will get a lot of errors,
> > but the idea is that we follow the ASF release methodology.
> >
> > Which steps are needed?
> >  - build release
> >  - sign release (mvn pgp?)
> >  - check release (rat, manual?)
> >  - release release
> >
>
> Sounds like a plan. When do you want to do it? This weekend?
>
> Eelco
>


-- 
Vote for Wicket at the http://www.thebeststuffintheworld.com/vote_for/wicket
Wicket 1.2.4 is as easy as 1-2-4. Download Wicket now!
http://wicketframework.org

Re: Practice 1.3-beta1 release using 1.2.5

Posted by Eelco Hillenius <ee...@gmail.com>.
On 1/29/07, Martijn Dashorst <ma...@gmail.com> wrote:
> However, I'll publish the distributions before I deploy to an external
> repository. Say that we do the final on monday, after *we* checked the
> release (better practice our skills at that with this release)?
>
> I'll do the release using our old distribution packages. Can anyone
> download those and check them with rat? We will get a lot of errors,
> but the idea is that we follow the ASF release methodology.
>
> Which steps are needed?
>  - build release
>  - sign release (mvn pgp?)
>  - check release (rat, manual?)
>  - release release
>

Sounds like a plan. When do you want to do it? This weekend?

Eelco