https://bugs.freedesktop.org/show_bug.cgi?id=78229
tommy27 <ba...@quipo.it> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution|--- |FIXED
Version|4.2.3.3 release |4.2.0.4 release
--- Comment #6 from tommy27 <ba...@quipo.it> ---
@NoOp
no this is not the correct procedure.
1- don't change the version number
it should always indicate tghe first release where the bug has been
reproduced.+
in this case: 4.2.0.4
2- once a bug is fixed in a codeline it should mark as RESOLVED, and not
REOPENED, even if it's still present in the current codeline and fixed just in
the development branch. and is labeled as FIXED if we know the committ that did
it, or WORKSFORME if we don't know which one did.
good or bad, these are the rules here :-)
sometimes a fix which is in the 4.3.x line cannot always be easily backported
to the 4.2.x (there are some fix that are the result of very drastical code
change and cannot be applied to old branch)
maybe if you are lucky the fix is already in a future 4.2.x release (you may
try downloading a 4.2.4 RC1 or a 4.2.5 master from prerelease and daily builds
page) to see if it's already there but in the worst case, you will have to wait
for 4.3.0 final release which is end of july 2014.
here some links in case you don't know have them at hand:
http://www.libreoffice.org/download/pre-releases/
http://dev-builds.libreoffice.org/daily/libreoffice-4-2/
https://wiki.documentfoundation.org/ReleasePlan
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
