I overestimated the amount of effort it would take to get email notifications working. They do work now. So please set your own email address in the ANNOUNCE_EMAIL parameter to test the output.
On Thu, Apr 13, 2017 at 10:15:06AM +0530, Nigel Babu wrote: > Hello folks, > > Current and past release managers + package maintainers, please take special > note. > > Please test the new release job[1]. I'm working on making email notifications > ready. I've eliminated a lot of code we used to run to get releases out. It > doesn't yet archive to bits.gluster.org. That's for next round of testing. > > Please take a look at the script[2] as well. > * Is the GERRIT_SPEC and RELEASE_VERSION largely different other than adding > the lack of preceding 'v'? > * The sed line (L77) in the current script seems unnecessary. It didn't have > any effect with my tests and we already get version number in ./configure > automatically. > * The Changelog seems to be unused as well, so I got rid of it. > > The git clone and the email notification will be handled by Jenkins. The git > clone, obviously works already. I'm working on getting the email bit working, > so you can safely test without fear that someone will be emailed. > > [1]: https://build.gluster.org/job/release-new/ > [2]: > https://review.gluster.org/#/c/17047/1/build-gluster-org/scripts/release.sh > [3]: > https://github.com/gluster/glusterfs-patch-acceptance-tests/blob/master/release.sh > > -- > nigelb -- nigelb
signature.asc
Description: PGP signature
_______________________________________________ maintainers mailing list [email protected] http://lists.gluster.org/mailman/listinfo/maintainers
