Jesse Eichar wrote: > More problems with trunk :-(. I was merging some code from 2.2 onto > trunk. And I discovered that the method: FeatureStore.addFeatures > (FeatureCollection) is missing. Whoever added that method onto 2.2 > did not merge it onto trunk as well. > I made that change and applied it in both places as far as I know :-( I do hope it was not clobbered. > Now this isn't a big deal but it makes one wonder how many other > major changes like that are being merged. If have branches we HAVE > TO (in double quotes and with exclamations) merge all of our changes > onto trunk. I know that many changes from 2.1 didn't get merged onto > trunk and as a result now are not on trunk or 2.2.x. I know it takes > longer to make changes if you have to merge it to trunk. But how > much longer does it take to have to find the same bugs for every > version and fix it? > I think what we need to do is use Jira to track these things, and include Jira numbers in any commit that is not on trunk. That is the only coding that should be happening on the stable branches should be fixes, and the commits should contain jira numbers.
So given that we screwed up with 2.2.x - being marked stable without a release, allowing continued development etc... I imagine a fair bit has fallen through the cracks. > So a big PLEASE remember to correctly put changes on trunk when you > add a patch to a branch. > Thanks for the reminder Jesse, can I also add that please remember to include a jira number with your commit. Jody ------------------------------------------------------------------------- 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
