I wanted to send a quick email to just make sure everyone is on the same
page with regard to branch maintenance. A the moment we have 3 branches:
1.7.x
2.0.x
trunk
It seems that 1.7.x is close to going into unmaintained mode? Or perhaps
just fix super critical show stopper mode? Or are we intend to continue
to maintain the branch?
As for 2.0.x. i just want to remind/confirm our policy is still that any
bug fixes and "stable improvements" that go into trunk also go into
2.0.x? Looking over the commit logs I have seen a recent commit to trunk
without a corresponding commit to 2.0.x. So just wanted to clarify.
-Justinx
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Had a good discussion about 1.7.x with Mark and Andrea. I would like
to put one more 1.7.x out; but schedule it for 6 months from now in
order to communicate that nobody should be planning for additional
1.7.x releases any time soon.
Jody
On Mon, Nov 2, 2009 at 9:04 PM, Justin Deoliveira <jdeolive@anonymised.com> wrote:
Hi all,
I wanted to send a quick email to just make sure everyone is on the same
page with regard to branch maintenance. A the moment we have 3 branches:
1.7.x
2.0.x
trunk
It seems that 1.7.x is close to going into unmaintained mode? Or perhaps
just fix super critical show stopper mode? Or are we intend to continue
to maintain the branch?
As for 2.0.x. i just want to remind/confirm our policy is still that any
bug fixes and "stable improvements" that go into trunk also go into
2.0.x? Looking over the commit logs I have seen a recent commit to trunk
without a corresponding commit to 2.0.x. So just wanted to clarify.
-Justinx
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
As for 2.0.x. i just want to remind/confirm our policy is still that any
bug fixes and "stable improvements" that go into trunk also go into
2.0.x? Looking over the commit logs I have seen a recent commit to trunk
without a corresponding commit to 2.0.x. So just wanted to clarify.
Ah, I'm one that forgot to backport some to 2.0.x, gonna do. Thanks for reminding.
Gabriel
-Justinx
--
Gabriel Roldan
OpenGeo - http://opengeo.org
Expert service straight from the developers.
I wanted to send a quick email to just make sure everyone is on the same
page with regard to branch maintenance. A the moment we have 3 branches:
1.7.x
2.0.x
trunk
It seems that 1.7.x is close to going into unmaintained mode? Or perhaps
just fix super critical show stopper mode? Or are we intend to continue
to maintain the branch?
As for 2.0.x. i just want to remind/confirm our policy is still that any
bug fixes and "stable improvements" that go into trunk also go into
2.0.x? Looking over the commit logs I have seen a recent commit to trunk
without a corresponding commit to 2.0.x. So just wanted to clarify.
I think that 1.7.x will be abandoned as a result of people working already on the 2.0.x and 1.7.x branches, and the fact that
working over 3 branches is just painful.
So I guess that there won't be any more work on 1.7.x besides work
that has specific funding going into that direction (at least, this
is what is going to happen for me )
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
I wanted to send a quick email to just make sure everyone is on the same
page with regard to branch maintenance. A the moment we have 3 branches:
1.7.x
2.0.x
trunk
It seems that 1.7.x is close to going into unmaintained mode? Or perhaps
just fix super critical show stopper mode? Or are we intend to continue
to maintain the branch?
As for 2.0.x. i just want to remind/confirm our policy is still that any
bug fixes and "stable improvements" that go into trunk also go into
2.0.x? Looking over the commit logs I have seen a recent commit to trunk
without a corresponding commit to 2.0.x. So just wanted to clarify.
I think that 1.7.x will be abandoned as a result of people working already on the 2.0.x and 1.7.x branches, and the fact that
working over 3 branches is just painful.
So I guess that there won't be any more work on 1.7.x besides work
that has specific funding going into that direction (at least, this
is what is going to happen for me )
Cheers
Andrea
Unless some big issues or funding happen in the 1.7.x world, the only reason I could see for the last release is to publicise it loudly as "The Last Release" of that branch. I think six months from now sounds reasonable; we should have enough 2.0.x's out by then to convince the laggers.
)