Re: Soft code freeze for Firefox 87 starts February 18

2021-02-22 Thread Julien Cristau
The last merge of autoland to central for 87 has now happened, so the soft
freeze is over, and development for 88 is open.

Cheers,
Julien

On Mon, Feb 15, 2021 at 4:28 PM Julien Cristau  wrote:

> Hi all,
>
> With Firefox 86 RC shipping soon, we are nearing the end of the Nightly 87
> cycle.
>
> In order to avoid invalidating the testing we get out of late Nightly and
> to ensure that we can roll out Beta 87 to a wider audience with confidence
> next week, we'd like to ask that any risky changes be avoided from Thursday
> February 18 until after the version bump to 88 on February 22.
>
> Some reminders for the soft code freeze period:
>
> Do:
> - Be ready to back out patches that cause crash spikes, new crashes,
> severe regressions
> - Monitor new regressions and escalate merge blockers
> - Support release management by prioritizing fixing of merge blockers
>
> Do Not:
> - Land a risky patch or a large patch
> - Land new features (that affect the current Nightly version) — be mindful
> that code behind NIGHTLY_BUILD or RELEASE_OR_BETA ifdefs can lead to
> unexpected CI results
> - Flip prefs that enable new Features that were untested in the Nightly
> cycle
> - Plan to kick off new experiments that might impact a feature's merge
> readiness
>
> Please let us know if you have any questions/concerns.
>
> Thanks,
> Julien
> --
> Firefox Release Manager
>
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Soft code freeze for Firefox 87 starts February 18

2021-02-15 Thread Julien Cristau
Hi all,

With Firefox 86 RC shipping soon, we are nearing the end of the Nightly 87
cycle.

In order to avoid invalidating the testing we get out of late Nightly and
to ensure that we can roll out Beta 87 to a wider audience with confidence
next week, we'd like to ask that any risky changes be avoided from Thursday
February 18 until after the version bump to 88 on February 22.

Some reminders for the soft code freeze period:

Do:
- Be ready to back out patches that cause crash spikes, new crashes, severe
regressions
- Monitor new regressions and escalate merge blockers
- Support release management by prioritizing fixing of merge blockers

Do Not:
- Land a risky patch or a large patch
- Land new features (that affect the current Nightly version) — be mindful
that code behind NIGHTLY_BUILD or RELEASE_OR_BETA ifdefs can lead to
unexpected CI results
- Flip prefs that enable new Features that were untested in the Nightly
cycle
- Plan to kick off new experiments that might impact a feature's merge
readiness

Please let us know if you have any questions/concerns.

Thanks,
Julien
-- 
Firefox Release Manager
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: Soft code freeze for Firefox 85 starts December 10

2020-12-14 Thread Julien Cristau
Hi all,

The last merge from autoland to mozilla-central before the version bump has
now happened, so the soft freeze for 85 is over, and development for
Firefox 86 is underway.

Cheers,
Julien

On Tue, Dec 8, 2020 at 5:34 PM Julien Cristau  wrote:

> Hi all,
>
> With Firefox 84 RC week upon us, we are nearing the end of the Nightly 85
> cycle.
>
> In order to avoid invalidating the testing we get out of late Nightly and
> to ensure that we can roll out Beta 84 to a wider audience with confidence,
> we'd like to ask that any risky changes be avoided from Thursday December
> 10 until after the version bump to 86 on December 14.
>
> Some reminders for the soft code freeze period:
>
> Do:
> - Be ready to back out patches that cause crash spikes, new crashes,
> severe regressions
> - Monitor new regressions and escalate merge blockers
> - Support release management by prioritizing fixing of merge blockers
>
> Do Not:
> - Land a risky patch or a large patch
> - Land new features (that affect the current Nightly version) — be mindful
> that code behind NIGHTLY_BUILD or RELEASE_OR_BETA ifdefs can lead to
> unexpected CI results
> - Flip prefs that enable new Features that were untested in the Nightly
> cycle
> - Plan to kick off new experiments that might impact a feature's merge
> readiness
>
> Please let us know if you have any questions/concerns.
>
> Thanks,
> Julien & the Release Management team
>
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Soft code freeze for Firefox 85 starts December 10

