Sorry, i meant to change the subject to start a new thread. Justin Deoliveira wrote: > Hi all, > > I have noticed a few things on 1.7.x being committed with a) no issue > for it in the tracker or b) when there is an issue, the commit message > does not reference it. > > Both of these are crucial for generating good change logs and giving > good summaries of what changes in a release. The last few releases I > have found myself wading through commit logs trying to figure out what > has changed which is not all that fun. And trying to link commits to > jira when there is no issue number is even less fun. > > So I am proposing that we make this project policy on stable branches. I > think we can be more lax on trunk. Perhaps this deserves a GSIP? That > might be overkill. I guess I could do a small one. > > Thoughts? > > -Justin > > Andrea Aime wrote: >> Hi all, >> here is the change proposal for RC handling procedures: >> http://geoserver.org/display/GEOS/GSIP+26+-+Long+freeze+handling+procedures >> >> Oh, if you can think of a better title, feel free to change, I could >> not come up with anything better. >> >> If you need to discuss this more please do, otherwise let's start voting. >> >> Cheers >> Andrea >> > >
-- Justin Deoliveira OpenGeo - http://opengeo.org Enterprise support for open source geospatial. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
