On Tue, Jul 16, 2013 at 1:40 AM, Anze Staric <[email protected]> wrote:
> I did not know we have a build bot running. Can we make it report test > failures to one of the mailing lists? > > On Tue, Jul 16, 2013 at 9:47 AM, Apache Bloodhound > <[email protected]> wrote: > > Page "BloodhoundReleaseProcess" was changed by rjollos > > Diff URL: < > https://issues.apache.org/bloodhound/wiki/BloodhoundReleaseProcess?action=diff&version=39 > > > > Revision 39 > > Comment: Suggestion to review unit test execution report. > > Changes: > > -------8<------8<------8<------8<------8<------8<------8<------8<-------- > > Index: BloodhoundReleaseProcess > > ========================================================================= > > --- BloodhoundReleaseProcess (version: 38) > > +++ BloodhoundReleaseProcess (version: 39) > > @@ -13,6 +13,7 @@ > > }}} > > 1. Review the tickets that have been resolved since the last release, > and update the RELEASE_NOTES file highlighting new features and issues > fixed, optionally including major known issues that remain. The relevant > tickets will usually be associated with a single milestone. However, check > for tickets that are part of this release but have been closed > [query:status=closed&resolution=fixed&milestone=&component!=siteadmin > without the milestone set]. All of the tickets in the milestone should be > resolved when the release is started. Unresolved tickets that are still > part of this milestone should be unassociated by moving them to another > milestone. > > 1. Check the [ > http://ci.apache.org/projects/bloodhound/rat-output.html Rat Report] for > any unapproved licences or missing license headers. > > + 1. You may want to review the most recent [ > http://ci.apache.org/builders/bh-unit-tests unit test execution report]. > > 1. Update NOTICE and LICENSE files if required (should any licenses > be added/removed; are the locations specified still accurate). > > 1. Update packages version numbers in > {{{bloodhound_<package>/setup.py}}} files to reflect the current overall > version number (if required). The package version numbers should have been > updated at the start of the release cycle. > > 1. Commit changes back to trunk. > > -------8<------8<------8<------8<------8<------8<------8<------8<-------- > > > > -- > > Page URL: < > https://issues.apache.org/bloodhound/wiki/BloodhoundReleaseProcess> > > Apache Bloodhound <https://issues.apache.org/bloodhound/> > > The Apache Bloodhound issue tracker > > > > This is an automated message. Someone added your email address to be > > notified of changes on 'BloodhoundReleaseProcess' page. > > If it was not you, please report to . > Seems like a good idea. Gary pointed me to the script, which all committers should have access to: https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/bloodhound.conf If someone knows or figures out how to send notifications from buildbot, I imagine that a modification to that script could be proposed.