2020-12-08 Thread Julien Cristau
Hi all,

With Firefox 84 RC week upon us, we are nearing the end of the Nightly 85
cycle.

In order to avoid invalidating the testing we get out of late Nightly and
to ensure that we can roll out Beta 84 to a wider audience with confidence,
we'd like to ask that any risky changes be avoided from Thursday December
10 until after the version bump to 86 on December 14.

Some reminders for the soft code freeze period:

Do:
- Be ready to back out patches that cause crash spikes, new crashes, severe
regressions
- Monitor new regressions and escalate merge blockers
- Support release management by prioritizing fixing of merge blockers

Do Not:
- Land a risky patch or a large patch
- Land new features (that affect the current Nightly version) — be mindful
that code behind NIGHTLY_BUILD or RELEASE_OR_BETA ifdefs can lead to
unexpected CI results
- Flip prefs that enable new Features that were untested in the Nightly
cycle
- Plan to kick off new experiments that might impact a feature's merge
readiness

Please let us know if you have any questions/concerns.

Thanks,
Julien & the Release Management team
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: Soft code freeze for Firefox 84 starts November 12

2020-11-16 Thread Julien Cristau
Hi,

84 has now merged to beta, mozilla-central is bumped to 85, so the soft
freeze is over.

Cheers,
Julien

On Tue, Nov 10, 2020 at 1:21 PM Pascal Chevrel  wrote:

> Hi all,
>
> With Firefox 83 RC shipping soon, we are nearing the end of the Nightly 84
> cycle.
>
> In order to avoid invalidating the testing we get out of late Nightly and
> to ensure that we can roll out Beta 84 to a wider audience with confidence,
> we'd like to ask that any risky changes be avoided from Thursday November
> 12
> until after the version bump to 85 on November 16.
>
> Some reminders for the soft code freeze period:
>
> Do:
> - Be ready to back out patches that cause crash spikes, new crashes, severe
> regressions
> - Monitor new regressions and escalate merge blockers
> - Support release management by prioritizing fixing of merge blockers
>
> Do Not:
> - Land a risky patch or a large patch
> - Land new features (that affect the current Nightly version) — be mindful
> that code behind NIGHTLY_BUILD or RELEASE_OR_BETA ifdefs can lead to
> unexpected CI results
> - Flip prefs that enable new Features that were untested in the Nightly
> cycle
> - Plan to kick off new experiments that might impact a feature's merge
> readiness
>
> Please let us know if you have any questions/concerns.
>
> Thanks,
> Pascal & the Release Management team
>
> --
> Pascal Chevrel
> Firefox Release Manager
> + Firefox Nightly community management
> https://fx-trains.herokuapp.com
>
>
> ___
> dev-platform mailing list
> dev-platform@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platform
>
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: Soft code freeze for Firefox 82 starts September 17

2020-09-21 Thread Julien Cristau
Development is now open for 83, the last merge from autoland to
mozilla-central before 82 merges to beta has happened.

Cheers,
Julien

On Mon, Sep 14, 2020 at 10:36 AM Julien Cristau 
wrote:

> Hi all,
>
> With Firefox 81 merging to mozilla-release later today, we are nearing the
> end of the Nightly 82 cycle.
>
> In order to avoid invalidating the testing we get out of late Nightly
> and to ensure that we can roll out 82 Betas to a wider audience with
> confidence, we'd like to ask that any risky changes be avoided from
> Thursday September 17 until after the version bump to 83 on September 21.
>
> Some reminders for the soft code freeze period:
>
> Do:
> - Be ready to back out patches that cause crash spikes, new crashes,
> severe regressions
> - Monitor new regressions and escalate merge blockers
> - Support release management by prioritizing fixing of merge blockers
>
> Do Not:
> - Land a risky patch or a large patch
> - Land new features (that affect the current Nightly version) — be mindful
> that code behind NIGHTLY_BUILD or RELEASE_OR_BETA ifdefs can lead to
> unexpected CI results
> - Flip prefs that enable new Features that were untested in the Nightly
> cycle
> - Plan to kick off new experiments that might impact a feature's merge
> readiness
>
> Please let us know if you have any questions/concerns.
>
> Thanks,
> Julien and the release management team
>
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Soft code freeze for Firefox 82 starts September 17

