Hi all, Today at the meeting we decided that we want to work towards a stable release. Right now we have had RCs which had fundamental changes in code between the two. This means that it was not obvious if RC2 is more stable than RC1, since half of the code is new. The reason for this is obviously the OL integration process we decided upon halfway. However we have finished this process and we can work towards a stable release now. This means that every new release should have more bugs fixed and more tests written to prove that it is more stable. Also it means that trunk should continue to become more stable. This also means that we cannot keep adding new features to trunk, without finishing the existing functions.
However, we probably do not want to stop developing and we should decide what we are going to until the next release, both in trunk and outside trunk. Previously we had a stable branch and trunk, but this was found to be a painful solution, since trunk was diverging from the stable branch quickly and it was difficult to keep both synced where possible. So what I like to do is to start a discussion what features we want to fix/finish/develop for the stable release and what features are left for the next stable release, and possibly being developed in a sandbox. My list contains: -Make sure all demos work -Tests for all demos (makes it easier to see if the first item is true) -Crossbrowser compatibility -Memory leaks -Simplified getFeatureInfo I'd like to hear your thoughts on this Steven ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ mapbuilder-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mapbuilder-devel
