On 14/01/2007, at 4:02 AM, Caio Tiago Oliveira wrote:
1.1 bugs are trivial to handle, it's just to close them if they don't apply to 2.0, off course.1.1 RFE's are usually handled the same way.But RFE's are quite different, since they don't apply to some specific version of the product.As stated in the bug writing guidelines<http://www.openoffice.org/ bugs/bug_writing_guidelines.html>, the version should be the one you first find the issue (if applicable).From my point of view, it's not applicable for requests of new enhancements or features.My purpose is, after confirming they still required, either: use current as the version or: change it to 2.0.Since makes more sense the "version" for an enhancement or feature means the version to which it's applicable, than a specific version (always major versions, by the way, never 2.1.1 or so on).Anyone dislike it or have a better solution?
This actually sounds like something I could help with. :D (It frustrates me very much that I can't do any code. :( )So we could hold a BSP [1] or simply go through a certain number of 1.1 bugs each (e.g. 5 a day), either closing them or reassigning them to version 2?
That could get rid of a lot of old cruft in the issue tracker.When I look at issues, though, the Version field is not modifiable. (I am a QA member.) How do we modify it in existing issues?
Component, OS and Version are not modifiable in my browser.It would be great to do this, though: it would encourage people to see the number of issues go down significantly. :)
from Clytie (vi-VN, Vietnamese free-software translation team / nhóm Việt hóa phần mềm tự do)
http://groups-beta.google.com/group/vi-VN [1] Bug-Squashing Party
PGP.sig
Description: This is a digitally signed message part