2020-09-14 Thread Julien Cristau
Hi all,

With Firefox 81 merging to mozilla-release later today, we are nearing the
end of the Nightly 82 cycle.

In order to avoid invalidating the testing we get out of late Nightly
and to ensure that we can roll out 82 Betas to a wider audience with
confidence, we'd like to ask that any risky changes be avoided from
Thursday September 17 until after the version bump to 83 on September 21.

Some reminders for the soft code freeze period:

Do:
- Be ready to back out patches that cause crash spikes, new crashes, severe
regressions
- Monitor new regressions and escalate merge blockers
- Support release management by prioritizing fixing of merge blockers

Do Not:
- Land a risky patch or a large patch
- Land new features (that affect the current Nightly version) — be mindful
that code behind NIGHTLY_BUILD or RELEASE_OR_BETA ifdefs can lead to
unexpected CI results
- Flip prefs that enable new Features that were untested in the Nightly
cycle
- Plan to kick off new experiments that might impact a feature's merge
readiness

Please let us know if you have any questions/concerns.

Thanks,
Julien and the release management team
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: Soft code freeze for Firefox 78 starts May 28

2020-06-01 Thread Julien Cristau
Hi,

The merge of 78 to beta is in progress, new changes landing now will target
79; please consider the soft code freeze lifted.

Thanks,
Julien

On Mon, May 25, 2020 at 2:15 PM Julien Cristau  wrote:

> With Firefox 77 RC shipping soon, we are nearing the end of the Nightly 78
> cycle.
>
> In order to avoid invalidating the testing we get out of late Nightly and
> to ensure that we can roll out Beta 78 to a wider audience with confidence
> next week, we'd like to ask that any risky changes be avoided from Thursday
> May 28 until after the version bump to 79 on June 1st.  This also means
> that by mid-week, feature work targeting 78 should be complete and ready to
> ride the trains.
>
> Some reminders for the soft code freeze period:
>
> Do:
> - Be ready to back out patches that cause crash spikes, new crashes,
> severe regressions
> - Monitor new regressions and escalate merge blockers
> - Support release management by prioritizing fixing of merge blockers
>
> Do Not:
> - Land a risky patch or a large patch
> - Land new features (that affect the current Nightly version) — be mindful
> that code behind NIGHTLY_BUILD or RELEASE_OR_BETA ifdefs can lead to
> unexpected CI results
> - Flip prefs that enable new Features that were untested in the Nightly
> cycle
> - Plan to kick off new experiments that might impact a feature's merge
> readiness
>
> Please let us know if you have any questions/concerns.
>
> Thanks,
> Julien & the Release Management team
>
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Soft code freeze for Firefox 78 starts May 28

2020-05-25 Thread Julien Cristau
With Firefox 77 RC shipping soon, we are nearing the end of the Nightly 78
cycle.

In order to avoid invalidating the testing we get out of late Nightly and
to ensure that we can roll out Beta 78 to a wider audience with confidence
next week, we'd like to ask that any risky changes be avoided from Thursday
May 28 until after the version bump to 79 on June 1st.  This also means
that by mid-week, feature work targeting 78 should be complete and ready to
ride the trains.

Some reminders for the soft code freeze period:

Do:
- Be ready to back out patches that cause crash spikes, new crashes, severe
regressions
- Monitor new regressions and escalate merge blockers
- Support release management by prioritizing fixing of merge blockers

Do Not:
- Land a risky patch or a large patch
- Land new features (that affect the current Nightly version) — be mindful
that code behind NIGHTLY_BUILD or RELEASE_OR_BETA ifdefs can lead to
unexpected CI results
- Flip prefs that enable new Features that were untested in the Nightly
cycle
- Plan to kick off new experiments that might impact a feature's merge
readiness

