You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by Daan Hoogland <da...@gmail.com> on 2014/07/30 14:16:24 UTC
[ACS441]please test
As we already have some reports of problems with 4.4.0, I am
considering to start working on 4.4.1 right away.
The decision to actually go ahead should by preceded by confirmed
issues with 4.4.0 that have no reasonable work around but still, I
want to ask you all to have a look at any code you might have worked
on in 4.4-forward and check of my conflict resolving didn't introduce
regression. I get the feeling we will need a 4.4.1 and will put some
effort into it but can not do it alone (especially not the testing).
If you find you should fix something I broke, please branch a branch
for yourself and let me merge that branch back. This in anticipation
and as exercise for the way we are considering the work in future
releases. It will surely help us fine-tune 'our' gitflow.
kind regards,
--
Daan
Re: [ACS441]please test
Posted by Pierre-Luc Dion <pd...@cloudops.com>.
+1
Can help on the Release-note and tests.
*Pierre-Luc DION*
Architecte de Solution Cloud | Cloud Solutions Architect
t 855.652.5683
*CloudOps* Votre partenaire infonuagique* | *Cloud Solutions Experts
420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6
w cloudops.com *|* tw @CloudOps_
On Wed, Jul 30, 2014 at 8:33 AM, Erik Weber <te...@gmail.com> wrote:
> On Wed, Jul 30, 2014 at 2:16 PM, Daan Hoogland <da...@gmail.com>
> wrote:
>
> > As we already have some reports of problems with 4.4.0, I am
> > considering to start working on 4.4.1 right away.
> >
> >
>
> +1
>
>
>
> > The decision to actually go ahead should by preceded by confirmed
> > issues with 4.4.0 that have no reasonable work around but still, I
> > want to ask you all to have a look at any code you might have worked
> > on in 4.4-forward and check of my conflict resolving didn't introduce
> > regression. I get the feeling we will need a 4.4.1 and will put some
> > effort into it but can not do it alone (especially not the testing).
> >
> >
> As mentioned on IRC, I'll start testing the system vm templates with KVM
> and XenServer using the template from SBP built from the 4.4.0 tag.
>
>
>
> > If you find you should fix something I broke, please branch a branch
> > for yourself and let me merge that branch back. This in anticipation
> > and as exercise for the way we are considering the work in future
> > releases. It will surely help us fine-tune 'our' gitflow.
>
>
>
> Erik
>
Re: [ACS441]please test
Posted by Erik Weber <te...@gmail.com>.
On Wed, Jul 30, 2014 at 2:16 PM, Daan Hoogland <da...@gmail.com>
wrote:
> As we already have some reports of problems with 4.4.0, I am
> considering to start working on 4.4.1 right away.
>
>
+1
> The decision to actually go ahead should by preceded by confirmed
> issues with 4.4.0 that have no reasonable work around but still, I
> want to ask you all to have a look at any code you might have worked
> on in 4.4-forward and check of my conflict resolving didn't introduce
> regression. I get the feeling we will need a 4.4.1 and will put some
> effort into it but can not do it alone (especially not the testing).
>
>
As mentioned on IRC, I'll start testing the system vm templates with KVM
and XenServer using the template from SBP built from the 4.4.0 tag.
> If you find you should fix something I broke, please branch a branch
> for yourself and let me merge that branch back. This in anticipation
> and as exercise for the way we are considering the work in future
> releases. It will surely help us fine-tune 'our' gitflow.
Erik
Re: [ACS441]please test
Posted by Daan Hoogland <da...@gmail.com>.
Because we throw away the tag on a released version that way.
Maybe we should anyway as 4.4 has barely or not been tested before
releasing. Most if not all testing by citrix qa has been done on
4.4-forward and hardly anyone else has or manages to upgrade (clean
installs seem to work).
On Fri, Aug 1, 2014 at 12:38 PM, Anshul Gangwar
<an...@citrix.com> wrote:
> The order of cherry-picked commits is not maintained. i.e. the order in which commits are made in 4.4-forwrad is not same in 4.4. This will create more regressions instead of fixing.
>
> One fix(Hyper-V agent build is broken) which I made is occurred due to this. To verify fixes, which one has made some 2 months back are in correct order will take lot of effort.
>
> Why can't we simply rename 4.4-forward to 4.4?
>
>
> -----Original Message-----
> From: Daan Hoogland [mailto:daan.hoogland@gmail.com]
> Sent: Wednesday, July 30, 2014 5:46 PM
> To: dev
> Subject: [ACS441]please test
>
> As we already have some reports of problems with 4.4.0, I am considering to start working on 4.4.1 right away.
>
> The decision to actually go ahead should by preceded by confirmed issues with 4.4.0 that have no reasonable work around but still, I want to ask you all to have a look at any code you might have worked on in 4.4-forward and check of my conflict resolving didn't introduce regression. I get the feeling we will need a 4.4.1 and will put some effort into it but can not do it alone (especially not the testing).
>
> If you find you should fix something I broke, please branch a branch for yourself and let me merge that branch back. This in anticipation and as exercise for the way we are considering the work in future releases. It will surely help us fine-tune 'our' gitflow.
>
> kind regards,
> --
> Daan
--
Daan
RE: [ACS441]please test
Posted by Anshul Gangwar <an...@citrix.com>.
The order of cherry-picked commits is not maintained. i.e. the order in which commits are made in 4.4-forwrad is not same in 4.4. This will create more regressions instead of fixing.
One fix(Hyper-V agent build is broken) which I made is occurred due to this. To verify fixes, which one has made some 2 months back are in correct order will take lot of effort.
Why can't we simply rename 4.4-forward to 4.4?
-----Original Message-----
From: Daan Hoogland [mailto:daan.hoogland@gmail.com]
Sent: Wednesday, July 30, 2014 5:46 PM
To: dev
Subject: [ACS441]please test
As we already have some reports of problems with 4.4.0, I am considering to start working on 4.4.1 right away.
The decision to actually go ahead should by preceded by confirmed issues with 4.4.0 that have no reasonable work around but still, I want to ask you all to have a look at any code you might have worked on in 4.4-forward and check of my conflict resolving didn't introduce regression. I get the feeling we will need a 4.4.1 and will put some effort into it but can not do it alone (especially not the testing).
If you find you should fix something I broke, please branch a branch for yourself and let me merge that branch back. This in anticipation and as exercise for the way we are considering the work in future releases. It will surely help us fine-tune 'our' gitflow.
kind regards,
--
Daan