← Back to team overview

fuel-dev team mailing list archive

Re: [Fuel] MOST 4.1.x backport candidates

 

Me and Ryan have backported 34 of the commits listed earlier to
stable/4.1, we found that 1 commit is irrelevant (the fix is already
present in stable/4.1), and 5 more require special treatment (3 have
changes to files not present in stable/4.1 and 2 depend on patches for
neutron and glance).

We have created a single branch from all these comments so that they
constitute a dependency chain. Not all of them really have to depend
on each other, but merging them in the chronological order will
eliminate the possibility of merge conflicts due to wrong ordering.

I have included in Cc: of this email everyone who has committed the
original changes to master. If you are in this list, please review
backports of your commits and +1 if you believe that the fix should
work in 4.1. Easiest way to get the whole branch is:

git review -d 96884

Please remember that 4.1.1 should be released on June 5th, for that to
happen we need to have Hard Code Freeze on Monday June 2nd. This means
that all review requests on that branch should be merged before end of
day Monday, no exceptions.

Thanks,
-DmitryB

On Wed, May 28, 2014 at 8:12 PM, Mike Scherbakov
<mscherbakov@xxxxxxxxxxxx> wrote:
> Folks, we need to do it sooner than later.
> Actually, the date we are trying to catch is June 5th for 4.1.1 release. Let
> me know if there is anything which blocks us to release by that time.
>
> Thanks,
>
>
> On Tue, May 27, 2014 at 5:47 PM, Dmitry Borodaenko
> <dborodaenko@xxxxxxxxxxxx> wrote:
>>
>> Team,
>>
>> Attached is a list of 41 commits present in fuel-library stable/5.0
>> and not present in stable/4.1 (based on a script written by Ryan) that
>> contain fixes for Critical and High priority bugs and potentially
>> should be backported to 4.1.x series (as reviewed by me and Ryan).
>>
>> Please review and highlight items that you believe are not relevant
>> for 4.1. My assumption is that everything on this list should be
>> backported, and that we should repeat this exercise for fuel-web,
>> fuel-astute, and fuel-main repositories.
>>
>> Thanks,
>>
>> --
>> Dmitry Borodaenko
>>
>> --
>> Mailing list: https://launchpad.net/~fuel-dev
>> Post to     : fuel-dev@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~fuel-dev
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
>
> --
> Mike Scherbakov
> #mihgen
>



-- 
Dmitry Borodaenko


Follow ups

References