You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-dev@xerces.apache.org by Michael Glavassevich <mr...@ca.ibm.com> on 2013/06/24 20:19:02 UTC
Re: Your Gump Build(s)
Hi,
Projects like Xerces and Xalan are near the bottom of the food chain. I've
always thought the projects higher up in the stack got more value from
Gump. I don't remember the last time we got a notification for a
legitimate build failure at our level. It was a rather rare occurrence,
even while e-mail notifications were still being sent out.
Thanks.
Michael Glavassevich
XML Technologies and WAS Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
Stefan Bodewig <bo...@apache.org> wrote on 06/24/2013 09:20:47 AM:
> Dear Community
>
> Apache Gump builds some of your projects and it is quite possible you
> don't know or have by now forgotten about it.
>
> More than half a year ago a technical problem has forced us to turn off
> emails on build failures as we would have been sending out lots of false
> alarms.
>
> Before we re-enable emails we'd like to know whether you are still
> interested in the service Gump provides, so please tell us. :-)
>
> Metadata for many projects have been neglected for a long time and it is
> quite possible they'd need some love for results to be meaningful. All
> Apache committers have write access to Gump's metadata.
>
> In case you don't know what this Gump stuff is about:
>
> Apache Gump builds the full stack of the latest commits of software in
> order to ensure integrity over releases. Build failures surface API
> discontinuities between projects before they impact releases, and Gump's
> e-mail notifications hope to promote the conversations between teams to
> resolve those discontinuities.
>
> When responding to this mail please shorten the CC list as appropriate.
>
> Cheers
>
> Stefan
>
> on behalf of the Gump PMC
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org
> For additional commands, e-mail: dev-help@xalan.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
Re: Your Gump Build(s)
Posted by Stefan Bodewig <bo...@apache.org>.
On 2013-06-25, Michael Glavassevich wrote:
> Stefan Bodewig <bo...@apache.org> wrote on 06/25/2013 03:59:56 AM:
>> No email doesn't mean no downstream has been broken.
> True, but if that occurred I'd expect the broken project (who would have
> been notified by Gump) would at some point open a discussion with us about
> the problem we caused
Yes, that's the idea :-)
> and I don't recall the last time that happened either, if it ever
> did. That's more of a statement about the stability of Xerces and
> Xalan than anything else. The rate of change is nowhere near like it
> was 10 years ago.
Coming out of Ant land myself I know pretty well what you are talking
about.
Thanks
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
Re: Your Gump Build(s)
Posted by Stefan Bodewig <bo...@apache.org>.
On 2013-06-25, Michael Glavassevich wrote:
> Stefan Bodewig <bo...@apache.org> wrote on 06/25/2013 03:59:56 AM:
>> No email doesn't mean no downstream has been broken.
> True, but if that occurred I'd expect the broken project (who would have
> been notified by Gump) would at some point open a discussion with us about
> the problem we caused
Yes, that's the idea :-)
> and I don't recall the last time that happened either, if it ever
> did. That's more of a statement about the stability of Xerces and
> Xalan than anything else. The rate of change is nowhere near like it
> was 10 years ago.
Coming out of Ant land myself I know pretty well what you are talking
about.
Thanks
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org
For additional commands, e-mail: dev-help@xalan.apache.org
Re: Your Gump Build(s)
Posted by Stefan Bodewig <bo...@apache.org>.
On 2013-06-25, Michael Glavassevich wrote:
> Stefan Bodewig <bo...@apache.org> wrote on 06/25/2013 03:59:56 AM:
>> No email doesn't mean no downstream has been broken.
> True, but if that occurred I'd expect the broken project (who would have
> been notified by Gump) would at some point open a discussion with us about
> the problem we caused
Yes, that's the idea :-)
> and I don't recall the last time that happened either, if it ever
> did. That's more of a statement about the stability of Xerces and
> Xalan than anything else. The rate of change is nowhere near like it
> was 10 years ago.
Coming out of Ant land myself I know pretty well what you are talking
about.
Thanks
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: Your Gump Build(s)
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
Stefan Bodewig <bo...@apache.org> wrote on 06/25/2013 03:59:56 AM:
> On 2013-06-24, Michael Glavassevich wrote:
>
> > Projects like Xerces and Xalan are near the bottom of the food chain.
I've
> > always thought the projects higher up in the stack got more value from
> > Gump.
>
> Unless Xalan or Xerces breaks something :-) In this case you get the
> early warning by other project's builds failing. That's why monitoring
> your dependee's builds is a crucial part of getting anything useful out
> of Gump.
I don't think we ever did that.
> Shall I translate this to "we're not too eager on keeping our Gump
> builds"?
I'd translate that to "we don't get much out of it but others might".
> > I don't remember the last time we got a notification for a legitimate
> > build failure at our level. It was a rather rare occurrence, even
> > while e-mail notifications were still being sent out.
>
> Well, yes, see above. No email doesn't mean no downstream has been
> broken.
True, but if that occurred I'd expect the broken project (who would have
been notified by Gump) would at some point open a discussion with us about
the problem we caused and I don't recall the last time that happened
either, if it ever did. That's more of a statement about the stability of
Xerces and Xalan than anything else. The rate of change is nowhere near
like it was 10 years ago.
> Thanks
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
> For additional commands, e-mail: j-dev-help@xerces.apache.org
Michael Glavassevich
XML Technologies and WAS Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org
For additional commands, e-mail: dev-help@xalan.apache.org
Re: Your Gump Build(s)
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
Stefan Bodewig <bo...@apache.org> wrote on 06/25/2013 03:59:56 AM:
> On 2013-06-24, Michael Glavassevich wrote:
>
> > Projects like Xerces and Xalan are near the bottom of the food chain.
I've
> > always thought the projects higher up in the stack got more value from
> > Gump.
>
> Unless Xalan or Xerces breaks something :-) In this case you get the
> early warning by other project's builds failing. That's why monitoring
> your dependee's builds is a crucial part of getting anything useful out
> of Gump.
I don't think we ever did that.
> Shall I translate this to "we're not too eager on keeping our Gump
> builds"?
I'd translate that to "we don't get much out of it but others might".
> > I don't remember the last time we got a notification for a legitimate
> > build failure at our level. It was a rather rare occurrence, even
> > while e-mail notifications were still being sent out.
>
> Well, yes, see above. No email doesn't mean no downstream has been
> broken.
True, but if that occurred I'd expect the broken project (who would have
been notified by Gump) would at some point open a discussion with us about
the problem we caused and I don't recall the last time that happened
either, if it ever did. That's more of a statement about the stability of
Xerces and Xalan than anything else. The rate of change is nowhere near
like it was 10 years ago.
> Thanks
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
> For additional commands, e-mail: j-dev-help@xerces.apache.org
Michael Glavassevich
XML Technologies and WAS Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: Your Gump Build(s)
Posted by Michael Glavassevich <mr...@ca.ibm.com>.
Stefan Bodewig <bo...@apache.org> wrote on 06/25/2013 03:59:56 AM:
> On 2013-06-24, Michael Glavassevich wrote:
>
> > Projects like Xerces and Xalan are near the bottom of the food chain.
I've
> > always thought the projects higher up in the stack got more value from
> > Gump.
>
> Unless Xalan or Xerces breaks something :-) In this case you get the
> early warning by other project's builds failing. That's why monitoring
> your dependee's builds is a crucial part of getting anything useful out
> of Gump.
I don't think we ever did that.
> Shall I translate this to "we're not too eager on keeping our Gump
> builds"?
I'd translate that to "we don't get much out of it but others might".
> > I don't remember the last time we got a notification for a legitimate
> > build failure at our level. It was a rather rare occurrence, even
> > while e-mail notifications were still being sent out.
>
> Well, yes, see above. No email doesn't mean no downstream has been
> broken.
True, but if that occurred I'd expect the broken project (who would have
been notified by Gump) would at some point open a discussion with us about
the problem we caused and I don't recall the last time that happened
either, if it ever did. That's more of a statement about the stability of
Xerces and Xalan than anything else. The rate of change is nowhere near
like it was 10 years ago.
> Thanks
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
> For additional commands, e-mail: j-dev-help@xerces.apache.org
Michael Glavassevich
XML Technologies and WAS Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
Re: Your Gump Build(s)
Posted by Stefan Bodewig <bo...@apache.org>.
On 2013-06-24, Michael Glavassevich wrote:
> Projects like Xerces and Xalan are near the bottom of the food chain. I've
> always thought the projects higher up in the stack got more value from
> Gump.
Unless Xalan or Xerces breaks something :-) In this case you get the
early warning by other project's builds failing. That's why monitoring
your dependee's builds is a crucial part of getting anything useful out
of Gump.
Shall I translate this to "we're not too eager on keeping our Gump
builds"?
> I don't remember the last time we got a notification for a legitimate
> build failure at our level. It was a rather rare occurrence, even
> while e-mail notifications were still being sent out.
Well, yes, see above. No email doesn't mean no downstream has been
broken.
Thanks
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@gump.apache.org
For additional commands, e-mail: general-help@gump.apache.org
Re: Your Gump Build(s)
Posted by Stefan Bodewig <bo...@apache.org>.
On 2013-06-24, Michael Glavassevich wrote:
> Projects like Xerces and Xalan are near the bottom of the food chain. I've
> always thought the projects higher up in the stack got more value from
> Gump.
Unless Xalan or Xerces breaks something :-) In this case you get the
early warning by other project's builds failing. That's why monitoring
your dependee's builds is a crucial part of getting anything useful out
of Gump.
Shall I translate this to "we're not too eager on keeping our Gump
builds"?
> I don't remember the last time we got a notification for a legitimate
> build failure at our level. It was a rather rare occurrence, even
> while e-mail notifications were still being sent out.
Well, yes, see above. No email doesn't mean no downstream has been
broken.
Thanks
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org
Re: Your Gump Build(s)
Posted by Stefan Bodewig <bo...@apache.org>.
On 2013-06-24, Michael Glavassevich wrote:
> Projects like Xerces and Xalan are near the bottom of the food chain. I've
> always thought the projects higher up in the stack got more value from
> Gump.
Unless Xalan or Xerces breaks something :-) In this case you get the
early warning by other project's builds failing. That's why monitoring
your dependee's builds is a crucial part of getting anything useful out
of Gump.
Shall I translate this to "we're not too eager on keeping our Gump
builds"?
> I don't remember the last time we got a notification for a legitimate
> build failure at our level. It was a rather rare occurrence, even
> while e-mail notifications were still being sent out.
Well, yes, see above. No email doesn't mean no downstream has been
broken.
Thanks
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org
For additional commands, e-mail: dev-help@xalan.apache.org