2 Feb
2010
2 Feb
'10
3:56 p.m.
Hi Silvia,
Silvia Rusu wrote:
Hi,
Here's an excerpt from the set of rules about not creating issues for
unreleased work:
"Imagine that someone has been working on a given issue for a given version.
Then someone else notices a problem related to the work done. If the version
has not been released then you shouldn't create a new JIRA issue for
reporting the problem. Instead you should reopen the issue (if it's been
closed) and add a comment to it."
There should be a mention about what to do when you encounter a problem for
which there is no Jira issue.
If you find a problem that is present in a snapshot but not in the
latest release then that problem was introduced by a change made after
the release. When we developers make a change we _usually_ refer to a
JIRA issue in the commit log. This means you can face this scenarios:
(1) A developer commits without opening a JIRA issue and his change
produces a bug which you notice. In this case, IMO the developer either
* reverts the commit
* or opens a JIRA issue related to his/her change where you can comment
the found bug
(2) The developer refers to a JIRA issue in the commit log. In this case
you find the JIRA issue either by searching or asking the developer. You
can find the developer that works on a specific part of XWiki platform
(the part where you discover the bug) by asking on the IRC/Jabber.
There is also a special case where the developer is working on a new
module which hasn't been release yet and it tells you to test it (i.e.
there's no previous release for that module). In this case, IMO, the
best is to ask the developer to release a first version, even if it's
featureless, and to open JIRA issue against that that initial version
for the features he/she's working on. This way you can comment on those
issues or even report issues for the initial release (if it's the case).
In case you don't find neither the JIRA issue nor the developer
responsible for the problem (can happen) I think you should open a JIRA
issue for the previous release. IMO it's better to close or correct a
JIRA issue than to forget or ignore a problem.
Thanks,
Marius
For example the way I report this is by creating a page on the incubator in
the "Test" space. There I present the issue, attach printscreens and mention
the version where I encountered the problem.
If the problem is not fixed in the release I report it on Jira.
Is there a "standard" procedure for this type of situation?
-----
Silvia Rusu
Tester & Documentation Writer - XWiki
http://twitter.com/silviarusu