Quantcast

Changes to Mozilla’s release model: Aurora is going away, Nightly is the focus for localization

classic Classic list List threaded Threaded
27 messages Options
12
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Changes to Mozilla’s release model: Aurora is going away, Nightly is the focus for localization

Francesco Lodolo [:flod]
Hi localizers,
A significant change is going to happen to Mozilla’s release model, and
is going to happen quickly, in just a few days.

The Aurora branch will be discontinued on April 18 (next Tuesday).

In the original plan for Rapid Release Cycle, Aurora was supposed to
represent a first stabilization channel, with a userbase about 10 times
the size of Nightly’s, providing an additional cycle of user feedback.
It was also chosen as the branch to focus localization activity on,
since only string changes explicitly allowed could land, giving
localizers time to work on translation and testing before their work
reached a larger audience with Beta and Release.

With significant improvements in stability and performance in the
Nightly channel we have determined that we tend to gain more time by
testing and localizing in Nightly and stabilizing in Beta. The increased
speed to market and resulting quality and stability in the Beta channel
is why Aurora is going to be discontinued on April 18 (next merge day,
exceptionally on Tuesday).

On April 18, code for Firefox 54 is moving from Aurora to Beta as usual,
while Firefox 55 will remain on Nightly for a second cycle in a row (a
total of 14 weeks). On next merge day, June 12, Firefox 55 will move
directly from Nightly to Beta.

Between April and June, Firefox on desktop will continue to receive
updates for critical security issues and the Aurora and Developer
Edition populations will be migrated to the Beta update channel. On
Android, Aurora users will be migrated to Nightly.
More details will be available in the official FAQs that will be
published early next week.

