Hi Roger, > Hmmm. I think the maintenance branch depends on whether there is going to be > a 2.0.3 or not, and how soon we start on 2.1 features. Yes, but a safer approach could be that I create a maintenance branch for 2.0.x (just after 2.0.2 final) and if not needed I can delete it ... BUT to put it in (new) bug-fix only , attention.
> I don't know that we need to make the decision until we start in earnest on > 2.1 stuff. The problem with 2.1 is that there are some really interesting features (more for a 2.5 release than only for 2.1, just to have an idea of planned changes) but where maybe we need to change some API inside, and we really need to start working on it. One of main features to include (and hard/long to write) is the abstraction to AWT for example ... So my trouble here is that I (and probably none of us) has enough time to do a backport of future features/fix from 2.1 (when started in the trunk) to 2.0.x, this is the main reason because I didn't open development of this already. Of course we can even delay (another time) the start on 2.1/2.5 (I like much more 2.5 to better mark it as a real transition to 3.0) ... so my request to other Pivot developers, really what do you think ? > I'm totally swamped by my release schedule, so I don't know if I'll have time > to research / fix the OSX problem for 2.0.2 (I was up until 2:00am last > night....) Ok, don't worry ... Bye