Please let us know if you have any questions/concerns.

Thanks,
Julien & the Release Management team
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: Soft code freeze for Firefox 75 starts March 5

2020-03-09 Thread Julien Cristau
Hi,

The last merge from autoland to central for 75 has happened, you can now
consider the soft code freeze lifted, new changes will land for 76.

Cheers,
Julien

On Mon, Mar 2, 2020 at 10:48 AM Julien Cristau  wrote:

> Hi all,
>
> With Firefox 74 RC shipping today, we are nearing the end of the Nightly
> 75 cycle.
>
> In order to avoid invalidating the testing we get out of late Nightly and
> to ensure that we can roll out Beta 75 to a wider audience with confidence,
> we'd like to ask that any risky changes be avoided from Thursday March 5th
> until after the version bump to 76 on March 9th.
>
> Some reminders for the soft code freeze period:
>
> Do:
> - Be ready to back out patches that cause crash spikes, new crashes,
> severe regressions
> - Monitor new regressions and escalate merge blockers
> - Support release management by prioritizing fixing of merge blockers
>
> Do Not:
> - Land a risky patch or a large patch
> - Land new features (that affect the current Nightly version) — be mindful
> that code behind NIGHTLY_BUILD or RELEASE_OR_BETA ifdefs can lead to
> unexpected CI results
> - Flip prefs that enable new Features that were untested in the Nightly
> cycle
> - Plan to kick off new experiments that might impact a feature's merge
> readiness
>
> Please let us know if you have any questions/concerns.
>
> Thanks,
> Julien & the Release Management team
>
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Soft code freeze for Firefox 75 starts March 5

2020-03-02 Thread Julien Cristau
Hi all,

With Firefox 74 RC shipping today, we are nearing the end of the Nightly 75
cycle.

In order to avoid invalidating the testing we get out of late Nightly and
to ensure that we can roll out Beta 75 to a wider audience with confidence,
we'd like to ask that any risky changes be avoided from Thursday March 5th
until after the version bump to 76 on March 9th.

Some reminders for the soft code freeze period:

Do:
- Be ready to back out patches that cause crash spikes, new crashes, severe
regressions
- Monitor new regressions and escalate merge blockers
- Support release management by prioritizing fixing of merge blockers

Do Not:
- Land a risky patch or a large patch
- Land new features (that affect the current Nightly version) — be mindful
that code behind NIGHTLY_BUILD or RELEASE_OR_BETA ifdefs can lead to
unexpected CI results
- Flip prefs that enable new Features that were untested in the Nightly
cycle
- Plan to kick off new experiments that might impact a feature's merge
readiness

Please let us know if you have any questions/concerns.

Thanks,
Julien & the Release Management team
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: Soft code freeze for Firefox 72 starts November 25

2019-12-03 Thread Julien Cristau
The next merge to central will have a 73 milestone, so please consider the
soft freeze lifted.

Thanks,
Julien

On Thu, Nov 21, 2019 at 4:25 PM Julien Cristau  wrote:

> Hi all,
>
> we're fast approaching the start of the 72 beta cycle on December 2nd,
> with our "Feature complete" milestone for 72 tomorrow, November 22nd.
>
> In order to avoid invalidating the testing we get out of late Nightly and
> to ensure that we can roll out Beta 72 to a wider audience with confidence,
> we'd like to ask that any risky changes be avoided from November 25 until
> after the version bump
> to 73 on December 2nd.
>
> Some reminders for the soft code freeze period:
>
> Do:
> - Be ready to back out patches that cause crash spikes, new crashes,
> severe regressions
> - Monitor new regressions and escalate merge blockers
> - Support release management by prioritizing fixing of merge blockers
>
> Do Not:
> - Land a risky patch or a large patch
> - Land new features (that affect the current Nightly version) — be mindful
> that code behind NIGHTLY_BUILD or RELEASE_OR_BETA ifdefs can lead to
> unexpected CI results
> - Flip prefs that enable new Features that were untested in the Nightly
> cycle
> - Plan to kick off new experiments that might impact a feature's merge
> readiness
>
> Please let us know if you have any questions/concerns.
>
> Thanks,
> Julien and the Release Management team
>
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Soft code freeze for Firefox 72 starts November 25

