Hi Stefan, > In the svn mails I see that some stuff is fixed in trunk while others is > fixed in branches/stable. I did all the fixes in the trunk, then merged them in the 1.5 branch. If you noticed something wrong, please, tell me, I may have misused merge command, as it was the first time. It is quite difficult to follow though, as the same rev number is incremented for trunk commits and for branch commit. > Is there a rule where to do the fixing? If so, is it written somewhere > for OJ developers? From my point of view, the rule is quite simple. All changes are made in the trunk. Fixes are backported in the 1.5 branch, so that 1.5.2 will have no new feature but will be more stable than 1.5.1 for production use. I have made only a small exception with the status bar, jut because I made a bug fix after Peppe did a feature change in the WorkbenchFrame class, so that it would have been more work to backport the bug fix without the feature change. > cheers from Calgary, Cheers,
Michaël > stefan > > ------------------------------------------------------------------------------ > Virtualization& Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > _______________________________________________ > Jump-pilot-devel mailing list > Jump-pilot-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > > ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
