I wasn’t aware that email notification had been turned off. Maybe our projects haven’t been building for months...
Before we reply to Stefan: do we want to keep the Gump build? Or do we want to take this as an opportunity to switch to Jenkins? Gump does the job, but I see the automatic build more as a regression catcher than an API compatibility checker. So Jenkins seems more appropriate. Vincent On 24/06/13 15:20, Stefan Bodewig wrote: > 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: general-unsubscr...@xmlgraphics.apache.org > For additional commands, e-mail: general-h...@xmlgraphics.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@xmlgraphics.apache.org For additional commands, e-mail: general-h...@xmlgraphics.apache.org
