Hi all,
On the heals of the 1.7.6 (thanks again Mark!) and looking forward:
* 2.0-RC1 release date
So last weeks update we pushed this back by a week, putting the relase Aug 10, next week. Are we still good to go? Or any problems with this date? Only one critical issue left open which seems to be minor, so unless their are any high priority issues that are not marked as so it would appear things are on track.
* 1.7.7 release date
Probably a bit early to attach a date. But begs the question which we have sort of been going back and forth on, and that is do we want to continue to shoot for a roughly monthly release cycle? Or drop back to every 2 months? I am not sure we came to a conclusion last time this came up.
* 2.0-RC1 outstanding issues
Only one issue outstanding:
http://jira.codehaus.org/browse/GEOS-3170, jdeolive
Setting number of decimals on feature type page does not persist
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Justin Deoliveira ha scritto:
Hi all,
On the heals of the 1.7.6 (thanks again Mark!) and looking forward:
* 2.0-RC1 release date
So last weeks update we pushed this back by a week, putting the relase Aug 10, next week. Are we still good to go? Or any problems with this date? Only one critical issue left open which seems to be minor, so unless their are any high priority issues that are not marked as so it would appear things are on track.
Yup, sounds like it.
* 1.7.7 release date
Probably a bit early to attach a date. But begs the question which we have sort of been going back and forth on, and that is do we want to continue to shoot for a roughly monthly release cycle? Or drop back to every 2 months? I am not sure we came to a conclusion last time this came up.
I guess this is pretty much in the hands of whoever is actually
doing the releases. Mark what do you think? 
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Andrea Aime wrote:
Justin Deoliveira ha scritto:
Hi all,
On the heals of the 1.7.6 (thanks again Mark!) and looking forward:
* 2.0-RC1 release date
So last weeks update we pushed this back by a week, putting the relase Aug 10, next week. Are we still good to go? Or any problems with this date? Only one critical issue left open which seems to be minor, so unless their are any high priority issues that are not marked as so it would appear things are on track.
Yup, sounds like it.
* 1.7.7 release date
Probably a bit early to attach a date. But begs the question which we have sort of been going back and forth on, and that is do we want to continue to shoot for a roughly monthly release cycle? Or drop back to every 2 months? I am not sure we came to a conclusion last time this came up.
I guess this is pretty much in the hands of whoever is actually
doing the releases. Mark what do you think?
Cheers
Andrea
Well, I've gotten sign off from on-high for three releases at two month intervals. I don't see it being a problem if we change that to one month intervals, but I'll need to request more time once I've done three and there are no guarantees there. So I'll need to leave it up to you to make sensible use of me; I've got no problem doing another round in a month(ish). Left to my own devises, I'll stick with our script and leave it two months.
Mark Leslie ha scritto:
Well, I've gotten sign off from on-high for three releases at two month intervals. I don't see it being a problem if we change that to one month intervals, but I'll need to request more time once I've done three and there are no guarantees there. So I'll need to leave it up to you to make sensible use of me; I've got no problem doing another round in a month(ish). Left to my own devises, I'll stick with our script and leave it two months.
Two months sounds good to me. As Justin suggested, the 1.7.x branch should be stable and low change enough that if a user needs a fix
urgently (that has already been committed) she can just grab a nightly.
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.