From my point of view pushing one release back a week isn't a big problem, but less frequent releases might be. One of the aspects of GeoServer that makes it easy to sell to people down here is that any changes or bug fixes that need to be done will be out in a stable release quickly. This means that I'm not deploying and maintaining patched versions for people, and consequently billing them for the effort.
--
Mark
Justin Deoliveira wrote:
A couple of things this week, a couple of issues appearing on the road map. Mostly surrounding the scalability improvements Andrea will be working on:
http://jira.codehaus.org/browse/GEOS-3085
http://jira.codehaus.org/browse/GEOS-3086
http://jira.codehaus.org/browse/GEOS-3087
We also fleshed out some release dates. For beta2 the data in jira was already set to June 15th. We agreed this is probably still acceptable. Any objections to this? Again it would be nice to sync up with Ben on this one.
1.7.5 is scheduled for June 1st, which is probably unrealistic, especially given the features Andrea wishes to start on. Are there any objections to pushing it back a week?
We also discusses the possibility of relaxing the frequency of releases on 1.7.x since it is more or less stable. Perhaps we can switch to a release every 2 months? Thoughts and opinions?
-Justin
Mark Leslie ha scritto:
From my point of view pushing one release back a week isn't a big problem, but less frequent releases might be. One of the aspects of GeoServer that makes it easy to sell to people down here is that any changes or bug fixes that need to be done will be out in a stable release quickly. This means that I'm not deploying and maintaining patched versions for people, and consequently billing them for the effort.
Mark,
I understand your point of view. However, I think this is a case
of a "short blanket" as we call it in Italy: you cover your feet,
your shoulders are not, and vice versa.
As OpenGeo pushes more on the 2.0 series it's normal that less work
is done on the 1.7.x series, we just don't have the resources to
work full steam on both the branches at the same time.
If you need frequent releases we can pair up and share the load,
for example, OpenGeo could make a release one month, and LisaSoft
could make one the next month. Don't underestimate the effort
thought, making a release usually takes at least one day of a core
developer and there are a few wrinkles about cite testing that
are not well explained in the release guide (e.g., we don't use the
cite tests published online since they are very old compared to
the version OGC has developed one year ago and that apparently
is still kept in svn).
But if you're interested in helping out, I'm sure we can find
the time to get you up to speed.
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
I like that analogy and I do understand. Once 2.0 is production ready I fully expect 1.7.x to slow down quickly, but as it's the current stable it seems a shame to let the momentum go already.
I'm willing to cast my hat in the ring for keeping the release pace up at least until 2.0 takes over (from our PoV). I'll have a look over the release guide now to see just what I'm getting myself into and see if there are any gross omissions or places where I'm confused.
Mark Leslie
Geospatial Software Architect
LISAsoft
-------------------------------------------------------------
Ph: +61 2 8570 5000 Fax: +61 2 8570 5099 Mob: +61
Suite 112, Jones Bay Wharf 19-21 Pirrama Rd Pyrmont NSW 2009
-------------------------------------------------------------
LISAsoft is part of the A2end Group of Companies
http://www.ardec.com.au
http://www.lisasoft.com
http://www.terrapages.com
Andrea Aime wrote:
Mark Leslie ha scritto:
From my point of view pushing one release back a week isn't a big problem, but less frequent releases might be. One of the aspects of GeoServer that makes it easy to sell to people down here is that any changes or bug fixes that need to be done will be out in a stable release quickly. This means that I'm not deploying and maintaining patched versions for people, and consequently billing them for the effort.
Mark,
I understand your point of view. However, I think this is a case
of a "short blanket" as we call it in Italy: you cover your feet,
your shoulders are not, and vice versa.
As OpenGeo pushes more on the 2.0 series it's normal that less work
is done on the 1.7.x series, we just don't have the resources to
work full steam on both the branches at the same time.
If you need frequent releases we can pair up and share the load,
for example, OpenGeo could make a release one month, and LisaSoft
could make one the next month. Don't underestimate the effort
thought, making a release usually takes at least one day of a core
developer and there are a few wrinkles about cite testing that
are not well explained in the release guide (e.g., we don't use the
cite tests published online since they are very old compared to
the version OGC has developed one year ago and that apparently
is still kept in svn).
But if you're interested in helping out, I'm sure we can find
the time to get you up to speed.
Cheers
Andrea
So, I've finally gotten the official sign-off from the powers that be to commit LISAsoft to helping out with alternate releases of the 1.7.x series leading up to the 2.0 stable release. Justin was good enough yesterday to point me at the new Release docs and answer some questions. So I suppose my question becomes, when is an appropriate time for such a release?
Mark Leslie
Geospatial Software Architect
LISAsoft
-------------------------------------------------------------
Ph: +61 2 8570 5000 Fax: +61 2 8570 5099 Mob: +61
Suite 112, Jones Bay Wharf 19-21 Pirrama Rd Pyrmont NSW 2009
-------------------------------------------------------------
LISAsoft is part of the A2end Group of Companies
http://www.ardec.com.au
http://www.lisasoft.com
http://www.terrapages.com
Mark Leslie wrote:
I like that analogy and I do understand. Once 2.0 is production ready I fully expect 1.7.x to slow down quickly, but as it's the current stable it seems a shame to let the momentum go already.
I'm willing to cast my hat in the ring for keeping the release pace up at least until 2.0 takes over (from our PoV). I'll have a look over the release guide now to see just what I'm getting myself into and see if there are any gross omissions or places where I'm confused.
Mark Leslie
Geospatial Software Architect
LISAsoft
-------------------------------------------------------------
Ph: +61 2 8570 5000 Fax: +61 2 8570 5099 Mob: +61
Suite 112, Jones Bay Wharf 19-21 Pirrama Rd Pyrmont NSW 2009
-------------------------------------------------------------
LISAsoft is part of the A2end Group of Companies
http://www.ardec.com.au
http://www.lisasoft.com
http://www.terrapages.com
Andrea Aime wrote:
Mark Leslie ha scritto:
From my point of view pushing one release back a week isn't a big problem, but less frequent releases might be. One of the aspects of GeoServer that makes it easy to sell to people down here is that any changes or bug fixes that need to be done will be out in a stable release quickly. This means that I'm not deploying and maintaining patched versions for people, and consequently billing them for the effort.
Mark,
I understand your point of view. However, I think this is a case
of a "short blanket" as we call it in Italy: you cover your feet,
your shoulders are not, and vice versa.
As OpenGeo pushes more on the 2.0 series it's normal that less work
is done on the 1.7.x series, we just don't have the resources to
work full steam on both the branches at the same time.
If you need frequent releases we can pair up and share the load,
for example, OpenGeo could make a release one month, and LisaSoft
could make one the next month. Don't underestimate the effort
thought, making a release usually takes at least one day of a core
developer and there are a few wrinkles about cite testing that
are not well explained in the release guide (e.g., we don't use the
cite tests published online since they are very old compared to
the version OGC has developed one year ago and that apparently
is still kept in svn).
But if you're interested in helping out, I'm sure we can find
the time to get you up to speed.
Cheers
Andrea
Hi Mark,
This is great to hear. More resources available for releases means we can release more often. Woot!
Your email is timely, i was actually just thinking about the next road map update and one of the topics was going to be the time of another 1.7.x release. So i suggest we move the discussion of when to the road map update, as it is the place designed for these type of discussions, and will give everyone a chance to chime in.
Will send the road map update email soon.
-Justin
Mark Leslie wrote:
So, I've finally gotten the official sign-off from the powers that be to commit LISAsoft to helping out with alternate releases of the 1.7.x series leading up to the 2.0 stable release. Justin was good enough yesterday to point me at the new Release docs and answer some questions. So I suppose my question becomes, when is an appropriate time for such a release?
Mark Leslie
Geospatial Software Architect
LISAsoft
-------------------------------------------------------------
Ph: +61 2 8570 5000 Fax: +61 2 8570 5099 Mob: +61
Suite 112, Jones Bay Wharf 19-21 Pirrama Rd Pyrmont NSW 2009
-------------------------------------------------------------
LISAsoft is part of the A2end Group of Companies
http://www.ardec.com.au
http://www.lisasoft.com
http://www.terrapages.com
Mark Leslie wrote:
I like that analogy and I do understand. Once 2.0 is production ready I fully expect 1.7.x to slow down quickly, but as it's the current stable it seems a shame to let the momentum go already.
I'm willing to cast my hat in the ring for keeping the release pace up at least until 2.0 takes over (from our PoV). I'll have a look over the release guide now to see just what I'm getting myself into and see if there are any gross omissions or places where I'm confused.
Mark Leslie
Geospatial Software Architect
LISAsoft
-------------------------------------------------------------
Ph: +61 2 8570 5000 Fax: +61 2 8570 5099 Mob: +61
Suite 112, Jones Bay Wharf 19-21 Pirrama Rd Pyrmont NSW 2009
-------------------------------------------------------------
LISAsoft is part of the A2end Group of Companies
http://www.ardec.com.au
http://www.lisasoft.com
http://www.terrapages.com
Andrea Aime wrote:
Mark Leslie ha scritto:
From my point of view pushing one release back a week isn't a big problem, but less frequent releases might be. One of the aspects of GeoServer that makes it easy to sell to people down here is that any changes or bug fixes that need to be done will be out in a stable release quickly. This means that I'm not deploying and maintaining patched versions for people, and consequently billing them for the effort.
Mark,
I understand your point of view. However, I think this is a case
of a "short blanket" as we call it in Italy: you cover your feet,
your shoulders are not, and vice versa.
As OpenGeo pushes more on the 2.0 series it's normal that less work
is done on the 1.7.x series, we just don't have the resources to
work full steam on both the branches at the same time.
If you need frequent releases we can pair up and share the load,
for example, OpenGeo could make a release one month, and LisaSoft
could make one the next month. Don't underestimate the effort
thought, making a release usually takes at least one day of a core
developer and there are a few wrinkles about cite testing that
are not well explained in the release guide (e.g., we don't use the
cite tests published online since they are very old compared to
the version OGC has developed one year ago and that apparently
is still kept in svn).
But if you're interested in helping out, I'm sure we can find
the time to get you up to speed.
Cheers
Andrea
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.