Forwarding this message from the geotools-devel list.
Justin, is this still the plan for this week? to release geoserver 1.7.0 by
the end of this week?
I first noticed today while reading pending messages on the geoserver devel
list. Don't remember if it was mentioned on yesterday's geoserver irc meeting
though.
Yet, if we're going for a geoserver release shouldn't we communicate with
enough anticipation. Setting a due date for the release on jira would also be
fine. I guess my point is just please guys lets communicate earlier. Not
really sure if a week is enough planning for a release, but if so I would of
needed to notice last week and not today with two days remaning.
What could we do to improve this sort of communication gap? can we set at
least a policy to email the geoserver-devel list with a week of anticipation
when a release is comming? or any other approach you may consider better.
Best regards,
Gabriel
On Friday 15 August 2008 02:15:03 pm Justin Deoliveira wrote:
Hi all,
We will be releasing the 1.7.0 release candidate of GeoServer later
today. Barring any major issues with it we hope to release the official
1.7.0 at the end of next week. In the meantime we need to release
geotools 2.5.0. So i wanted to start the wheels in motion.
There are still a number of issues still open in jira for 2.5.0-RC1 and
2.5.0, but no blockers. However I know Jody has some tasks he wants to
perform before 2.5.0 goes out.
-Justin
Hi Gabriel,
Well nothing is really set in stone for GeoServer... since releasing depends on issues that come up with RC1. I thought I did send email last week after releasing RC1 that we wanted to get a gt release out this week, in anticipation for a possible geoserver release the week after barring no issues with RC1.
But yeah, apologies for not making this more clear. I think your suggestion of both using jira and an email to the devel list a week before are good ideas. I will try to be better on communicating this.
Gabriel Roldán wrote:
Forwarding this message from the geotools-devel list.
Justin, is this still the plan for this week? to release geoserver 1.7.0 by the end of this week?
I first noticed today while reading pending messages on the geoserver devel list. Don't remember if it was mentioned on yesterday's geoserver irc meeting though.
Yet, if we're going for a geoserver release shouldn't we communicate with enough anticipation. Setting a due date for the release on jira would also be fine. I guess my point is just please guys lets communicate earlier. Not really sure if a week is enough planning for a release, but if so I would of needed to notice last week and not today with two days remaning.
What could we do to improve this sort of communication gap? can we set at least a policy to email the geoserver-devel list with a week of anticipation when a release is comming? or any other approach you may consider better.
Best regards,
Gabriel
On Friday 15 August 2008 02:15:03 pm Justin Deoliveira wrote:
Hi all,
We will be releasing the 1.7.0 release candidate of GeoServer later
today. Barring any major issues with it we hope to release the official
1.7.0 at the end of next week. In the meantime we need to release
geotools 2.5.0. So i wanted to start the wheels in motion.
There are still a number of issues still open in jira for 2.5.0-RC1 and
2.5.0, but no blockers. However I know Jody has some tasks he wants to
perform before 2.5.0 goes out.
-Justin
--
Justin Deoliveira
Software Engineer, OpenGeo
http://opengeo.org
On Wednesday 20 August 2008 03:48:42 pm Justin Deoliveira wrote:
Hi Gabriel,
Well nothing is really set in stone for GeoServer... since releasing
depends on issues that come up with RC1. I thought I did send email last
week after releasing RC1 that we wanted to get a gt release out this
week, in anticipation for a possible geoserver release the week after
barring no issues with RC1.
hmm... I guess I missunderstood what you meant for "next" week so, and since
you sent the email last Friday I thought the release were due _this_ week,
but it could also be interpreted like the week after the geotools release..
sorry about that, false alarm on my side...
But can we have the geoserver-devel list as the mandatory place where to
communicate this sort of stuff? I mean, I know we topp'ers are running things
for the most part, but geos-dev keeps being the appropriate place imho.
Cheers,
Gabriel
But yeah, apologies for not making this more clear. I think your
suggestion of both using jira and an email to the devel list a week
before are good ideas. I will try to be better on communicating this.
Gabriel Roldán wrote:
> Forwarding this message from the geotools-devel list.
>
> Justin, is this still the plan for this week? to release geoserver 1.7.0
> by the end of this week?
> I first noticed today while reading pending messages on the geoserver
> devel list. Don't remember if it was mentioned on yesterday's geoserver
> irc meeting though.
>
> Yet, if we're going for a geoserver release shouldn't we communicate with
> enough anticipation. Setting a due date for the release on jira would
> also be fine. I guess my point is just please guys lets communicate
> earlier. Not really sure if a week is enough planning for a release, but
> if so I would of needed to notice last week and not today with two days
> remaning.
>
> What could we do to improve this sort of communication gap? can we set at
> least a policy to email the geoserver-devel list with a week of
> anticipation when a release is comming? or any other approach you may
> consider better.
>
> Best regards,
>
> Gabriel
>
> On Friday 15 August 2008 02:15:03 pm Justin Deoliveira wrote:
>> Hi all,
>>
>> We will be releasing the 1.7.0 release candidate of GeoServer later
>> today. Barring any major issues with it we hope to release the official
>> 1.7.0 at the end of next week. In the meantime we need to release
>> geotools 2.5.0. So i wanted to start the wheels in motion.
>>
>> There are still a number of issues still open in jira for 2.5.0-RC1 and
>> 2.5.0, but no blockers. However I know Jody has some tasks he wants to
>> perform before 2.5.0 goes out.
>>
>> -Justin