This message will probably be of most interest to Stefan, but I wanted to include the other developers as well.
I know Stefan has been doing the majority of the work integrating new features in Vivid's JUMP and other JUMP brands into OpenJUMP. With the release of Vivid's JUMP 1.2 it looks like there is now a lot more work to do! I'd like to offer my assistance to Stefan this go around, if he needs it. I know we'll need a couple of weeks to test out the new JUMP, and then we'll need to figure out what things in Vivid's JUMP 1.2 will go into OpenJUMP, and what we'll keep out. Then there is also the task of internationalizing what goes in. (If Vivid hasn't done this already.) I'll just offer my help to Stefan, and let him direct me as needed. I would like to suggest a list on one of the wiki's that shows which classes have been added or changed from the last version of Vivid's JUMP to this new version. I think it will be important to track these changes to Vivid's code base as time moves on. I sent an e-mail to Martin at Vivid asking about how we can better coordinate the development of JUMP and OpenJUMP in the future, but he hasn't had time to get back to me. I think he may have some useful input on this process as well. At a minimum I'd like to strive for the following: [1] As much similarity between the 2 code bases as reasonable and possible. [2] Good documentation of the differences between the code bases when these differences are necessary because of the different goals of Vivid Solutions and the JUMP Pilot Project. I can start work on this list of Stefan and the other OpenJUMP developers think it is a good idea. I was also wondering how the announcement of Vivid's JUMP 1.2 will affect our release schedule for OpenJUMP. I was thinking about a release in the first part of 2007, as I will have some time of work at the end of December. Should we push this back until spring so we can include the changes available in JUMP 1.2? Or do you think there is reason enough to provide an intermediate release? If Stefan doesn't need much help with incorporating the changes from Vivid's JUMP 1.2 I can probably have the first version of the SurveyOS Cursor Tool code ready to go by the end of December, but I don't know if that justifies a release in itself. Has there been enough bug fixes to put out an "official" public release of OpenJUMP for the non-developers? I know Stefan and the other developers are very busy. I think I can handle the majority of the work for a January 2007 release if we decide not to wait. The Sunburned Surveyor P.S. - I'll try to get a blog post about Vivid's JUMP 1.2 this weekend if I can squeeze it in. ------------------------------------------------------------------------- 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 _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
