Hi all! I just wanted to remind you that we are planning to tag OpenSAF 4.4.FC in the beginning of January. This means that if you are taking a holiday over Christmas, there is effectively only three weeks left for implementing enhancements that will go into OpenSAF 4.4. After 4.4.FC has been tagged, only bug fixes are supposed to go into the 4.4 branch.
One other thing that we are planing to do in conjunction with the 4.4.FC tagging is to run a script that reindents the code. This will fix things like wrong indentation, wrong use of tabs vs. spaces, and trailing white space at the end of the lines. The idea of doing it at this point in time is that most big patches should have been pushed by then, and thus we are minimizing the work of re-basing patches. If you have a patch that has not been pushed, it should however still be possible to apply it using the --ignore-whitespace option to the patch command. Finally, I noted that there are a lot of defect tickets that have the 4.4.FC milestone. Normally, a defect ticket should be fixed on all applicable branches that we are still supporting. So one would expect that most defects should have the 4.2.5 milestone. Please check your tickets and make sure that the only defect tickets with the 4.4.FC milestone are defects for new functionality that is not present on earlier branches. regards, Anders Widell ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk _______________________________________________ Opensaf-devel mailing list Opensaf-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-devel
