Incubator release and what now?

[Martijn Dashorst <ma...@gmail.com>]

We have some feedback on the release and should work on resolving
that. There are several avenues we can walk to fix it.

- fix the release branch and re-issue that (requires some backporting
of threadtest iirc)
- port the release stuff to the 1.x branch, and cut a new release

I think I prefer fixing the release branch, get it vetted and then
backport the release stuff to branch 1.x. This is the shortest way to
getting ratified IMO.

wdyt?

Martijn

-- 
Learn Wicket at ApacheCon Europe: http://apachecon.com
Join the wicket community at irc.freenode.net: ##wicket
Wicket 1.2.5 will keep your server alive. Download Wicket now!
http://wicketframework.org

Re: Incubator release and what now?

[Martijn Dashorst <ma...@gmail.com>]

On 4/2/07, Jean-Baptiste Quenot <jb...@apache.org> wrote:
> I would have put the release stuff in the 1.x branch in the first
> place.  Now that it ended up there, the sooner it comes back to
> 1.x the better.

No, because you don't want to build a release against a moving target,
which the 1.x branch clearly is. The decision was made conciously to
fork the release, get that stable and then push the results to the 1.x
branch.

We explicitly decided to split the effort of backporting stuff from
trunk and the effort of graduation.

Martijn

-- 
Learn Wicket at ApacheCon Europe: http://apachecon.com
Join the wicket community at irc.freenode.net: ##wicket
Wicket 1.2.5 will keep your server alive. Download Wicket now!
http://wicketframework.org

Re: Incubator release and what now?

[Jean-Baptiste Quenot <jb...@apache.org>]

* Martijn Dashorst:
> We have some feedback on the release and should work on resolving
> that. There are several avenues we can walk to fix it.
> 
> - fix the release branch and re-issue that (requires some backporting
> of threadtest iirc)
> - port the release stuff to the 1.x branch, and cut a new release
> 
> I think I prefer fixing the release branch, get it vetted and then
> backport the release stuff to branch 1.x. This is the shortest way to
> getting ratified IMO.

Hi Martijn,

I would have put the release stuff in the 1.x branch in the first
place.  Now that it ended up there, the sooner it comes back to
1.x the better.


For those who wonder what feedback we are talking about, this is
on the incubator-general mailing-list:

http://www.nabble.com/-VOTE--Ratify-the-release-of-Apache-Wicket-1.3.0-incubating-alpha-tf3491229.html
-- 
     Jean-Baptiste Quenot
aka  John Banana   Qwerty
http://caraldi.com/jbq/

Re: Incubator release and what now?

[Eelco Hillenius <ee...@gmail.com>]

> We have some feedback on the release and should work on resolving
> that. There are several avenues we can walk to fix it.
>
> - fix the release branch and re-issue that (requires some backporting
> of threadtest iirc)
>
> - port the release stuff to the 1.x branch, and cut a new release
>
> I think I prefer fixing the release branch, get it vetted and then
> backport the release stuff to branch 1.x. This is the shortest way to
> getting ratified IMO.
>
> wdyt?

Whatever works best for you. Those fixes are tiny and they're in 1.3.

Eelco