WRT- Signing: Who should sign tarballs? We should KISS (keep it standard & simple...) ie- 1. All tarballs should have md5 / other hash published in the downloads page and possibly a hash file with the tarball. 2. Each distro will sign its packages in its own means, such as signing key, certificate, etc. On Wednesday 30 November 2011 12:49:01 Ofer Schreiber wrote:
Following this discussion, I've created http://www.ovirt.org/wiki/Releases/First_Release in order to track the schedule/gaps/requirements for the first oVirt release.
Thoughts?
Ofer.
-----Original Message----- From: board-bounces@ovirt.org [mailto:board-bounces@ovirt.org] On Behalf Of Yaniv Kaul Sent: 29 November 2011 23:41 To: cctrieloff@redhat.com Cc: arch@ovirt.org; board@ovirt.org Subject: Re: First community release
On 11/29/2011 08:14 PM, Carl Trieloff wrote:
On 11/29/2011 12:58 PM, Barak Azulay wrote:
I think we should aim for a fast first release, meaning ASAP on jboss 5
The questions are:
1 - what is a release? a tag in all the repos to be picked up by each distro ? 2 - do we have any criteria on what is good enough for a release ? or any point in time that everybody feels ready? I would say a release needs to be at least.
1. a tag in the repos 2. tars posted on the site for easy download, build and install, with instructions. 3. these tars have basically been tested.
Not sure what the definition of 'tested' is, probably worth expanding it a bit. Y.
4. optional binary builds for different distros linked from the release page 5. a set of any relevant release notes.
Carl. _______________________________________________ Arch mailing list Arch@ovirt.org http://lists.ovirt.org/mailman/listinfo/arch
_______________________________________________ Board mailing list Board@ovirt.org http://lists.ovirt.org/mailman/listinfo/board
Arch mailing list Arch@ovirt.org http://lists.ovirt.org/mailman/listinfo/arch
-- /d "Do not look into laser with remaining eye." --On a laser pointer user-manual