2019-11-21 Thread Julien Cristau
Hi all,

we're fast approaching the start of the 72 beta cycle on December 2nd, with
our "Feature complete" milestone for 72 tomorrow, November 22nd.

In order to avoid invalidating the testing we get out of late Nightly and
to ensure that we can roll out Beta 72 to a wider audience with confidence,
we'd like to ask that any risky changes be avoided from November 25 until
after the version bump
to 73 on December 2nd.

Some reminders for the soft code freeze period:

Do:
- Be ready to back out patches that cause crash spikes, new crashes, severe
regressions
- Monitor new regressions and escalate merge blockers
- Support release management by prioritizing fixing of merge blockers

Do Not:
- Land a risky patch or a large patch
- Land new features (that affect the current Nightly version) — be mindful
that code behind NIGHTLY_BUILD or RELEASE_OR_BETA ifdefs can lead to
unexpected CI results
- Flip prefs that enable new Features that were untested in the Nightly
cycle
- Plan to kick off new experiments that might impact a feature's merge
readiness

Please let us know if you have any questions/concerns.

Thanks,
Julien and the Release Management team
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: Soft code freeze for Firefox 71, Oct 14

2019-10-21 Thread Julien Cristau
Hi everyone,

anything that lands on integration trees (inbound or autoland) from now on
will be after the cutoff for 71, so consider the soft freeze lifted.

Thanks,
Julien

On Mon, Oct 14, 2019 at 1:02 PM Pascal Chevrel  wrote:

> Hi all,
>
> We will be merging Firefox 71 from mozilla-central to beta for the first
> time later today, Oct. 14.
>
> In order to avoid invalidating the testing we get out of late Nightly
> and the early Developer Edition builds and to ensure that we can roll
> out Beta 71 to a wider audience with confidence, we'd like to ask that
> any risky changes be avoided from Oct. 14 until after the version bump
> to 72 on Oct 21.
>
> Some reminders for the soft code freeze period:
>
> Do:
> - Be ready to back out patches that cause crash spikes, new crashes,
> severe regressions
> - Monitor new regressions and escalate merge blockers
> - Support release management by prioritizing fixing of merge blockers
>
> Do Not:
> - Land a risky patch or a large patch
> - Land new features (that affects the current Nightly version) — be
> mindful that code behind NIGHTLY_BUILD or RELEASE_OR_BETA ifdefs can
> lead to unexpected CI results
> - Flip prefs that enable new Features that were untested in Nightly cycle
> - Plan to kick off new experiments that might impact a feature's merge
> readiness
>
> Please let us know if you have any questions/concerns.
>
> Thanks,
>
> Release Management Team
>
> --
> Pascal Chevrel
> Firefox Release Manager
> + Firefox Nightly community management
>
> ___
> dev-platform mailing list
> dev-platform@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platform
>
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: Soft code freeze for Firefox 70, Aug 26

2019-09-02 Thread Julien Cristau
As of now mozilla-central is version 71.  The soft freeze is thus over,
land away!

Cheers,
Julien

On Wed, Aug 21, 2019 at 7:50 PM Liz Henry (:lizzard) 
wrote:

