2007/6/2, Arnout Engelen <[EMAIL PROTECTED]>:
(clip)
I'd like to commit them for some broader testing and feedback, but the
code does trigger an unresolved bug (the BasicSelectionCommand thing I
mailed about earlier).
(clip)
Arnout
The pocily is same than for the policy for releasing stable releases:
If you have something valuable and you don't introduce a new or an old
bug, you are free to commit (or release a new stable release).
So, if your patch just makes a known bug more visible, you are free to
commit. I expect that this is your position, then just go on.
Typically if the code does not work very well, the functionality is hidden
somewhere in the gui for testing purposes (this may have been the case with
the guitar tabs), until most critical bugs are being fixed. In your case,
this would mean that the new toolbar would not be shown by default. If you
have a new gui property which is not tested or it contains some bugs, mark
it as EXPERIMENTAL in the gui. Then the users knows that if they use the new
functionality, they have to be careful and maybe save the work before
trying. When the bug is fixed, the word EXPERIMENTAL is removed from the
i18n strings.
Now we are in development mode. Bugfixing mode is when "string freeze" mode
is published. However, the submitting policy with the rosegarden project is
that the code should always be compilable.
--
Heikki
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Rosegarden-devel mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-devel
