At the workshop in the release / roadmap working session we agreed that around November 16th we see how all the distro's are making out in creating a release for oVirt and set the date for the first community release. Please have your comments / feedback for that time period, at which point I will start the release discussions. regards Carl.
On 11/07/2011 06:51 PM, Carl Trieloff wrote:
At the workshop in the release / roadmap working session we agreed that around November 16th we see how all the distro's are making out in creating a release for oVirt and set the date for the first community release.
Please have your comments / feedback for that time period, at which point I will start the release discussions.
regards Carl. _______________________________________________ Board mailing list Board@ovirt.org http://lists.ovirt.org/mailman/listinfo/board
Hi All, Not sure where we stand with the first release but I think we should take into account the jboss version we use before releasing. We currently deploy on jboss as 5, but we started working on deployment on jboss as 7. Releasing on AS 5 and then moving to AS 7 might require some upgrade path and it is a time consuming task to do that. Since we already started working on the deployment on jboss AS 7, I think it might worth holding back first 'formal' release until it is done. It will help us avoiding upgrade support and get all the benefits of using as7 (startup time, memory/cpu foot-print etc.) - get better reviews? Livnat
-----Original Message----- From: board-bounces@ovirt.org [mailto:board-bounces@ovirt.org] On Behalf Of Livnat Peer Sent: 29 November 2011 17:59 To: cctrieloff@redhat.com Cc: arch@ovirt.org; board@ovirt.org Subject: Re: First community release
On 11/07/2011 06:51 PM, Carl Trieloff wrote:
At the workshop in the release / roadmap working session we agreed
that
around November 16th we see how all the distro's are making out in creating a release for oVirt and set the date for the first community release.
Please have your comments / feedback for that time period, at which point I will start the release discussions.
regards Carl. _______________________________________________ Board mailing list Board@ovirt.org http://lists.ovirt.org/mailman/listinfo/board
Hi All, Not sure where we stand with the first release but I think we should take into account the jboss version we use before releasing.
We currently deploy on jboss as 5, but we started working on deployment on jboss as 7. Releasing on AS 5 and then moving to AS 7 might require some upgrade path and it is a time consuming task to do that.
I am not sure we MUST support upgrade path, specifically in such early version.
Since we already started working on the deployment on jboss AS 7, I think it might worth holding back first 'formal' release until it is done. It will help us avoiding upgrade support and get all the benefits of using as7 (startup time, memory/cpu foot-print etc.) - get better reviews?
Livnat _______________________________________________ Board mailing list Board@ovirt.org http://lists.ovirt.org/mailman/listinfo/board
On 11/29/2011 05:59 PM, Livnat Peer wrote:
On 11/07/2011 06:51 PM, Carl Trieloff wrote:
At the workshop in the release / roadmap working session we agreed that around November 16th we see how all the distro's are making out in creating a release for oVirt and set the date for the first community release.
Please have your comments / feedback for that time period, at which point I will start the release discussions.
regards Carl. _______________________________________________ Board mailing list Board@ovirt.org http://lists.ovirt.org/mailman/listinfo/board
Hi All, Not sure where we stand with the first release but I think we should take into account the jboss version we use before releasing.
We currently deploy on jboss as 5, but we started working on deployment on jboss as 7. Releasing on AS 5 and then moving to AS 7 might require some upgrade path and it is a time consuming task to do that.
Since we already started working on the deployment on jboss AS 7, I think it might worth holding back first 'formal' release until it is done. It will help us avoiding upgrade support and get all the benefits of using as7 (startup time, memory/cpu foot-print etc.) - get better reviews?
Livnat
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? Thanks Barak Azulay
_______________________________________________ Board mailing list Board@ovirt.org http://lists.ovirt.org/mailman/listinfo/board
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. 4. optional binary builds for different distros linked from the release page 5. a set of any relevant release notes. Carl.
They should also be signed as well... On Nov 29, 2011, at 1: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. 4. optional binary builds for different distros linked from the release page 5. a set of any relevant release notes.
Carl. _______________________________________________ Board mailing list Board@ovirt.org http://lists.ovirt.org/mailman/listinfo/board
-- Jim Jagielski | jimjag@redhat.com | 443-324-8390 (cell)
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
On 11/30/2011 02:03 AM, David Jorm wrote:
3. these tars have basically been tested. Not sure what the definition of 'tested' is, probably worth expanding it a bit. Y. I would think just smoke tested.
David
I would like to believe the code should pass smoke tests at all times. When it doesn't, it's a regression we should strive to fix asap. Y.
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
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
On 11/30/2011 06:41 AM, Doron Fediuck wrote:
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.
+1 Though for the case of oVirt Node, since the ISO isn't in Fedora officially, all we will provide is the md5 of the ISO itself. Perry
On Wed, Nov 30, 2011 at 12:41 PM, Doron Fediuck <dfediuck@redhat.com> wrote:
1. All tarballs should have md5 / other hash published in the downloads page and possibly a hash file with the tarball.
SHA512 please e.g. http://collectd.org/files/SHA512SUM
2. Each distro will sign its packages in its own means, such as signing key, certificate, etc.
It would be nice if upstream release manager could sign release tag in git. Alan
On 11/29/2011 04:40 PM, Yaniv Kaul wrote:
3. these tars have basically been tested.
Not sure what the definition of 'tested' is, probably worth expanding it a bit. Y.
this can be fuzzy, but on other projects it is. Have a few people down load the tar, follow the instructions and get it installed and running + passing the tests that are checked in. Carl.
On 11/30/2011 09:20 AM, Carl Trieloff wrote:
3. these tars have basically been tested. Not sure what the definition of 'tested' is, probably worth expanding it a bit. Y.
On 11/29/2011 04:40 PM, Yaniv Kaul wrote: this can be fuzzy, but on other projects it is.
Have a few people down load the tar, follow the instructions and get it installed and running + passing the tests that are checked in.
Carl. _______________________________________________ Arch mailing list Arch@ovirt.org http://lists.ovirt.org/mailman/listinfo/arch Have we defined the process for approving the release (like having a vote which gets at least 3 +1's and no -1's)?
Hi All, Not sure where we stand with the first release but I think we should take into account the jboss version we use before releasing.
We currently deploy on jboss as 5, but we started working on deployment on jboss as 7. Releasing on AS 5 and then moving to AS 7 might require some upgrade path and it is a time consuming task to do that.
Since we already started working on the deployment on jboss AS 7, I think it might worth holding back first 'formal' release until it is done. It will help us avoiding upgrade support and get all the benefits of using as7 (startup time, memory/cpu foot-print etc.) - get better reviews?
Please note that JBoss AS 5 has not been updated with any async security patches since it was released in 2009. There are multiple known high impact security flaws that affect it. I would prefer we only ship against AS 7, as it incorporates fixes for these flaws. David
participants (11)
-
Alan Pevec -
Barak Azulay -
Carl Trieloff -
David Jorm -
Doron Fediuck -
Jim Jagielski -
Jon Choate -
Livnat Peer -
Ofer Schreiber -
Perry Myers -
Yaniv Kaul