> Correction, avoid risky changes from Aug 26th to Sept 2.
> Thanks to kwierso for pointing out my typo.
>
> - Liz
>
>
> On Wed, Aug 21, 2019 at 10:41 AM Liz Henry (:lizzard) 
> wrote:
>
>> Hi there,
>>
>> On August 26th, we will be merging Firefox 70 from mozilla-central to beta
>> for the first time. In order to avoid invalidating the testing we get
>> out of late Nightly and the early Developer Edition builds and to ensure
>> that we can roll out Beta 70 to a wider audience with confidence, we'd
>> like to ask that any risky changes be avoided from July 1st until after
>> the version bump to 71 on Sept 2. Please also be mindful of any
>> landings late this week or over the weekend as there will be very little
>> buffer between the first merge and shipping the 70.0b1 builds.
>>
>> Some reminders for the soft code freeze period:
>>
>> Do:
>> - Be ready to back out patches that cause crash spikes, new crashes,
>> severe regressions
>> - Monitor new regressions and escalate merge blockers
>> - Support release management by prioritizing fixing of merge blockers
>>
>> Do Not:
>> - Land a risky patch or a large patch
>> - Land new features (that affects the current Nightly version) — be
>> mindful that code behind NIGHTLY_BUILD or RELEASE_OR_BETA ifdefs can
>> lead to unexpected CI results
>> - Flip prefs that enable new Features that were untested in Nightly cycle
>> - Plan to kick off new experiments that might impact a feature's merge
>> readiness
>>
>> Please let us know if you have any questions/concerns.
>>
>> Thanks,
>>
>> Release Management Team
>>
>>
>> --
>> 
>> Liz Henry (:lizzard)
>> Firefox Release Manager
>> lhe...@mozilla.com
>>
>
>
> --
> 
> Liz Henry (:lizzard)
> Firefox Release Manager
> lhe...@mozilla.com
> ___
> firefox-dev mailing list
> firefox-...@mozilla.org
> https://mail.mozilla.org/listinfo/firefox-dev
>
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: Soft code freeze for Firefox 68 starts May 6

2019-05-20 Thread Julien Cristau
Hi,

With a week of delay as per
https://mail.mozilla.org/pipermail/firefox-dev/2019-May/007066.html, the
Firefox 68 soft code freeze is now over.  Changes landing in integration
now will be in 69.

Cheers,
Julien

On Fri, May 3, 2019 at 9:05 AM Julien Cristau  wrote:

> Hi all,
>
> On May 6, we will be merging Firefox 68 from mozilla-central to beta
> for the first time. In order to avoid invalidating the testing we get
> out of late Nightly and the early Developer Edition builds and to ensure
> that we can roll out Beta 68 to a wider audience with confidence, we'd
> like to ask that any risky changes be avoided from May 6 until after
> the version bump to 69 on May 13. Please also be mindful of any
> landings between now and Monday as there will be very little
> buffer between the first merge and shipping the 68.0b1 builds.
>
> Some reminders for the soft code freeze period:
>
> Do:
> - Be ready to backout patches that cause crash spikes, new crashes,
> severe regressions
> - Monitor new regressions and escalate merge blockers
> - Support release management by prioritizing fixing of merge blockers
>
> Do Not:
> - Land a risky patch or a large patch
> - Land new features (that affects the current Nightly version) — be
> mindful that code behind NIGHTLY_BUILD or RELEASE_OR_BETA ifdefs can
> lead to unexpected CI results
> - Flip prefs that enable new Features that were untested in Nightly cycle
> - Plan to kick off new experiments that might impact a feature's merge
> readiness
>
> Please let us know if you have any questions/concerns.
>
> Thanks,
> Julien, for the Release Management Team
>
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Soft code freeze for Firefox 68 starts May 6

2019-05-03 Thread Julien Cristau
Hi all,

On May 6, we will be merging Firefox 68 from mozilla-central to beta
for the first time. In order to avoid invalidating the testing we get
out of late Nightly and the early Developer Edition builds and to ensure
that we can roll out Beta 68 to a wider audience with confidence, we'd
like to ask that any risky changes be avoided from May 6 until after
the version bump to 69 on May 13. Please also be mindful of any
landings between now and Monday as there will be very little
buffer between the first merge and shipping the 68.0b1 builds.

Some reminders for the soft code freeze period:

Do:
- Be ready to backout patches that cause crash spikes, new crashes,
severe regressions
- Monitor new regressions and escalate merge blockers
- Support release management by prioritizing fixing of merge blockers

