Hi
we should start thinking about what we want in a future 1.0 release and what we want to postpone. I think we should not add many features (also if useful) now if we don't want to go on with betas forever.
I tried looking at all the bugs on sf bugtracker, and assigning a "planned for 1.0" or "after 1.0" group to all items. These are the bugs/FRs I marked to be fixed for 1.0:
http://sourceforge.net/tracker/index.php?group_id=73068&atid=536613&set=custom&_status=1&_group=377833
http://sourceforge.net/tracker/index.php?group_id=73068&atid=536616&set=custom&_status=1&_group=377835
The logic used to mark items for 1.0 was:
- everything is a real bug (=doesn't work as intended) in actual releases;
- simple things that can't break other functionalities;
- changes needed to make the library more customizable which is better to release before 1.0 (code changes which doesn't affect current functionalities).
Please let me know if you think that any other item MUST be addressed before 1.0. I hope we will be able to fix all these items for b3, release it and then working only on bugs before releasing 1.0.
fabrizio
