Bug triage/Release Notes for 1.0

[dfabulich]

Somebody needs to do bug triage for 1.0.  We need to figure out what we've
fixed since the last version, what we still need to fix (if anything) and
what to watch out for in 1.0, paying special attention to those bugs that
have been filed against the 1.0-beta.

Until we do that, I think there's no way of knowing whether we're clear
for release.  Once that's done, we can write release notes and do a
release.

Does anybody want to volunteer?  We can split up the work between the
three projects (Core, RC, IDE) and by bug number.  In the past I've done
triage both for Core and for RC; I'd like to do just one of those this
time. ;-)

http://wiki.openqa.org/display/SRC/Bug+Triage+HOWTO

The responsibilities of a triager, IMO:

* Go through every bug (even the old ones) and attempt to reproduce them.

* If the issue reproduces, assign it a "Fix Version."  Create new Fix
Versions if necessary.  (1.1, 2.0, Future)  If you think we need to fix it
before we release 1.0, then assign it Fix Version 1.0.

* If not enough information is available to reproduce, just Close the
issue with the Resolution "Incomplete."  Make sure that you REMOVE the Fix
Version from bugs marked "Incomplete."

* For every issue marked "Incomplete," be sure to specify exactly what
information you do need, e.g. "provide an example HTML page and an HTML
Selenese test", or "a publicly available website that exercises that
feature", log files, etc.  In RC, you can also suggest trying to reproduce
the problem using -interactive mode.

This page explains how to set up logging:
http://wiki.openqa.org/display/SRC/Selenium+RC+Logging

* If you have enough information, but the bug doesn't reproduce, then
Close the issue with the Resolution "Not Reproducible."  Again, make sure
that you REMOVE the Fix Version from any bug marked "Not Reproducible."

* Do not mark the bug "Fixed" unless you are saying that you, yourself,
just fixed that bug (in which case you should specify a revision number).
If you think the bug must have been fixed in the past, then just mark it
"Not Reproducible".

-Dan

---------------------------------------------------------------------
To unsubscribe, e-mail: selenium-dev-unsubscribe@...
For additional commands, e-mail: selenium-dev-help@...

[Shinya Kasatani]

I'll be responsible for doing triage for Selenium IDE.
However going through every bugs is a time consuming task, so it would
be helpful if anybody can look into some of them.

-Shinya

On Tue, Mar 18, 2008 at 5:05 AM, Dan Fabulich <dan@...> wrote:

>
>  Somebody needs to do bug triage for 1.0.  We need to figure out what we've
>  fixed since the last version, what we still need to fix (if anything) and
>  what to watch out for in 1.0, paying special attention to those bugs that
>  have been filed against the 1.0-beta.
>
>  Until we do that, I think there's no way of knowing whether we're clear
>  for release.  Once that's done, we can write release notes and do a
>  release.
>
>  Does anybody want to volunteer?  We can split up the work between the
>  three projects (Core, RC, IDE) and by bug number.  In the past I've done
>  triage both for Core and for RC; I'd like to do just one of those this
>  time. ;-)
>
>  http://wiki.openqa.org/display/SRC/Bug+Triage+HOWTO
>
>  The responsibilities of a triager, IMO:
>
>  * Go through every bug (even the old ones) and attempt to reproduce them.
>
>  * If the issue reproduces, assign it a "Fix Version."  Create new Fix
>  Versions if necessary.  (1.1, 2.0, Future)  If you think we need to fix it
>  before we release 1.0, then assign it Fix Version 1.0.
>
>  * If not enough information is available to reproduce, just Close the
>  issue with the Resolution "Incomplete."  Make sure that you REMOVE the Fix
>  Version from bugs marked "Incomplete."
>
>  * For every issue marked "Incomplete," be sure to specify exactly what
>  information you do need, e.g. "provide an example HTML page and an HTML
>  Selenese test", or "a publicly available website that exercises that
>  feature", log files, etc.  In RC, you can also suggest trying to reproduce
>  the problem using -interactive mode.
>
>  This page explains how to set up logging:
>  http://wiki.openqa.org/display/SRC/Selenium+RC+Logging
>
>  * If you have enough information, but the bug doesn't reproduce, then
>  Close the issue with the Resolution "Not Reproducible."  Again, make sure
>  that you REMOVE the Fix Version from any bug marked "Not Reproducible."
>
>  * Do not mark the bug "Fixed" unless you are saying that you, yourself,
>  just fixed that bug (in which case you should specify a revision number).
>  If you think the bug must have been fixed in the past, then just mark it
>  "Not Reproducible".
>
>  -Dan
>
>  ---------------------------------------------------------------------
>  To unsubscribe, e-mail: selenium-dev-unsubscribe@...
>  For additional commands, e-mail: selenium-dev-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: selenium-dev-unsubscribe@...
For additional commands, e-mail: selenium-dev-help@...

[R-24]

I'd like to at least help out with Core.


Haw-Bin
---------------------------------------------------------------------
Posted via Jive Forums
http://forums.openqa.org/thread.jspa?threadID=12963&messageID=41096#41096

---------------------------------------------------------------------
To unsubscribe, e-mail: selenium-dev-unsubscribe@...
For additional commands, e-mail: selenium-dev-help@...