Hi, >> i am growing more and more convinced that the stable branch is a waste of >> effort. how about moving back to trunk and add a 'option setting'/'cmd line >> switch' for experimental features? but actually i feel that all this is not >> necessary and we could add new functions all the time and simply point them >> out in the release notes, so users don't expect them to be very robust. > It turned to be a waste of effort because most of the work done since > 1.5.1 has been bug fixes. I was hoping that some more innovative changes > would have started in the trunk in the same time, but it did not > happened :-( > Maybe we'll stop this experiment after 1.5.2. I would agree, having things unbranched is easier to handle for me ; - but its your choice.
>> >> in my other project with major.minor.patch version scheme i keep it like this >> major breaks backward compatibility >> minor adds new functionality >> patch fixes bugs > Still agree with this scheme. I do too > I ask for the zoom as it is a case where we did not do what we decided > for vers. 1.5.1, so we must decide how to manage this feature for 1.5.2 ;-) rather switch off? > Nice information. Don't know the difference between check and loading, > but dependency analysis seem more time-consuming than jar-size. seems like it actually is better to have a slow machine, as the figure returned are much easier to read ;) What is the time to load sextante only without any other plugin? stefan PS: did you guys know that I am now only 5h behind europe? ... but i am on mobile (infrequent/low bandwidth) internet = USB stick ------------------------------------------------------------------------------ Better than sec? Nothing is better than sec when it comes to monitoring Big Data applications. Try Boundary one-second resolution app monitoring today. Free. http://p.sf.net/sfu/Boundary-dev2dev _______________________________________________ Jump-pilot-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