Do Not:
- Land a risky patch or a large patch
- Land new features (that affects the current Nightly version) — be
mindful that code behind NIGHTLY_BUILD or RELEASE_OR_BETA ifdefs can
lead to unexpected CI results
- Flip prefs that enable new Features that were untested in Nightly cycle
- Plan to kick off new experiments that might impact a feature's merge
readiness

Please let us know if you have any questions/concerns.

Thanks,
Julien, for the Release Management Team
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: Soft code freeze for Firefox 67 starts March 11

2019-03-19 Thread Julien Cristau
To confirm:

The version number on central was bumped to 68 on central yesterday, so the
67 soft code freeze is over.  Land away.

Cheers,
Julien

On Fri, Mar 8, 2019 at 9:45 AM Pascal Chevrel  wrote:

> Hi all,
>
> On March 11, we will be merging Firefox 67 from mozilla-central to beta
> for the first time. In order to avoid invalidating the testing we get
> out of late Nightly and the early Developer Edition builds and to ensure
> that we can roll out Beta 67 to a wider audience with confidence, we'd
> like to ask that any risky changes be avoided from March 11 until after
> the version bump to 68 on March 18. Please also be mindful of any
> landings late this week or over the weekend as there will be very little
> buffer between the first merge and shipping the 67.0b1 builds.
>
> Some reminders for the soft code freeze period:
>
> Do:
> - Be ready to backout patches that cause crash spikes, new crashes,
> severe regressions
> - Monitor new regressions and escalate merge blockers
> - Support release management by prioritizing fixing of merge blockers
>
> Do Not:
> - Land a risky patch or a large patch
> - Land new features (that affects the current Nightly version) — be
> mindful that code behind NIGHTLY_BUILD or RELEASE_OR_BETA ifdefs can
> lead to unexpected CI results
> - Flip prefs that enable new Features that were untested in Nightly cycle
> - Plan to kick off new experiments that might impact a feature's merge
> readiness
>
> Please let us know if you have any questions/concerns.
>
> Thanks,
>
> Release Management Team
>
> --
> Pascal Chevrel
> Firefox Release Manager
> ___
> dev-platform mailing list
> dev-platform@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platform
>
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: Intent to implement and ship: Gamepad Extensions `multi touch` and `light indicator`

2019-02-26 Thread Julien Cristau
On Mon, Feb 25, 2019 at 8:45 PM Daosheng Mu  wrote:

> Is this feature restricted to secure contexts? Nope
>

Why not?

Cheers,
Julien
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Soft code freeze for Firefox 64 starts October 15

2018-10-10 Thread Julien Cristau
Hi all,

On October 15, we will be merging Firefox 64 from mozilla-central to beta
for the first time. In order to avoid invalidating the testing we get out
of late Nightly and the early Developer Edition builds and to ensure that
we can roll out Beta 64 to a wider audience with confidence, we'd like to
ask that any risky changes be avoided from October 15 until after the
version bump to 65 on October 22.  Please also be mindful of any landings
late this week or over the weekend: we're shortening the soft code freeze
this cycle to reduce confusion and friction, but that means we don't have a
buffer between the first merge and shipping the 64.0b1 builds.

Some reminders for the soft code freeze period:

Do:
- Be ready to backout patches that cause crash spikes, new crashes,
severe regressions
- Monitor new regressions and escalate merge blockers
- Support release management by prioritizing fixing of merge blockers

Do Not:
- Land a risky patch or a large patch
- Land new features (that affects the current Nightly version) — be
mindful that code behind NIGHTLY_BUILD or RELEASE_OR_BETA ifdefs can
lead to unexpected CI results
- Flip prefs that enable new Features that were untested in Nightly cycle
- Plan to kick off new experiments that might impact a feature's merge
readiness

Please let us know if you have any questions/concerns.

Thanks,

Release Management Team
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: Soft code freeze for Firefox 60 starts March 1

2018-03-12 Thread Julien Cristau
The version bump to 61 has landed, central thawed and is open for business.

Thanks,
Julien

On Thu, Feb 22, 2018 at 3:37 PM, Julien Cristau <jcris...@mozilla.com>
wrote:

