Re: Hosting of source tarballs and rpms

--0rSojgWGcpz+ezC3 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Oct 28, 2011 at 02:49:08PM -0400, Mike Burns wrote: It's a MUST requirement for an open source project, really - gzip or bzip tarballs, zip if appropriate of at least each release, going back in time. Packages ideally end-up in the respective distros, until then we SHOULD host them via ovirt.org. (I reckon JARs & WARs may be already compressed, if we're providing those we can probaly leave them as .jar/.war files?) Now the how of it is the trick. We can start doing it manually, create a directory structur off ovirt.org that makes sense, etc. But don't we really want these generated as part of the release build process? Then don't we want those builds + checksums pushed automagically to the above ovit.org directory? Then might we want to provide nightly builds in some way? So no rush on picking the how, except that the directory structure we build first would ideally match the future structure. And probably some other stuff. - Karsten --=20 name: Karsten 'quaid' Wade, Sr. Community Gardener team: Red Hat Community Architecture & Leadership uri: http://communityleadershipteam.org http://TheOpenSourceWay.org gpg: AD0E0C41 --0rSojgWGcpz+ezC3 Content-Type: application/pgp-signature --0rSojgWGcpz+ezC3--