*Impact on the localization process*
On April 18 (Monday evening, European time) we’ll disable all the Aurora
projects on both Pontoon and Pootle, in order to minimize the risk of
losing data. Starting from April 19, right after merge day, you’ll need
to focus your localization on Nightly (https://wiki.mozilla.org/Nightly)
instead of Aurora. We will work to ensure that localization tools will
be ready shortly after merge day.

This means that you will see more string changes, more frequently. To
avoid the risk of exposing poor strings to localizers, we plan to
publish new strings only once or twice a week. If you’re working
directly on Mercurial, or you’re interested in the technical details,
see the FAQs linked at the end of this email.

The original plan was to have cross-channel[1] available by the time
Project Dawn was in place, but the unexpected schedule acceleration
won’t make that possible. We expect to have it implemented by the time
Firefox 56 is available on the Nightly channel, and that will allow
localizers to work on one repository for both Nightly and Beta.

One other consequence is that all the testers you currently have on
Aurora will move to Beta around the end of the month. Pascal Chevrel,
who's been working on increasing Nightly's population in the past
months, has offered his help in building out a testing population on
Nightly. Among other things, we plan to run messages in about:home to
invite users of localized builds to install Nightly, but you should plan
to reach out to your community nonetheless.

 From April 19, all localizers should migrate to Nightly and start using
it for testing their work. We now have builds for all languages that
previously had Aurora builds.

You can download Firefox Nightly (for desktop) from here
https://www.mozilla.org/firefox/channel/desktop/#nightly

Firefox for Android Nightly (multilocale) is available here
https://www.mozilla.org/firefox/channel/android/#nightly

If this page is not available in your language, it means that
mozilla.org translation is behind and you should translate it as soon as
possible. Please check your webdashboard:
https://l10n.mozilla-community.org/webdashboard/

In the meantime, you can use this page to download your localized
Nightly build
https://www.mozilla.org/firefox/nightly/all/

We’ve started building a series of Frequently Asked Questions, the
document is available here:
https://github.com/mozilla-l10n/localizer-documentation/blob/master/misc/aurora_faqs.md 


It currently covers the same topics explained in this email, in some
cases with a bit more details.

It’s going to be a live, constantly evolving document: if you have any
questions, please ask here and we’ll update it as needed with relevant
information.

Francesco

[1]
https://blog.mozilla.org/l10n/2016/06/17/mozlondon-localization-sessions/
_______________________________________________
dev-l10n mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-l10n
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Changes to Mozilla’s release model: Aurora is going away, Nightly is the focus for localization

Francesco Lodolo [:flod]

> On April 18 (Monday evening, European time) we’ll disable all the
> Aurora projects on both Pontoon and Pootle
Correction: April 17 (still Monday evening, European time).




_______________________________________________
dev-l10n mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-l10n
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Changes to Mozilla’s release model: Aurora is going away, Nightly is the focus for localization

Michael Wolf-2
In reply to this post by Francesco Lodolo [:flod]
Francesco Lodolo [:flod] schrieb:
>
>> On April 18 (Monday evening, European time) we’ll disable all the
>> Aurora projects on both Pontoon and Pootle
> Correction: April 17 (still Monday evening, European time).
>

Ji Francesco,

a lot of text and all happens pretty suddenly. Aurora will be disabled
on Pontoon and Pootle? They all are Aurora! At least, until now.

Michael

_______________________________________________
dev-l10n mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-l10n
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Changes to Mozilla’s release model: Aurora is going away, Nightly is the focus for localization

Jeff Beatty
True, currently they are all Aurora. We will be moving the localization
process to Nightly until such a time as we can complete the work
surrounding cross-channel (one Firefox project, not channel-based Firefox
projects). The take away is that you may see new strings more often, but
you are expected to continue to localize at whatever pace/cadence you feel
most comfortable with.

Hope that helps,
Jeff

On Fri, Apr 14, 2017 at 10:18 AM, Michael Wolf <[hidden email]> wrote:

> Francesco Lodolo [:flod] schrieb:
>
>>
>> On April 18 (Monday evening, European time) we’ll disable all the Aurora
>>> projects on both Pontoon and Pootle
>>>
>> Correction: April 17 (still Monday evening, European time).
>>
>>
> Ji Francesco,
>
> a lot of text and all happens pretty suddenly. Aurora will be disabled on
> Pontoon and Pootle? They all are Aurora! At least, until now.
>
> Michael
>
>
> _______________________________________________
> dev-l10n mailing list
> [hidden email]
> https://lists.mozilla.org/listinfo/dev-l10n
>



--
Thanks,
Jeff
_______________________________________________
dev-l10n mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-l10n
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Changes to Mozilla’s release model: Aurora is going away, Nightly is the focus for localization

Michal Stanke-2
Hi Jeff.

I have been watching project Dawn for some time as well as the cross
channel l10n repository plan and I do not see anything bad about them.
But there are two things I wanted to clarify about the single repository
for both beta and nightly.

 1. What tools are we going to use to find out, which strings belong to
    beta and need to be done in the cycle?
 2. What about sign-offs in case we change a string, that is used in
    beta? Are we eventually dropping localizer sign-offs for beta too
    and you (l10n-drivers) will take care of them as in aurora today?


Cheers,
Michal Stanke

Dne 14.4.2017 v 18:24 Jeff Beatty napsal(a):

> True, currently they are all Aurora. We will be moving the localization
> process to Nightly until such a time as we can complete the work
> surrounding cross-channel (one Firefox project, not channel-based Firefox
> projects). The take away is that you may see new strings more often, but
> you are expected to continue to localize at whatever pace/cadence you feel
> most comfortable with.
>
> Hope that helps,
> Jeff
>
> On Fri, Apr 14, 2017 at 10:18 AM, Michael Wolf <[hidden email]> wrote:
>
>> Francesco Lodolo [:flod] schrieb:
>>
>>> On April 18 (Monday evening, European time) we’ll disable all the Aurora
>>>> projects on both Pontoon and Pootle
>>>>
>>> Correction: April 17 (still Monday evening, European time).
>>>
>>>
>> Ji Francesco,
>>
>> a lot of text and all happens pretty suddenly. Aurora will be disabled on
>> Pontoon and Pootle? They all are Aurora! At least, until now.
>>
>> Michael
>>
>>
>> _______________________________________________
>> dev-l10n mailing list
>> [hidden email]
>> https://lists.mozilla.org/listinfo/dev-l10n
>>
>
>

_______________________________________________
dev-l10n mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-l10n
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Changes to Mozilla’s release model: Aurora is going away, Nightly is the focus for localization

Jeff Beatty
Great questions! I'll do my best to answer and look to Pike to fill in
other gaps.

On Fri, Apr 14, 2017 at 10:46 AM, Michal Stanke <[hidden email]> wrote:

> Hi Jeff.
>
> I have been watching project Dawn for some time as well as the cross
> channel l10n repository plan and I do not see anything bad about them. But
> there are two things I wanted to clarify about the single repository for
> both beta and nightly.
>
> 1. What tools are we going to use to find out, which strings belong to
>    beta and need to be done in the cycle?
>
If you're using Pontoon or Pootle, all strings across branches will be in
one project. The repository will mark which strings belong to which version
and the tools will include that data.

As to what needs to be done within the cycle, one of the great things about
cross-channel is that there is less pressure on getting things done within
the cycle, since all strings across all branches will be in the same
repo/project.

> 2. What about sign-offs in case we change a string, that is used in
>    beta? Are we eventually dropping localizer sign-offs for beta too
>    and you (l10n-drivers) will take care of them as in aurora today?
>
Localizer sign-offs for all products have been dropped since June 2016.
We've taken over that process with the policy that we ship all good
updates, big or small, whenever they come in.

Thanks,
Jeff

>
>
> Cheers,
> Michal Stanke
>
> Dne 14.4.2017 v 18:24 Jeff Beatty napsal(a):
>
> True, currently they are all Aurora. We will be moving the localization
>> process to Nightly until such a time as we can complete the work
>> surrounding cross-channel (one Firefox project, not channel-based Firefox
>> projects). The take away is that you may see new strings more often, but
>> you are expected to continue to localize at whatever pace/cadence you feel
>> most comfortable with.
>>
>> Hope that helps,
>> Jeff
>>
>> On Fri, Apr 14, 2017 at 10:18 AM, Michael Wolf <[hidden email]>
>> wrote:
>>
>> Francesco Lodolo [:flod] schrieb:
>>>
>>> On April 18 (Monday evening, European time) we’ll disable all the Aurora
>>>>
>>>>> projects on both Pontoon and Pootle
>>>>>
>>>>> Correction: April 17 (still Monday evening, European time).
>>>>
>>>>
>>>> Ji Francesco,
>>>
>>> a lot of text and all happens pretty suddenly. Aurora will be disabled on
>>> Pontoon and Pootle? They all are Aurora! At least, until now.
>>>
>>> Michael
>>>
>>>
>>> _______________________________________________
>>> dev-l10n mailing list
>>> [hidden email]
>>> https://lists.mozilla.org/listinfo/dev-l10n
>>>
>>>
>>
>>
> _______________________________________________
> dev-l10n mailing list
> [hidden email]
> https://lists.mozilla.org/listinfo/dev-l10n
>



--
Thanks,
Jeff
_______________________________________________
dev-l10n mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-l10n
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Changes to Mozilla’s release model: Aurora is going away, Nightly is the focus for localization

Michal Stanke-2
I know we do not need to sign-off aurora ourselves (I have still done it a
few time, just for the feeling ;). And so you actually ship also updates
that happen in beta? I thought if we change anything in beta, we still need
to click the sign-off button ourselves today.

--
Michal Stanke

2017-04-14 18:52 GMT+02:00 Jeff Beatty <[hidden email]>:

> Great questions! I'll do my best to answer and look to Pike to fill in
> other gaps.
>
> On Fri, Apr 14, 2017 at 10:46 AM, Michal Stanke <[hidden email]>
> wrote:
>
>> Hi Jeff.
>>
>> I have been watching project Dawn for some time as well as the cross
>> channel l10n repository plan and I do not see anything bad about them. But
>> there are two things I wanted to clarify about the single repository for
>> both beta and nightly.
>>
>> 1. What tools are we going to use to find out, which strings belong to
>>    beta and need to be done in the cycle?
>>
> If you're using Pontoon or Pootle, all strings across branches will be in
> one project. The repository will mark which strings belong to which version
> and the tools will include that data.
>
> As to what needs to be done within the cycle, one of the great things
> about cross-channel is that there is less pressure on getting things done
> within the cycle, since all strings across all branches will be in the same
> repo/project.
>
>> 2. What about sign-offs in case we change a string, that is used in
>>    beta? Are we eventually dropping localizer sign-offs for beta too
>>    and you (l10n-drivers) will take care of them as in aurora today?
>>
> Localizer sign-offs for all products have been dropped since June 2016.
> We've taken over that process with the policy that we ship all good
> updates, big or small, whenever they come in.
>
> Thanks,
> Jeff
>
>>
>>
>> Cheers,
>> Michal Stanke
>>
>> Dne 14.4.2017 v 18:24 Jeff Beatty napsal(a):
>>
>> True, currently they are all Aurora. We will be moving the localization
>>> process to Nightly until such a time as we can complete the work
>>> surrounding cross-channel (one Firefox project, not channel-based Firefox
>>> projects). The take away is that you may see new strings more often, but
>>> you are expected to continue to localize at whatever pace/cadence you
>>> feel
>>> most comfortable with.
>>>
>>> Hope that helps,
>>> Jeff
>>>
>>> On Fri, Apr 14, 2017 at 10:18 AM, Michael Wolf <[hidden email]>
>>> wrote:
>>>
>>> Francesco Lodolo [:flod] schrieb:
>>>>
>>>> On April 18 (Monday evening, European time) we’ll disable all the Aurora
>>>>>
>>>>>> projects on both Pontoon and Pootle
>>>>>>
>>>>>> Correction: April 17 (still Monday evening, European time).
>>>>>
>>>>>
>>>>> Ji Francesco,
>>>>
>>>> a lot of text and all happens pretty suddenly. Aurora will be disabled
>>>> on
>>>> Pontoon and Pootle? They all are Aurora! At least, until now.
>>>>
>>>> Michael
>>>>
>>>>
>>>> _______________________________________________
>>>> dev-l10n mailing list
>>>> [hidden email]
>>>> https://lists.mozilla.org/listinfo/dev-l10n
>>>>
>>>>
>>>
>>>
>> _______________________________________________
>> dev-l10n mailing list
>> [hidden email]
>> https://lists.mozilla.org/listinfo/dev-l10n
>>
>
>
>
> --
> Thanks,
> Jeff
>
_______________________________________________
dev-l10n mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-l10n
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Changes to Mozilla’s release model: Aurora is going away, Nightly is the focus for localization

Jeff Beatty
We've taken on the whole sign-off process, Aurora & Beta :-)

On Fri, Apr 14, 2017 at 10:58 AM, Michal Stanke <[hidden email]> wrote:

> I know we do not need to sign-off aurora ourselves (I have still done it a
> few time, just for the feeling ;). And so you actually ship also updates
> that happen in beta? I thought if we change anything in beta, we still need
> to click the sign-off button ourselves today.
>
> --
> Michal Stanke
>
> 2017-04-14 18:52 GMT+02:00 Jeff Beatty <[hidden email]>:
>
>> Great questions! I'll do my best to answer and look to Pike to fill in
>> other gaps.
>>
>> On Fri, Apr 14, 2017 at 10:46 AM, Michal Stanke <[hidden email]>
>> wrote:
>>
>>> Hi Jeff.
>>>
>>> I have been watching project Dawn for some time as well as the cross
>>> channel l10n repository plan and I do not see anything bad about them. But
>>> there are two things I wanted to clarify about the single repository for
>>> both beta and nightly.
>>>
>>> 1. What tools are we going to use to find out, which strings belong to
>>>    beta and need to be done in the cycle?
>>>
>> If you're using Pontoon or Pootle, all strings across branches will be in
>> one project. The repository will mark which strings belong to which version
>> and the tools will include that data.
>>
>> As to what needs to be done within the cycle, one of the great things
>> about cross-channel is that there is less pressure on getting things done
>> within the cycle, since all strings across all branches will be in the same
>> repo/project.
>>
>>> 2. What about sign-offs in case we change a string, that is used in
>>>    beta? Are we eventually dropping localizer sign-offs for beta too
>>>    and you (l10n-drivers) will take care of them as in aurora today?
>>>
>> Localizer sign-offs for all products have been dropped since June 2016.
>> We've taken over that process with the policy that we ship all good
>> updates, big or small, whenever they come in.
>>
>> Thanks,
>> Jeff
>>
>>>
>>>
>>> Cheers,
>>> Michal Stanke
>>>
>>> Dne 14.4.2017 v 18:24 Jeff Beatty napsal(a):
>>>
>>> True, currently they are all Aurora. We will be moving the localization
>>>> process to Nightly until such a time as we can complete the work
>>>> surrounding cross-channel (one Firefox project, not channel-based
>>>> Firefox
>>>> projects). The take away is that you may see new strings more often, but
>>>> you are expected to continue to localize at whatever pace/cadence you
>>>> feel
>>>> most comfortable with.
>>>>
>>>> Hope that helps,
>>>> Jeff
>>>>
>>>> On Fri, Apr 14, 2017 at 10:18 AM, Michael Wolf <[hidden email]>
>>>> wrote:
>>>>
>>>> Francesco Lodolo [:flod] schrieb:
>>>>>
>>>>> On April 18 (Monday evening, European time) we’ll disable all the
>>>>>> Aurora
>>>>>>
>>>>>>> projects on both Pontoon and Pootle
>>>>>>>
>>>>>>> Correction: April 17 (still Monday evening, European time).
>>>>>>
>>>>>>
>>>>>> Ji Francesco,
>>>>>
>>>>> a lot of text and all happens pretty suddenly. Aurora will be disabled
>>>>> on
>>>>> Pontoon and Pootle? They all are Aurora! At least, until now.
>>>>>
>>>>> Michael
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> dev-l10n mailing list
>>>>> [hidden email]
>>>>> https://lists.mozilla.org/listinfo/dev-l10n
>>>>>
>>>>>
>>>>
>>>>
>>> _______________________________________________
>>> dev-l10n mailing list
>>> [hidden email]
>>> https://lists.mozilla.org/listinfo/dev-l10n
>>>
>>
>>
>>
>> --
>> Thanks,
>> Jeff
>>
>
>


--
Thanks,
Jeff
_______________________________________________
dev-l10n mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-l10n
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Changes to Mozilla’s release model: Aurora is going away, Nightly is the focus for localization

Marko Zeka Andrejic
In reply to this post by Francesco Lodolo [:flod]
Just to be sure, my community currently doesn't localize Nightly. After Aurora has been discounted, will Nightly automaticaly be enabled on our Pontoon with imported localization from Aurora or should we request for it?

Thanks in advance.

Marko Andrejić, Mozilla Serbia
_______________________________________________
dev-l10n mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-l10n
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Changes to Mozilla’s release model: Aurora is going away, Nightly is the focus for localization

Francesco Lodolo [:flod]
Hi,
After Tuesday all projects will be re-enabled and will be pointing to
Nightly, in both Pootle and Pontoon.

The work you've done on aurora until that point will be there, you'll
only see the strings for the new version of Firefox.

This will be done for all locales, no need to request anything.

Francesco



2017-04-14 21:43 GMT+02:00 Marko Zeka Andrejic <[hidden email]>:
> Just to be sure, my community currently doesn't localize Nightly. After Aurora has been discounted, will Nightly automaticaly be enabled on our Pontoon with imported localization from Aurora or should we request for it?
>
> Thanks in advance.
>
> Marko Andrejić, Mozilla Serbia
> _______________________________________________
> dev-l10n mailing list
> [hidden email]
> https://lists.mozilla.org/listinfo/dev-l10n
_______________________________________________
dev-l10n mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-l10n
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Changes to Mozilla’s release model: Aurora is going away, Nightly is the focus for localization

Kim Ludvigsen-2
In reply to this post by Francesco Lodolo [:flod]
Den 14-04-2017 kl. 16:48 skrev Francesco Lodolo [:flod]:
>
> This means that you will see more string changes, more frequently. To
> avoid the risk of exposing poor strings to localizers, we plan to
> publish new strings only once or twice a week.

How long before a deadline will there be a string freeze?

I will not translate several times in a cycle, and I do not like to have
to translate close to a deadline. I prefer to continue doing what I have
been doing for a long time in aurora; that is, taking the new strings
within the first week of a new cycle. Will it be possible to do that in
beta? If so, I will probably go to beta rather than go to nightly.

--
Kind regards
Kim Ludvigsen
_______________________________________________
dev-l10n mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-l10n
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Changes to Mozilla’s release model: Aurora is going away, Nightly is the focus for localization

maxxdroidusa
In reply to this post by Francesco Lodolo [:flod]
On Friday, April 14, 2017 at 7:48:51 AM UTC-7, Francesco Lodolo [:flod] wrote:

> Hi localizers,
> A significant change is going to happen to Mozilla’s release model, and
> is going to happen quickly, in just a few days.
>
> The Aurora branch will be discontinued on April 18 (next Tuesday).
>
> In the original plan for Rapid Release Cycle, Aurora was supposed to
> represent a first stabilization channel, with a userbase about 10 times
> the size of Nightly’s, providing an additional cycle of user feedback.
> It was also chosen as the branch to focus localization activity on,
> since only string changes explicitly allowed could land, giving
> localizers time to work on translation and testing before their work
> reached a larger audience with Beta and Release.
>
> With significant improvements in stability and performance in the
> Nightly channel we have determined that we tend to gain more time by
> testing and localizing in Nightly and stabilizing in Beta. The increased
> speed to market and resulting quality and stability in the Beta channel
> is why Aurora is going to be discontinued on April 18 (next merge day,
> exceptionally on Tuesday).
>
> On April 18, code for Firefox 54 is moving from Aurora to Beta as usual,
> while Firefox 55 will remain on Nightly for a second cycle in a row (a
> total of 14 weeks). On next merge day, June 12, Firefox 55 will move
> directly from Nightly to Beta.
>
> Between April and June, Firefox on desktop will continue to receive
> updates for critical security issues and the Aurora and Developer
> Edition populations will be migrated to the Beta update channel. On
> Android, Aurora users will be migrated to Nightly.
> More details will be available in the official FAQs that will be
> published early next week.
>
> *Impact on the localization process*
> On April 18 (Monday evening, European time) we’ll disable all the Aurora
> projects on both Pontoon and Pootle, in order to minimize the risk of
> losing data. Starting from April 19, right after merge day, you’ll need
> to focus your localization on Nightly (https://wiki.mozilla.org/Nightly)
> instead of Aurora. We will work to ensure that localization tools will
> be ready shortly after merge day.
>
> This means that you will see more string changes, more frequently. To
> avoid the risk of exposing poor strings to localizers, we plan to
> publish new strings only once or twice a week. If you’re working
> directly on Mercurial, or you’re interested in the technical details,
> see the FAQs linked at the end of this email.
>
> The original plan was to have cross-channel[1] available by the time
> Project Dawn was in place, but the unexpected schedule acceleration
> won’t make that possible. We expect to have it implemented by the time
> Firefox 56 is available on the Nightly channel, and that will allow
> localizers to work on one repository for both Nightly and Beta.
>
> One other consequence is that all the testers you currently have on
> Aurora will move to Beta around the end of the month. Pascal Chevrel,
> who's been working on increasing Nightly's population in the past
> months, has offered his help in building out a testing population on
> Nightly. Among other things, we plan to run messages in about:home to
> invite users of localized builds to install Nightly, but you should plan
> to reach out to your community nonetheless.
>
>  From April 19, all localizers should migrate to Nightly and start using
> it for testing their work. We now have builds for all languages that
> previously had Aurora builds.
>
> You can download Firefox Nightly (for desktop) from here
> https://www.mozilla.org/firefox/channel/desktop/#nightly
>
> Firefox for Android Nightly (multilocale) is available here
> https://www.mozilla.org/firefox/channel/android/#nightly
>
> If this page is not available in your language, it means that
> mozilla.org translation is behind and you should translate it as soon as
> possible. Please check your webdashboard:
> https://l10n.mozilla-community.org/webdashboard/
>
> In the meantime, you can use this page to download your localized
> Nightly build
> https://www.mozilla.org/firefox/nightly/all/
>
> We’ve started building a series of Frequently Asked Questions, the
> document is available here:
> https://github.com/mozilla-l10n/localizer-documentation/blob/master/misc/aurora_faqs.md 
>
>
> It currently covers the same topics explained in this email, in some
> cases with a bit more details.
>
> It’s going to be a live, constantly evolving document: if you have any
> questions, please ask here and we’ll update it as needed with relevant
> information.
>
> Francesco
>
> [1]
> https://blog.mozilla.org/l10n/2016/06/17/mozlondon-localization-sessions/

Will xpinstall.signatures.required & xpinstall.whitelist.required will be available in beta then?
As nightly is too unstable for some people and testing addons/themes etc in beta will be very useful.
_______________________________________________
dev-l10n mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-l10n
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Changes to Mozilla’s release model: Aurora is going away, Nightly is the focus for localization

maxxdroidusa
In reply to this post by Francesco Lodolo [:flod]
I'm curious how this will affect the addon plan for 57. Will Legacy and WebExt Experiments be allowed on Beta now that Aurora is pretty much merged into it? Or will Nightly be the only channel to allow them? which is not stable enough
As nightly is too unstable for some people and testing addons/themes etc in beta will be very useful.
WebExtension Experiments is what I was referring to. There is meant to be a pref to allow Legacy extensions in Nightly and (now formerly) in Aurora.
https://wiki.mozilla.org/Add-ons/Firefox57
Will xpinstall.signatures.required & xpinstall.whitelist.required will be available in beta then?
_______________________________________________
dev-l10n mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-l10n
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Changes to Mozilla’s release model: Aurora is going away, Nightly is the focus for localization

Francesco Lodolo [:flod]
Il 15/04/17 00.00, [hidden email] ha scritto:
> I'm curious how this will affect the addon plan for 57. Will Legacy and WebExt Experiments be allowed on Beta now that Aurora is pretty much merged into it? Or will Nightly be the only channel to allow them? which is not stable enough
> As nightly is too unstable for some people and testing addons/themes etc in beta will be very useful.
> WebExtension Experiments is what I was referring to. There is meant to be a pref to allow Legacy extensions in Nightly and (now formerly) in Aurora.
> https://wiki.mozilla.org/Add-ons/Firefox57
> Will xpinstall.signatures.required & xpinstall.whitelist.required will be available in beta then?
Hi,
These are valid questions and concerns, but please let's focus on the
localization impact of this change, since this the mailing list for
localizers.

There will be an official announcement on Monday, with FAQs, we got a
green light to send communication to localizers in advance because of
the drastic change in tools. Those topics will be covered in the
official FAQs.

Francesco
_______________________________________________
dev-l10n mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-l10n
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Changes to Mozilla’s release model: Aurora is going away, Nightly is the focus for localization

Francesco Lodolo [:flod]
In reply to this post by Kim Ludvigsen-2
Il 14/04/17 23.24, Kim Ludvigsen ha scritto:
> How long before a deadline will there be a string freeze?
>
> I will not translate several times in a cycle, and I do not like to
> have to translate close to a deadline. I prefer to continue doing what
> I have been doing for a long time in aurora; that is, taking the new
> strings within the first week of a new cycle. Will it be possible to
> do that in beta? If so, I will probably go to beta rather than go to
> nightly.
Hi Kim,
I think these two questions are relevant
https://github.com/mozilla-l10n/localizer-documentation/blob/master/misc/aurora_faqs.md#q-how-often-will-i-have-new-strings-to-localize

There won't be a string freeze on Nightly, when strings move to Beta
you're going to only have about 4 weeks for translating and testing
before the sign-off deadline.

If you work on Mercurial and decide to translate on Beta, you will also
need to manually port changes to l10n-central (on next merge day, the
content of l10n-central will be moved to mozilla-beta, overwriting the
existing content). If you work on Pontoon, you will need to manually
commit these changes to the Nightly project to avoid losing them.

Things will improve with cross-channel, since you need to commit only to
one repository for all versions. Unfortunately, the next cycle is going
to be a transition phase in that sense, because of the last minute
schedule change.

We are aware that this is going to be a big change for some teams, but
it could also become a chance to involve new contributors (there will be
small batches of strings available every week). It might also be an
occasion to evaluate workflows and tools that have been used efficiently
so far, but don't adapt and scale as well to this new scenario.

Francesco
_______________________________________________
dev-l10n mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-l10n
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Changes to Mozilla’s release model: Aurora is going away, Nightly is the focus for localization

Kim Ludvigsen-2
In reply to this post by Kim Ludvigsen-2
Den 15-04-2017 kl. 07:05 skrev Francesco Lodolo [:flod]:
>
> If you work on Mercurial and decide to translate on Beta, you will also
> need to manually port changes to l10n-central (on next merge day, the
> content of l10n-central will be moved to mozilla-beta, overwriting the
> existing content).

How do I do that?

> We are aware that this is going to be a big change for some teams, but it could
 > also become a chance to involve new contributors (there will be small
batches of
> strings available every week)

It could also mean a big chance to lose old contributors; just as the
change of SUMO did.

--
Kind regards
Kim Ludvigsen
_______________________________________________
dev-l10n mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-l10n
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Changes to Mozilla’s release model: Aurora is going away, Nightly is the focus for localization

Francesco Lodolo [:flod]
Il 15/04/17 07.55, Kim Ludvigsen ha scritto:
> Den 15-04-2017 kl. 07:05 skrev Francesco Lodolo [:flod]:
>>
>> If you work on Mercurial and decide to translate on Beta, you will also
>> need to manually port changes to l10n-central (on next merge day, the
>> content of l10n-central will be moved to mozilla-beta, overwriting the
>> existing content).
>
> How do I do that?
If you decide to work on beta next cycle, please ping me directly and
we'll figure out the best way to do it. Changesets should be pulled from
mozilla-beta to l10n-central and merged.

Note that it's not different from localizing now on mozilla-beta with
Mercurial, you need to port your changes into mozilla-aurora on your own
to avoid losing them on merge day.

>
>> We are aware that this is going to be a big change for some teams,
>> but it could
> > also become a chance to involve new contributors (there will be
> small batches of
>> strings available every week)
>
> It could also mean a big chance to lose old contributors; just as the
> change of SUMO did.
We clearly hope that's not the case, even if we understand this change
is going to be harder on some teams than others, especially those not
working on tools like Pootle or Pontoon.

We're here to help as best as we can in this transition.

Francesco





_______________________________________________
dev-l10n mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-l10n
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Changes to Mozilla’s release model: Aurora is going away, Nightly is the focus for localization

Fjoerfoks
Hi,
Some of these questions were als answered by Axel in the last bi-weekly
call thithursday.You can view it here:
https://air.mozilla.org/localization-community-bi-monthly-call-2017-04-13/
Not all new strings will be exposed directly to localizers, there will be
some sort of quarantaine.

Wim

Op 15 apr. 2017 8:19 AM schreef "Francesco Lodolo [:flod]" <[hidden email]
>:

> Il 15/04/17 07.55, Kim Ludvigsen ha scritto:
>
>> Den 15-04-2017 kl. 07:05 skrev Francesco Lodolo [:flod]:
>>
>>>
>>> If you work on Mercurial and decide to translate on Beta, you will also
>>> need to manually port changes to l10n-central (on next merge day, the
>>> content of l10n-central will be moved to mozilla-beta, overwriting the
>>> existing content).
>>>
>>
>> How do I do that?
>>
> If you decide to work on beta next cycle, please ping me directly and
> we'll figure out the best way to do it. Changesets should be pulled from
> mozilla-beta to l10n-central and merged.
>
> Note that it's not different from localizing now on mozilla-beta with
> Mercurial, you need to port your changes into mozilla-aurora on your own to
> avoid losing them on merge day.
>
>
>> We are aware that this is going to be a big change for some teams, but it
>>> could
>>>
>> > also become a chance to involve new contributors (there will be small
>> batches of
>>
>>> strings available every week)
>>>
>>
>> It could also mean a big chance to lose old contributors; just as the
>> change of SUMO did.
>>
> We clearly hope that's not the case, even if we understand this change is
> going to be harder on some teams than others, especially those not working
> on tools like Pootle or Pontoon.
>
> We're here to help as best as we can in this transition.
>
> Francesco
>
>
>
>
>
> _______________________________________________
> dev-l10n mailing list
> [hidden email]
> https://lists.mozilla.org/listinfo/dev-l10n
>
_______________________________________________
dev-l10n mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-l10n
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Changes to Mozilla’s release model: Aurora is going away, Nightly is the focus for localization

Francesco Lodolo [:flod]
Il 15/04/17 10.23, Fjoerfoks ha scritto:
> Not all new strings will be exposed directly to localizers, there will
> be some sort of quarantaine.
Thanks Wim, if someone is interested there are also meeting notes for
last call (thanks Théo for taking them)
https://public.etherpad-mozilla.org/p/l10n-community-13-04-2017

If anybody is interested in the details, they're available here
https://github.com/mozilla-l10n/localizer-documentation/blob/master/misc/aurora_faqs.md#q-i-work-directly-on-mercurial-is-something-going-to-change-for-me

Francesco
_______________________________________________
dev-l10n mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-l10n
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Changes to Mozilla’s release model: Aurora is going away, Nightly is the focus for localization

Axel Hecht
In reply to this post by Kim Ludvigsen-2
Am 14.04.17 um 23:24 schrieb Kim Ludvigsen:

> Den 14-04-2017 kl. 16:48 skrev Francesco Lodolo [:flod]:
>>
>> This means that you will see more string changes, more frequently. To
>> avoid the risk of exposing poor strings to localizers, we plan to
>> publish new strings only once or twice a week.
>
> How long before a deadline will there be a string freeze?
>
> I will not translate several times in a cycle, and I do not like to have
> to translate close to a deadline. I prefer to continue doing what I have
> been doing for a long time in aurora; that is, taking the new strings
> within the first week of a new cycle. Will it be possible to do that in
> beta? If so, I will probably go to beta rather than go to nightly.
>

This is a reply for more folks than just Kim. We've heard similar
stories in the workshops of the past year or two, so I'd like to give a
more general perspective...

Truth be told, I expect that Firefox will become a suite of localizable
features shipping on different schedules. Test pilot and other system
addons are just the start, and we'll have more of that. I don't think
that we'll be able to tell you N weeks in advance if you've fully
translated Firefox 60.

What we can do is trying to make that as seamless as possible, but we
can't keep mozilla from shipping things as part of Firefox that just had
2-3 weeks of exposure to localization.

We'll expose strings in a more continuous fashion, frequently and
incrementally, to localizers. At the same time, we're trying to get
fixes from localizers out to end-users in a timely fashion. The idea is
to reward improvements to a localization with actually shipping it to users.

What we're trying to achieve is to also take away the pressure of
timelines and calendars, and make localization of Firefox more fun
again. For most of our community members, this will actually work out
this way, while for some it might not be the best fit. I'm saying "most
of our community members" because we did talk to many of you over the
past year about patterns of localization and contribution, and for many
the rapid release cycle didn't work out great. It took away the hobby of
translating Firefox for 5 weeks out of 6, and that's just awful.

At the same time, the rapid release cycle doesn't work well for those of
you that are driven by the sense of achievement, or that want to dive
deep into translation for a period of time. We just didn't offer the
achievement of localizing Firefox 4, and then have celebrate that
release, whether it's press or websites or parties or just a cup of tea
on Sunday afternoon. We just don't expose a meaningful bucket of 1000
words to dive into over a weekend. If you're in this group, I invite you
to reach out to us, and see if we can find ways to substitute these
motivation factors with.

To close with a suggestion. Set a release cycle for yourself. Release
something to yourself, and to your community every two or three weeks.
Build out ways to create an achievement on those. If it's the cup of tea
on Sunday afternoon or some community post or whatever works for you.
The idea here is this: The release cadence that you can ignore the
easiest is the 6-8 weeks where we bump the major version number. If your
heart ticks on that beat, you'll be hurt, but if it beats more
frequently, you won't be hurt, and hopefully you can give that frequency
purpose. And with x-channel, finding that purpose will be at least
possible, which is frankly impossible with the current way of localizing
the rapid release process.

There's an opportunity to find a new compromise between yourself and the
way we ship Firefox.

In closing, this is a response addressing concerns we heard from a few
of you, and I hope that Kim can make something useful out of this, too.

Hope that helps

Axel
_______________________________________________
dev-l10n mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-l10n
12
Loading...