> Hi all,
>
> On March 1st, we will be merging Firefox 60 from mozilla-central to beta
> for the first time.  In order to avoid invalidating the testing we get out
> of nightly and the early Developer Edition builds and to ensure that we
> can roll out beta60 with confidence, we'd like to ask that any risky
> changes be avoided from March 1st until the version bump to 61 on March 12.
>
> Dos and Don'ts during the soft code freeze:
> Do:
>
>- Be ready to backout patches that cause crash spikes, new crashes,
>severe regressions
>
>
>- Monitor new regressions and escalate merge blockers
>
>
>- Support release management by prioritizing fixing of merge blockers
>
> Do Not:
>
>- Land a risky patch or a large patch
>
>
>- Land new features (that affects the current nightly version) — be
>mindful that code behind NIGHTLY_BUILD or RELEASE_OR_BETA ifdefs can lead
>to unexpected CI results
>
>
>- Flip prefs that enable new Features that were untested in Nightly
>cycle
>
>
>- Plan to kick off new experiments that might impact a feature's merge
>readiness
>
>
> Please let us know if you have any questions/concerns.
>
> Thanks,
> Release management team
>
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Soft code freeze for Firefox 60 starts March 1

2018-02-22 Thread Julien Cristau
Hi all,

On March 1st, we will be merging Firefox 60 from mozilla-central to beta
for the first time.  In order to avoid invalidating the testing we get out
of nightly and the early Developer Edition builds and to ensure that we can
roll out beta60 with confidence, we'd like to ask that any risky changes be
avoided from March 1st until the version bump to 61 on March 12.

Dos and Don'ts during the soft code freeze:
Do:

   - Be ready to backout patches that cause crash spikes, new crashes,
   severe regressions


   - Monitor new regressions and escalate merge blockers


   - Support release management by prioritizing fixing of merge blockers

Do Not:

   - Land a risky patch or a large patch


   - Land new features (that affects the current nightly version) — be
   mindful that code behind NIGHTLY_BUILD or RELEASE_OR_BETA ifdefs can lead
   to unexpected CI results


   - Flip prefs that enable new Features that were untested in Nightly cycle


   - Plan to kick off new experiments that might impact a feature's merge
   readiness


Please let us know if you have any questions/concerns.

Thanks,
Release management team
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform


Re: More Rust code

2017-07-11 Thread Julien Cristau
On Tue, Jul 11, 2017 at 3:04 AM, Chris Peterson 
wrote:

> On 7/10/17 4:48 PM, Xidorn Quan wrote:
>
>> The first thing comes to my mind is crash reports. It currently doesn't
>> always include useful panic message from Rust, see for example [1] and [2].
>> Also for Stylo, we generate lots of code (including using bindgen and mako
>> template system, bindgen is usually fine, but the code generated from
>> template can contain lots of code logic), and when the crash happens inside
>> generated code, it is pretty hard to understand what's going wrong, because
>> there is no useful source link, see for example [3].
>> There are also issues from Rust side. I've always been using an optimized
>> debug build locally (because that runs faster), and sometimes use Visual
>> Studio to investigate issues. C++ code works fine with this configuration,
>> but in Rust code, I cannot see any variable information. Stack backtrace
>> seems to work fine to me, though.
>> [1]https://crash-stats.mozilla.com/report/index/2abff06f-
>> d969-4ba5-845b-a98410170708[2]https://crash-stats.mozilla.
>> com/report/index/03718a9c-9d98-4832-b8a6-026220170706[3]
>> https://crash-stats.mozilla.com/report/index/6b7d1d78-
>> 8418-47ef-bee9-f49c20170710
>>
>
> Looking at those crash reports' signatures, we should probably add
> `core::option::expect_failed` and `core::str::slice_error_fail` to
> Socorro's list of function names to ignore [1]. Should Socorro ignore all
> Rust core::* or std::* function names when searching the backtrace for a
> useful signature?
>

I filed https://bugzilla.mozilla.org/show_bug.cgi?id=1379089 last week for
core::option::expect_failed.

Cheers,
Julien
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform