Jody Garnett wrote: > The related GeoTools policy is here: suggestions on "visibility and > enforcement" are welcome > - http://docs.codehaus.org/display/GEOT/Working+on+a+stable+branch its a bit vague about the requirement to port fixes forward - merely describes this as "nice". I'd start of by making the case that fixes _must_ be pushed into trunk, and even that even if you have a patch working on a branch, the committing process should be to commit to trunk (with tests) first.
Maybe the point about "saving up a few" is valid, but perhaps this shuld apply to the branches as well. Current practive follows the policy AFAICT - goodwill but indefinite timelines to actually port forward. RnD branches probably dont need to follow this, but where they uncover issues they should still push fixes to trunk, and if the amount of work is too great because of wierdness in the RnD codebase, at least register a Jira issue on trunk ? >> >> >> Rob Atkinson >> ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
