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

James May <[email protected]>
Newsgroups gmane.comp.mozilla.devel.seamonkey
Message-ID <CABY6sLgd0-t6kG47s7PsLBdPFpx7xF=huzXsWK4zzeE=VTD=dA@mail.gmail.com>
Hi,

Apologies that this is slightly off topic.

On 23/04/2015 7:17 PM, "Sylvestre Ledru" <[email protected]> wrote:
>
> Hello,
>
> As you are probably aware, we are going to publish a release between 38 &
39 (called 38.0.5)

I'd appreciate if anyone could point to this announcement as it's the first
I've heard of it and I try to keep up with what's going on. Guess I've
missed a list somewhere 😒.

(I did a search of my email and couldn't find any references at all, with
google being of similar help. )

>
> 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.
>
> The schedule has been updated, links can be found on this blog post:
> http://release.mozilla.org/planning/2015/01/13/release-schedule.html
>
> On the behalf of the release management team,
> Sylvestre
> _______________________________________________
> dev-planning mailing list
> [email protected]
> https://lists.mozilla.org/listinfo/dev-planning

Thanks,
James
_______________________________________________
dev-planning mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-planning
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.