[Gluster-Maintainers] Moving release job off master

[Niels de Vos]

On Thu, Mar 23, 2017 at 04:26:16PM +0530, Nigel Babu wrote:
> Er, why the need for the FTP/HTTP server in addition to the Jenkins artificat?
> A Jenkins artificat is practically a permanent url to the file. Is there
> a use-case I'm missing?
> 
> It's not a big deal. I'm just curious why.

Mainly to make it easy and practical for users who want to browse
through the available tarballs. URLs used by packages are basically
static, with the only difference in the versions. Packagers should not
need to care about the job-id id or other unrelated bits in a path.

It would be most welcome to have the older versions in the same place as
the new ones. Alternatively we could have READMEs pointing to the other
locations where older/newer releases are done.

Thanks,
Niels


> 
> On Wed, Mar 22, 2017 at 12:30:12PM -0400, Niels de Vos wrote:
> > It really does not matter where the tarball is hosted. As long as the
> > emails sent to the packagers list contains the URL and it is archived on
> > an additional FTP/HTTP server (not only as a Jenkins artifact).
> >
> > Many distributions include packages for Gluster where we are not
> > directly involved (Arch, NetBSD, Debian, ...). We need to make sure
> > those packagers are informed as well.
> >
> > HTH,
> > Niels
> 
> 
> --
> nigelb


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <http://lists.gluster.org/pipermail/maintainers/attachments/20170323/f73c628f/attachment.sig>