Morning all: So far the email thread on this one has been long on discussion (yeah) and short on modifications to the proposal. I was wondering if we can split this proposal into two in order to make it easier to proceed...
Roadmap ======= I am really keen to both update the existing roadmap and sort out a way for us to maintain this roadmap in the future. This to me is the hardest angle of GSIP 43 - as it involves us sorting out as a community what we are up to so we don't step on each others toes. In order to proceed on this part of GSIP 43 I would like to update the roadmap page this week over email, and IRC if needed to clean up any loose ends. Simone you were talking about doing a monthly IRC on this one - I am not sure if that is needed all the time; but it is probably needed right now as the roadmap does not look at all like what is being planned over the next 6 months. With that in mind I will: a) start a separate roadmap email thread; b) ask for an IRC meeting with Simone later in the week after we have both tried updating the page Release Handling Procedure ===================== So the change here is designating a contact person as the "release manager" - this does not seem that different from what we do now (perhaps it is only writing down what we do now). We need to underline the fact that the release manager is just facilitating the release process - they are not on the hook for fixing problems for example. The email thread highlighted a couple of gaps: - We would love for the release process to be lighter (either by reducing GeoTools to a tag, or skipping steps) - We don't have a schedule of releases Quite frankly I would find it easier to release every month then to sort out the roadmap - it may be less total effort for the community. In terms of alternatives discussed - there is merit in sticking a release step on the end of every accepted major change - it would ensure that the responsibility of making a release is shared around and that the work resulting from each GSIP is releasable. It would however result in more work for those who are growing the application with more work - not a sensible feedback cycle. Mark has time for one more "release", and we can ask for additional time based on our experience. I am willing to release GeoTools for him, or anyone making a GeoServer release in order to minimize overhead. Jody ------------------------------------------------------------------------------ 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 Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
