> That is what I meant. Now that we have stable fltk1, we can > 1) Adding new bugs to it through adding new features
1.1.9 is closed. Unless someone finds a show-stopper, it will be that way forever. We don't expect there ever to be a 1.1.10. Any new 1.x style work will go into the experimental 1.3 tree, in an attempt to move the 1.x and 2.x series back together, but without orphaning the huge amount of 1.1.x code that is extant in the wild, and without giving up 1.1.x's much vaunted stability. > 2) Adding new bugs to it through merging with fltk2 > Both 1) and 2) add bugs, and add features. The key difference is that > after 2) we'll have two times less projects to improve and maintain. Someone needs to take up 2.x and start fixing the bugs, particularly the bugs that were fixed years ago in 1.1.x, and even more so the ones that *were* fixed and have been re-broken. Then, maybe, we can look at moving the 1.3 and 2.x trees together. I haven't the time, nor the stength of will, to undertake that task, but if somebody will, that would be a Good Thing. SELEX Sensors and Airborne Systems Limited Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
