Hi all, Lately I have come into question about just how useful the road map process is. There seems to be little success in using it as a tool to plan out releases and the project short term road map.
Issues are scheduled without discussion unless explicitly asked as part of a road map update email, issues are set priority with no discussion or agreement blocking releases, etc... In short it seems the process is not agile enough or is too restricting for the project. So I don't plan to put any more effort into such a process if it doesn't work. I am also tired of looking like the bad guy when trying to police the policy. In a few cases it has made me look like i am trying to control what goes into GeoServer. Which is ironic because the reason the process was drafted up in the first place was to ensure that no one person or organization had such rights. So unless someone else wants to take this on I don't plan to send any more road map update emails, or work for any sort of structure into the short term road map. Which sort of leaves us in an undefined and arbitrary state in terms of release dates. But I am sure the community will figure it out as it has in the past. -Justin -- Justin Deoliveira OpenGeo - http://opengeo.org Enterprise support for open source geospatial. ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
