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 > ------------------------------------------------------------------------------ Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT is a gathering of tech-side developers & brand creativity professionals. Meet the minds behind Google Creative Lab, Visual Complexity, Processing, & iPhoneDevCamp as they present alongside digital heavyweights like Barbarian Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com _______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
