Re: 38.0 & 38.0.5: An update on the upflits and branches

On 04/23/2015 11:16 AM, Sylvestre Ledru wrote:
> Hello,
>
> As you are probably aware, we are going to publish a release between 38 & 39 (called 38.0.5).
>
> In order to continue the development of 38 & 38.0.5 in parallel, we merged mozilla-beta (m-b)
> into mozilla-release (m-r).
>
> Before:
> m-b = 38.0.0 beta
> m-r = 37.0.2
>
> Now:
> m-b = 38.0.5 beta (even if we won't build any for now)
> m-r = 38.0 beta (next one being beta7)
>
> We will do regular m-r => m-b merges to make sure 38.0.5 is up to date.
>
> This does not impact aurora (aka 39). In case we have to make a new 37 dot release, we would use
> a relbranch.
>
> The m-b tree is closed avoid any confusion.
>
> Last but not least, uplift requests to 38 should be filled for mozilla-release
> 38.0.5 would be mozilla-beta. However, release managers and sheriffs will translate the information
> if the uplift requests are incorrect.

I don't understand all the consequences, can you clarify the following 
questions:
  - Are we removing the definitely beta-cycle, or only for this version?
  - As I understand m-r is our new beta? Then, why swapping the 2?
  - 38.0.5 version seems to suggests that this is a security fix of 38.0, if 
this is for a adding a feature, why not naming it 38.1.0?  Otherwise, why 
are we not making builds of 38.0.5?


-- 
Nicolas B. Pierron