Hi, Rafael:

I am glad to get the final word here, and much relieved that 4.11.1.0 was not 
affected after all!

Thanks,

Yiping

On 9/28/18, 11:54 AM, "Rafael Weingärtner" <rafaelweingart...@gmail.com> wrote:

    Hello Yiping Zhang,
    
    It was a misunderstanding. CLOUDSTACK-10240 was never merged into 4.11. It
    was only merged into master (4.12). Indeed we had a problem with managed
    storage, but Mike and I already fixed it. However, it did not affect any
    released version of ACS.
    
    On Fri, Sep 28, 2018 at 12:56 PM Rohit Yadav <rohit.ya...@shapeblue.com>
    wrote:
    
    > Hi Yiping,
    >
    >
    > Based on what I can understand, the fix most likely went into master but
    > not the 4.11 branch. I've pinged Rafael on the PR:
    > https://github.com/apache/cloudstack/pull/2761
    >
    >
    > - Rohit
    >
    > <https://cloudstack.apache.org>
    >
    >
    >
    > ________________________________
    > From: Yiping Zhang <yzh...@marketo.com>
    > Sent: Friday, September 28, 2018 9:56:33 PM
    > To: dev@cloudstack.apache.org
    > Subject: Re: [DISCUSS] Release effort for 4.11.2.0
    >
    > Hi, Rohit:
    >
    > Back in July, there was a thread discussion here about CLOUDSTACK-10240.
    >
    > The gist of it is that the PR for CLOUDSTACK-10240 was merged into 4.11.x
    > branch and it introduced a regression.
    >
    > My question here is whether the fix for said regression is included in
    > 4.11.2.0 RC1 and onwards ?  We are waiting for this fix to start our ACS
    > upgrade to 4.11.2.0, so this is quite important for us.
    >
    > Thanks,
    >
    > Yiping
    >
    > On 8/28/18, 3:33 AM, "Rohit Yadav" <rohit.ya...@shapeblue.com> wrote:
    >
    >     All,
    >
    >
    >     We're about 4 weeks into the schedule, we've following items remaining
    > towards the 4.11.2.0 milestone:
    >
    >     https://github.com/apache/cloudstack/milestone/6
    >
    >
    >     In next 1-2 weeks, we'll aim to test and stabilize the 4.11 branch,
    > which will then lead to cutting of RC1.
    >
    >
    >     Please share if there are any blockers/critical/major issues you've
    > found in 4.11.0.0 or 4.11.1.0 releases that we should aim to fix in
    > 4.11.2.0. Thanks.
    >
    >
    >     - Rohit
    >
    >     <https://cloudstack.apache.org>
    >
    >
    >
    >     ________________________________
    >
    >     rohit.ya...@shapeblue.com
    >     www.shapeblue.com<http://www.shapeblue.com>
    >     Amadeus House, Floral Street, London  WC2E 9DPUK
    >     @shapeblue
    >
    >
    >
    >     From: Rohit Yadav
    >     Sent: Thursday, August 2, 2018 2:27:25 PM
    >     To: dev@cloudstack.apache.org; us...@cloudstack.apache.org
    >     Subject: [DISCUSS] Release effort for 4.11.2.0
    >
    >
    >     All,
    >
    >
    >     The recent CloudStack 4.11.1.0 release received a good reception but
    > this thread is to gather feedback especially list of bugs and issues from
    > the community that we should aim to fix towards the next minor LTS 
4.11.2.0
    > release.
    >
    >
    >     Here is a rough timeline proposal for the same:
    >
    >
    >     0-4 week: Get feedback from the community, gather and triage list of
    > issues, start fixing/testing/reviewing them
    >
    >     4-6 week: Stabilize 4.11 branch towards 4.11.2.0, cut RC and start
    > voting
    >
    >     6-8 week: Iterate over RCs/voting and release!
    >
    >
    >     To limit the scope for RM, blocker/critical issues will take priority.
    > Paul will continue as RM for the 4.11.2.0 release, with assistance from
    > Boris, Daan, and myself.
    >
    >
    >     For reference, this is the 4.11.2.0 milestone PR/issues list:
    >
    >     https://github.com/apache/cloudstack/milestone/6
    >
    >
    >     Thoughts, issues you want to discuss, feedback? Thanks.
    >
    >
    >     - Rohit
    >
    >
    >
    > rohit.ya...@shapeblue.com
    > www.shapeblue.com
    > Amadeus House, Floral Street, London  WC2E 9DPUK
    > @shapeblue
    >
    >
    >
    >
    
    -- 
    Rafael Weingärtner
    

Reply via email to