26 Jan
2011
26 Jan
'11
3:41 p.m.
Hi devs,
Sorin and Silvia are helping us in term of improving the quality of platform/XE/XEM by
systematically testing milestones/RCs/final versions.
They've started a TestReports space on xwiki.org where he's going to put all his
test reports from now on:
http://www.xwiki.org/xwiki/bin/view/TestReports/
In those reports, when a test fails they'll need to create a JIRA issue (instead of
pointing to a page on the incubator). This would make it much easier for reporting
purpose, to see all the issues they've created and for us to see all issues found by
the Q&A team.
The problem is that our current JIRA strategy is to NOT create jira issue for issues that
haven't been "released" already (instead the strategy is to comment in
them).
I'm proposing to relax this rule in the following manner:
* Allow to have "affects" and "fix for" be the same value in JIRA
* Automatically exclude from our release notes issues where "affects" ==
"fixfor"
In addition IMO it would be good for Sorin/Silvia to:
* Link the newly created jira to an existing jira
WDYT?
Thanks
-Vincent
27 Jan
27 Jan
9:34 a.m.
On 01/26/2011 04:41 PM, Vincent Massol wrote:
Hi devs,
Sorin and Silvia are helping us in term of improving the quality of platform/XE/XEM by
systematically testing milestones/RCs/final versions.
They've started a TestReports space on xwiki.org where he's going to put all his
test reports from now on:
http://www.xwiki.org/xwiki/bin/view/TestReports/
In those reports, when a test fails they'll need to create a JIRA issue (instead of
pointing to a page on the incubator). This would make it much easier for reporting
purpose, to see all the issues they've created and for us to see all issues found by
the Q&A team.
The problem is that our current JIRA strategy is to NOT create jira issue for issues that
haven't been "released" already (instead the strategy is to comment in
them).
I'm proposing to relax this rule in the following manner:
* Allow to have "affects" and "fix for" be the same value in JIRA
* Automatically exclude from our release notes issues where "affects" ==
"fixfor"
In addition IMO it would be good for Sorin/Silvia to:
* Link the newly created jira to an existing jira
WDYT?
+1 provided it is used as a last resort, after:
* making sure the issue is not present in the latest release
* making sure there aren't any automated tests failing for the same
reason (-> devs are already notified)
* asking on IRC or mailing list if there were recent changes to the
module affected by the issue (-> comment on existing issue)
Thanks,
Marius
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
1:41 p.m.
On Jan 27, 2011, at 9:34 AM, Marius Dumitru Florea wrote:
On 01/26/2011 04:41 PM, Vincent Massol wrote:
Sounds good to me.
What do others think?
If we agree I'll update xwiki.org
Thanks
-Vincent
Hi devs,
Sorin and Silvia are helping us in term of improving the quality of platform/XE/XEM by
systematically testing milestones/RCs/final versions.
They've started a TestReports space on xwiki.org where he's going to put all his
test reports from now on:
http://www.xwiki.org/xwiki/bin/view/TestReports/
In those reports, when a test fails they'll need to create a JIRA issue (instead of
pointing to a page on the incubator). This would make it much easier for reporting
purpose, to see all the issues they've created and for us to see all issues found by
the Q&A team.
The problem is that our current JIRA strategy is to NOT create jira issue for issues that
haven't been "released" already (instead the strategy is to comment in
them).
I'm proposing to relax this rule in the following manner:
* Allow to have "affects" and "fix for" be the same value in JIRA
* Automatically exclude from our release notes issues where "affects" ==
"fixfor"
In addition IMO it would be good for Sorin/Silvia to:
* Link the newly created jira to an existing jira
WDYT?
+1 provided it is used as a last resort, after:
* making sure the issue is not present in the latest release
* making sure there aren't any automated tests failing for the same
reason (-> devs are already notified)
* asking on IRC or mailing list if there were recent changes to the
module affected by the issue (-> comment on existing issue) 
8:39 p.m.
On 01/27/2011 01:41 PM, Vincent Massol wrote:
On Jan 27, 2011, at 9:34 AM, Marius Dumitru Florea wrote:
+1 for Marius' suggestions.
On 01/26/2011 04:41 PM, Vincent Massol wrote:
Sounds good to me.
What do others think? Hi devs,
Sorin and Silvia are helping us in term of improving the quality of platform/XE/XEM by
systematically testing milestones/RCs/final versions.
They've started a TestReports space on xwiki.org where he's going to put all his
test reports from now on:
http://www.xwiki.org/xwiki/bin/view/TestReports/
In those reports, when a test fails they'll need to create a JIRA issue (instead of
pointing to a page on the incubator). This would make it much easier for reporting
purpose, to see all the issues they've created and for us to see all issues found by
the Q&A team.
The problem is that our current JIRA strategy is to NOT create jira issue for issues that
haven't been "released" already (instead the strategy is to comment in
them).
I'm proposing to relax this rule in the following manner:
* Allow to have "affects" and "fix for" be the same value in JIRA
* Automatically exclude from our release notes issues where "affects" ==
"fixfor"
In addition IMO it would be good for Sorin/Silvia to:
* Link the newly created jira to an existing jira
WDYT?
+1 provided it is used as a last resort, after:
* making sure the issue is not present in the latest release
* making sure there aren't any automated tests failing for the same
reason (-> devs are already notified)
* asking on IRC or mailing list if there were recent changes to the
module affected by the issue (-> comment on existing issue) If we agree I'll update xwiki.org
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
28 Jan
28 Jan
1:51 p.m.
Hi devs,
I am +1 for this strategy because it makes QA job more visible and more
easy to see. Instead of having a separate page on Incubator or on
another Wiki, everything goes to JIRA, which is much more easy to follow
than other sources because it is also a centralized source of bugs.
I am also +1 for what Marius said, IMO it is the most natural approach.
Thank you Vincent for proposing this, I think this has benefits on all
sides and eases the work of devs.
Regards,
Sorin B.
On 01/26/2011 04:41 PM, Vincent Massol wrote:
Hi devs,
Sorin and Silvia are helping us in term of improving the quality of platform/XE/XEM by
systematically testing milestones/RCs/final versions.
They've started a TestReports space on xwiki.org where he's going to put all his
test reports from now on:
http://www.xwiki.org/xwiki/bin/view/TestReports/
In those reports, when a test fails they'll need to create a JIRA issue (instead of
pointing to a page on the incubator). This would make it much easier for reporting
purpose, to see all the issues they've created and for us to see all issues found by
the Q&A team.
The problem is that our current JIRA strategy is to NOT create jira issue for issues that
haven't been "released" already (instead the strategy is to comment in
them).
I'm proposing to relax this rule in the following manner:
* Allow to have "affects" and "fix for" be the same value in JIRA
* Automatically exclude from our release notes issues where "affects" ==
"fixfor"
In addition IMO it would be good for Sorin/Silvia to:
* Link the newly created jira to an existing jira
WDYT?
+1 provided it is used as a last resort, after:
* making sure the issue is not present in the latest release
* making sure there aren't any automated tests failing for the same
reason (-> devs are already notified)
* asking on IRC or mailing list if there were recent changes to the
module affected by the issue (-> comment on existing issue)
Thanks,
Marius
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
5:02 p.m.
On Jan 27, 2011, at 9:34 AM, Marius Dumitru Florea wrote:
On 01/26/2011 04:41 PM, Vincent Massol wrote:
if we find the issue already exists we'll close it with a duplicate.
Hi devs,
Sorin and Silvia are helping us in term of improving the quality of platform/XE/XEM by
systematically testing milestones/RCs/final versions.
They've started a TestReports space on xwiki.org where he's going to put all his
test reports from now on:
http://www.xwiki.org/xwiki/bin/view/TestReports/
In those reports, when a test fails they'll need to create a JIRA issue (instead of
pointing to a page on the incubator). This would make it much easier for reporting
purpose, to see all the issues they've created and for us to see all issues found by
the Q&A team.
The problem is that our current JIRA strategy is to NOT create jira issue for issues that
haven't been "released" already (instead the strategy is to comment in
them).
I'm proposing to relax this rule in the following manner:
* Allow to have "affects" and "fix for" be the same value in JIRA
* Automatically exclude from our release notes issues where "affects" ==
"fixfor"
In addition IMO it would be good for Sorin/Silvia to:
* Link the newly created jira to an existing jira
WDYT?
+1 provided it is used as a last resort, after:
* making sure the issue is not present in the latest release * making sure there aren't any automated tests
failing for the same
reason (-> devs are already notified)
Agreed, that said if functional tests are failing they need to be fixed and fixing them
will require a commit usually, which can be done against the created issue. But I agree we
should try to minimize those issues as they're not necessary.
* asking on IRC or mailing list if there were recent
changes to the
module affected by the issue (-> comment on existing issue)
Thanks
-Vincent
1 Feb
1 Feb
3:34 p.m.
New subject: [xwiki-devs] [Discussion] JIRA: Improving QA/Test Reports + relaxing JIRA rule
+1
On Thu, Jan 27, 2011 at 09:34, Marius Dumitru Florea
<mariusdumitru.florea(a)xwiki.com> wrote:
On 01/26/2011 04:41 PM, Vincent Massol wrote:
--
Thomas Mortagne
Hi devs,
Sorin and Silvia are helping us in term of improving the quality of platform/XE/XEM by
systematically testing milestones/RCs/final versions.
They've started a TestReports space on xwiki.org where he's going to put all his
test reports from now on:
http://www.xwiki.org/xwiki/bin/view/TestReports/
In those reports, when a test fails they'll need to create a JIRA issue (instead of
pointing to a page on the incubator). This would make it much easier for reporting
purpose, to see all the issues they've created and for us to see all issues found by
the Q&A team.
The problem is that our current JIRA strategy is to NOT create jira issue for issues that
haven't been "released" already (instead the strategy is to comment in
them).
I'm proposing to relax this rule in the following manner:
* Allow to have "affects" and "fix for" be the same value in JIRA
* Automatically exclude from our release notes issues where "affects" ==
"fixfor"
In addition IMO it would be good for Sorin/Silvia to:
* Link the newly created jira to an existing jira
WDYT?
+1 provided it is used as a last resort, after:
* making sure the issue is not present in the latest release
* making sure there aren't any automated tests failing for the same
reason (-> devs are already notified)
* asking on IRC or mailing list if there were recent changes to the
module affected by the issue (-> comment on existing issue)
Thanks,
Marius
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
28 Jan
28 Jan
8:47 a.m.
Sorin/Silvia/others,
Would you be ok with that?
Thanks
-Vincent
On Jan 26, 2011, at 3:41 PM, Vincent Massol wrote:
Hi devs,
Sorin and Silvia are helping us in term of improving the quality of platform/XE/XEM by
systematically testing milestones/RCs/final versions.
They've started a TestReports space on xwiki.org where he's going to put all his
test reports from now on:
http://www.xwiki.org/xwiki/bin/view/TestReports/
In those reports, when a test fails they'll need to create a JIRA issue (instead of
pointing to a page on the incubator). This would make it much easier for reporting
purpose, to see all the issues they've created and for us to see all issues found by
the Q&A team.
The problem is that our current JIRA strategy is to NOT create jira issue for issues that
haven't been "released" already (instead the strategy is to comment in
them).
I'm proposing to relax this rule in the following manner:
* Allow to have "affects" and "fix for" be the same value in JIRA
* Automatically exclude from our release notes issues where "affects" ==
"fixfor"
In addition IMO it would be good for Sorin/Silvia to:
* Link the newly created jira to an existing jira
WDYT?
Thanks
-Vincent
5:04 p.m.
Documented on
http://dev.xwiki.org/xwiki/bin/view/Community/DevelopmentPractices#HJIRABes…
Actually all I did was remove an existing rule which no longer applies (that was the
simplest way to document this without making it too complex to read).
Thanks
-Vincent
On Jan 26, 2011, at 3:41 PM, Vincent Massol wrote:
Hi devs,
Sorin and Silvia are helping us in term of improving the quality of platform/XE/XEM by
systematically testing milestones/RCs/final versions.
They've started a TestReports space on xwiki.org where he's going to put all his
test reports from now on:
http://www.xwiki.org/xwiki/bin/view/TestReports/
In those reports, when a test fails they'll need to create a JIRA issue (instead of
pointing to a page on the incubator). This would make it much easier for reporting
purpose, to see all the issues they've created and for us to see all issues found by
the Q&A team.
The problem is that our current JIRA strategy is to NOT create jira issue for issues that
haven't been "released" already (instead the strategy is to comment in
them).
I'm proposing to relax this rule in the following manner:
* Allow to have "affects" and "fix for" be the same value in JIRA
* Automatically exclude from our release notes issues where "affects" ==
"fixfor"
In addition IMO it would be good for Sorin/Silvia to:
* Link the newly created jira to an existing jira
WDYT?
Thanks
-Vincent
4976
days inactive
4982
days old
8 comments
5 participants
participants (5)
-
Marius Dumitru Florea -
Sergiu Dumitriu -
Sorin Burjan -
Thomas Mortagne -
Vincent Massol