[xwiki-devs] [Proposal] Stop Jenkins notifications for 3.1 branch
Hi devs, I'd like to stop sending jenkins emails for the 3.1 builds for the following reason: * We don't have enough time to fix the tests on that branch as we did for the master branch * Almost all (if not all) emails are false positives * We're stabilizing the build and we're trying to reduce all false positive emails and this is not helping us go in the right direction * This branch is supposed to go away in not too long * We don't do many commits on that branch (and we shouldn't) So the idea is that we don't receive emails anymore for that branch **but** it'll be up to the Release Manager when we release this branch to review the failing tests with the other devs when it's time to release it to ensure that we don't have real test failures. WDYT? Thanks -Vincent
On 09/06/2011 02:51 AM, Vincent Massol wrote:
Hi devs,
I'd like to stop sending jenkins emails for the 3.1 builds for the following reason: * We don't have enough time to fix the tests on that branch as we did for the master branch * Almost all (if not all) emails are false positives * We're stabilizing the build and we're trying to reduce all false positive emails and this is not helping us go in the right direction * This branch is supposed to go away in not too long * We don't do many commits on that branch (and we shouldn't)
So the idea is that we don't receive emails anymore for that branch **but** it'll be up to the Release Manager when we release this branch to review the failing tests with the other devs when it's time to release it to ensure that we don't have real test failures.
WDYT?
+1. By the way, when should we release 3.1.1? The stable-3.0.x branch is going to be deleted next week after the trunk moves to 3.3-SNAPSHOT -- Sergiu Dumitriu http://purl.org/net/sergiu/
On Tue, Sep 6, 2011 at 9:07 AM, Sergiu Dumitriu <[email protected]> wrote:
On 09/06/2011 02:51 AM, Vincent Massol wrote:
Hi devs,
I'd like to stop sending jenkins emails for the 3.1 builds for the following reason: * We don't have enough time to fix the tests on that branch as we did for the master branch * Almost all (if not all) emails are false positives * We're stabilizing the build and we're trying to reduce all false positive emails and this is not helping us go in the right direction * This branch is supposed to go away in not too long * We don't do many commits on that branch (and we shouldn't)
So the idea is that we don't receive emails anymore for that branch **but** it'll be up to the Release Manager when we release this branch to review the failing tests with the other devs when it's time to release it to ensure that we don't have real test failures.
WDYT?
+1. By the way, when should we release 3.1.1? The stable-3.0.x branch is going to be deleted next week after the trunk moves to 3.3-SNAPSHOT
Why next week ? Since the rule is to support 2 branches (3.2.x and 3.1.x) we already should have deleted 3.0.x
-- Sergiu Dumitriu http://purl.org/net/sergiu/ _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
On 09/06/2011 03:11 AM, Thomas Mortagne wrote:
On Tue, Sep 6, 2011 at 9:07 AM, Sergiu Dumitriu<[email protected]> wrote:
On 09/06/2011 02:51 AM, Vincent Massol wrote:
Hi devs,
I'd like to stop sending jenkins emails for the 3.1 builds for the following reason: * We don't have enough time to fix the tests on that branch as we did for the master branch * Almost all (if not all) emails are false positives * We're stabilizing the build and we're trying to reduce all false positive emails and this is not helping us go in the right direction * This branch is supposed to go away in not too long * We don't do many commits on that branch (and we shouldn't)
So the idea is that we don't receive emails anymore for that branch **but** it'll be up to the Release Manager when we release this branch to review the failing tests with the other devs when it's time to release it to ensure that we don't have real test failures.
WDYT?
+1. By the way, when should we release 3.1.1? The stable-3.0.x branch is going to be deleted next week after the trunk moves to 3.3-SNAPSHOT
Why next week ? Since the rule is to support 2 branches (3.2.x and 3.1.x) we already should have deleted 3.0.x
Wasn't it 2 stable branches + trunk? -- Sergiu Dumitriu http://purl.org/net/sergiu/
On Tue, Sep 6, 2011 at 9:38 AM, Sergiu Dumitriu <[email protected]> wrote:
On 09/06/2011 03:11 AM, Thomas Mortagne wrote:
On Tue, Sep 6, 2011 at 9:07 AM, Sergiu Dumitriu<[email protected]> wrote:
On 09/06/2011 02:51 AM, Vincent Massol wrote:
Hi devs,
I'd like to stop sending jenkins emails for the 3.1 builds for the following reason: * We don't have enough time to fix the tests on that branch as we did for the master branch * Almost all (if not all) emails are false positives * We're stabilizing the build and we're trying to reduce all false positive emails and this is not helping us go in the right direction * This branch is supposed to go away in not too long * We don't do many commits on that branch (and we shouldn't)
So the idea is that we don't receive emails anymore for that branch **but** it'll be up to the Release Manager when we release this branch to review the failing tests with the other devs when it's time to release it to ensure that we don't have real test failures.
WDYT?
+1. By the way, when should we release 3.1.1? The stable-3.0.x branch is going to be deleted next week after the trunk moves to 3.3-SNAPSHOT
Why next week ? Since the rule is to support 2 branches (3.2.x and 3.1.x) we already should have deleted 3.0.x
Wasn't it 2 stable branches + trunk?
Nop, never was.
-- Sergiu Dumitriu http://purl.org/net/sergiu/ _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
+1 Thanks, Marius On Tue, Sep 6, 2011 at 9:51 AM, Vincent Massol <[email protected]> wrote:
Hi devs,
I'd like to stop sending jenkins emails for the 3.1 builds for the following reason: * We don't have enough time to fix the tests on that branch as we did for the master branch * Almost all (if not all) emails are false positives * We're stabilizing the build and we're trying to reduce all false positive emails and this is not helping us go in the right direction * This branch is supposed to go away in not too long * We don't do many commits on that branch (and we shouldn't)
So the idea is that we don't receive emails anymore for that branch **but** it'll be up to the Release Manager when we release this branch to review the failing tests with the other devs when it's time to release it to ensure that we don't have real test failures.
WDYT?
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
+1 On Tue, Sep 6, 2011 at 8:51 AM, Vincent Massol <[email protected]> wrote:
Hi devs,
I'd like to stop sending jenkins emails for the 3.1 builds for the following reason: * We don't have enough time to fix the tests on that branch as we did for the master branch * Almost all (if not all) emails are false positives * We're stabilizing the build and we're trying to reduce all false positive emails and this is not helping us go in the right direction * This branch is supposed to go away in not too long * We don't do many commits on that branch (and we shouldn't)
So the idea is that we don't receive emails anymore for that branch **but** it'll be up to the Release Manager when we release this branch to review the failing tests with the other devs when it's time to release it to ensure that we don't have real test failures.
WDYT?
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
Done, I've removed emails notifications for functional tests for the 3.1 branch (I've kept email notifs for other modules for the 3.1 branch). Thanks -Vincent On Sep 6, 2011, at 8:51 AM, Vincent Massol wrote:
Hi devs,
I'd like to stop sending jenkins emails for the 3.1 builds for the following reason: * We don't have enough time to fix the tests on that branch as we did for the master branch * Almost all (if not all) emails are false positives * We're stabilizing the build and we're trying to reduce all false positive emails and this is not helping us go in the right direction * This branch is supposed to go away in not too long * We don't do many commits on that branch (and we shouldn't)
So the idea is that we don't receive emails anymore for that branch **but** it'll be up to the Release Manager when we release this branch to review the failing tests with the other devs when it's time to release it to ensure that we don't have real test failures.
WDYT?
Thanks -Vincent
participants (4)
-
Marius Dumitru Florea -
Sergiu Dumitriu -
Thomas Mortagne -
Vincent Massol