On Thu, Dec 02, 2010 at 03:03:56PM +0100, Diego Elio Pettenò wrote:
Il giorno gio, 02/12/2010 alle 10.58 +, Daniel P. Berrange ha
scritto:
I think this is really viable, because it implies we need another
week prior to creating the pre-release where we do what we currently
do with
On Thu, Dec 02, 2010 at 02:47:22AM +1100, Justin Clift wrote:
On 02/12/2010, at 2:26 AM, Diego Elio Pettenò wrote:
Il giorno mar, 30/11/2010 alle 21.09 +0100, Daniel Veillard ha scritto:
As indicated 10 days ago, today was time for a release, I didn't
had much time so I simply generated
On Thu, Dec 02, 2010 at 05:47:01AM +1100, Justin Clift wrote:
On 02/12/2010, at 5:26 AM, Diego Elio Pettenò wrote:
Il giorno gio, 02/12/2010 alle 02.47 +1100, Justin Clift ha scritto:
Looks like it might be time to put some kind of regression testing in
place, as a go/no-go release
On 02/12/2010, at 9:58 PM, Daniel P. Berrange wrote:
snip
I think this is really viable, because it implies we need another
Err... not really viable yeah?
week prior to creating the pre-release where we do what we currently
do with pre-release stabalization. With a monthly release cycle,
Il giorno gio, 02/12/2010 alle 10.58 +, Daniel P. Berrange ha
scritto:
I think this is really viable, because it implies we need another
week prior to creating the pre-release where we do what we currently
do with pre-release stabalization.
Note that I said “one week or less”.
- A
On 03/12/2010, at 1:03 AM, Diego Elio Pettenò wrote:
- A official list of supported platforms / OS combinations
- Run a test build on each combination before release
- Actually follow the 'bug fixes' only rule leading upto release
no matter how simple the new feature might appear.
And let
Daniel P. Berrange wrote:
Concept wise, do you reckon something like this would work:
+ a new libvirt-announce mailing list, low trafic, purely for release
announcements and similar
Along with us announcing a 'release candidate build through it (instead of
the
present approach). If
On 03/12/2010, at 4:04 PM, Jim Fehlig wrote:
I can deploy a release candidate tarball to the libvirt package in this
project quickly to test building across these various SuSE products. I
suspect there is an opportunity for some automation here as well.
Whichever way we go, I think automation
On 12/02/2010 03:03 PM, Diego Elio Pettenò wrote:
Il giorno gio, 02/12/2010 alle 10.58 +, Daniel P. Berrange ha
scritto:
I think this is really viable, because it implies we need another
week prior to creating the pre-release where we do what we currently
do with pre-release
Il giorno mar, 30/11/2010 alle 21.09 +0100, Daniel Veillard ha scritto:
As indicated 10 days ago, today was time for a release, I didn't
had much time so I simply generated a release from libvirt git
without much testing. Hopefully this will be okay !
Doesn't seem to be the case :/
In
On 02/12/2010, at 2:26 AM, Diego Elio Pettenò wrote:
Il giorno mar, 30/11/2010 alle 21.09 +0100, Daniel Veillard ha scritto:
As indicated 10 days ago, today was time for a release, I didn't
had much time so I simply generated a release from libvirt git
without much testing. Hopefully this
2010/12/1 Diego Elio Pettenò flamee...@gmail.com:
Il giorno mar, 30/11/2010 alle 21.09 +0100, Daniel Veillard ha scritto:
As indicated 10 days ago, today was time for a release, I didn't
had much time so I simply generated a release from libvirt git
without much testing. Hopefully this will
Il giorno gio, 02/12/2010 alle 02.47 +1100, Justin Clift ha scritto:
Looks like it might be time to put some kind of regression testing in
place, as a go/no-go release criteria.
May I suggest a 1-week (or less) window without merge of new
features/improvements, announced on a separate
On 02/12/2010, at 5:26 AM, Diego Elio Pettenò wrote:
Il giorno gio, 02/12/2010 alle 02.47 +1100, Justin Clift ha scritto:
Looks like it might be time to put some kind of regression testing in
place, as a go/no-go release criteria.
May I suggest a 1-week (or less) window without merge of
Il giorno gio, 02/12/2010 alle 05.47 +1100, Justin Clift ha scritto:
Concept wise, do you reckon something like this would work:
Yes that looks perfect to me.
--
Diego Elio Pettenò — “Flameeyes”
http://blog.flameeyes.eu/
If you found a .asc file in this mail and know not what it is,
it's a
As indicated 10 days ago, today was time for a release, I didn't
had much time so I simply generated a release from libvirt git
without much testing. Hopefully this will be okay !
Release is available as usual at
ftp://libvirt.org/libvirt/
There is actually a number of significant
16 matches
Mail list logo
