hello Jody, my comments are in-lined
Jody Garnett wrote: >>> current GeoServer is at version 2.0 (unstable) / 1.7.6 (stable), we have >>> installations out there that have GeoServer versions 1.5.4b and 1.6.4b! >> Both dead for a long time >> > Dead may be too strong a word; a critical patch done for a paying > customer would be fine. The difficulty is that the developers no > longer have a checkout; so there is an over head associated with > grabbing the code; making a fix; deploying it for someone to test; and > then finally issuing a dot release. These overheads add up restricting > it to a paid activity. > > It is also worth noting that these overheads are not present in when > working on trunk since a release will be coming out later in the > month; making it much cheaper for everyone to be involved. noted. i was trying to make the point that there's a time lag between a release of a (really stable) version of GeoServer and a similar one for a product that includes that version. in my case the product in question does not have a once-a-month release. >>> * 2-3 days testing is not enough. for my type of application, at least >>> 1-week is more like it. having a 4-6 weeks notice would also mean that >>> this testing period can be better planned. > > From our standpoint it is worth asking you to put in that kind of > effort for the 2.0 release. My fear is that your team will try testing > in earnest after the release has gone out when it is much more > expensive to fix; especially with respect to any API changes. > > If your team can test your application against a "sample" 2.0 release > the changes between 2.0.1, 2.0.2 etc will be much smaller in nature. > >> bug fixes to the 1.7.x series and make releases. Lisasoft expressed >> some interest in that and is helping with the current 1.7.x releases, >> which the dev team would have already abandoned otherwise (so thank >> you Lisasoft, 1.7.6 might not have been there without your help). > > We are actual in the same neck of the woods as Raif - so if you want > to join us in making the next 1.7.x release come on over and we will > buy beer. cool! moving from 1.5/1.6 to 1.7 sounds less risky for me than to 2.0 right now. spending time on testing 1.7 releases in my case is a better value proposition. let me know when the next round is about to start. > Actually Raif I am having trouble hunting down a location for an extra > day of code sprint. If possible I would like to corner the deegree > developers and get an initial cut of the geometry module out while > everyone is in the same city. Is there any chance we could hack at > your offices on the Sunday after the conference? i'll talk to you about this off the list. >> As an alternative there are commercial support companies that can >> be "persuaded" to port back selected bug fixes and make further releases >> out of dead branches. > > Just so. cheers; rsn ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
