Intent to require Python 3 to build Firefox 59 and later

classic Classic list List threaded Threaded
14 messages Options
Reply | Threaded
Open this post in threaded view
|

Intent to require Python 3 to build Firefox 59 and later

Gregory Szorc-3
For reasons outlined at https://bugzilla.mozilla.org/show_bug.cgi?id=1388447#c7, we would like to make Python 3 a requirement to build Firefox sometime in the Firefox 59 development cycle. (Firefox 59 will be an ESR release.)

The requirement will likely be Python 3.5+. Although I would love to make that 3.6 if possible so we can fully harness modern features and performance.

I would love to hear feedback - positive or negative - from downstream packagers and users of various operating systems and distributions about this proposal.

Please send comments to [hidden email] or leave them on bug 1388447.

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

Re: Intent to require Python 3 to build Firefox 59 and later

Adam Moore
The current Ubuntu LTS release has 3.5.2, I wouldn't try to force 3.6.

On Fri, Nov 10, 2017 at 3:46 PM, Adam Moore <[hidden email]> wrote:
The current Ubuntu LTS release has 3.5.2, I wouldn't try to force 3.6.

On Fri, Nov 10, 2017 at 3:27 PM, Gregory Szorc <[hidden email]> wrote:
For reasons outlined at
https://bugzilla.mozilla.org/show_bug.cgi?id=1388447#c7, we would like to
make Python 3 a requirement to build Firefox sometime in the Firefox 59
development cycle. (Firefox 59 will be an ESR release.)

The requirement will likely be Python 3.5+. Although I would love to make
that 3.6 if possible so we can fully harness modern features and
performance.

I would love to hear feedback - positive or negative - from downstream
packagers and users of various operating systems and distributions about
this proposal.

Please send comments to [hidden email] or leave them on bug
1388447.
_______________________________________________
dev-platform mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-platform



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

Re: Intent to require Python 3 to build Firefox 59 and later

David Burns-9
In reply to this post by Gregory Szorc-3
My only concern about this is how local developer environments are going to be when it comes to testing. While I am sympathetic to moving to python 3 we need to make sure that all the test harnesses have been moved over and this is something that needs a bit of coordination. Luckily a lot of the mozbase stuff is already moving to python 3 support but that still means we need to have web servers and the actual test runners moved over too.

David



On 10 November 2017 at 23:27, Gregory Szorc <[hidden email]> wrote:
For reasons outlined at https://bugzilla.mozilla.org/show_bug.cgi?id=1388447#c7, we would like to make Python 3 a requirement to build Firefox sometime in the Firefox 59 development cycle. (Firefox 59 will be an ESR release.)

The requirement will likely be Python 3.5+. Although I would love to make that 3.6 if possible so we can fully harness modern features and performance.

I would love to hear feedback - positive or negative - from downstream packagers and users of various operating systems and distributions about this proposal.

Please send comments to [hidden email] or leave them on bug 1388447.

_______________________________________________
dev-builds mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-builds



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

Re: Intent to require Python 3 to build Firefox 59 and later

Andreas Tolfsen-2
In reply to this post by Gregory Szorc-3
Also sprach Gregory Szorc:

> The requirement will likely be Python 3.5+. Although I would
> love to make that 3.6 if possible so we can fully harness modern
> features and performance.

Hold your horses with 3.6.  Only Python 3.5.3 is at the time of
writing available in the most common Linux distributions.  I
wouldn’t discount that 3.6 will be generally available in the
short- to medium term.
_______________________________________________
dev-builds mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-builds
Reply | Threaded
Open this post in threaded view
|

Re: Intent to require Python 3 to build Firefox 59 and later

Andrew Halberstadt
In reply to this post by David Burns-9
On Fri, Nov 10, 2017 at 9:44 PM David Burns <[hidden email]> wrote:
My only concern about this is how local developer environments are going to be when it comes to testing. While I am sympathetic to moving to python 3 we need to make sure that all the test harnesses have been moved over and this is something that needs a bit of coordination. Luckily a lot of the mozbase stuff is already moving to python 3 support but that still means we need to have web servers and the actual test runners moved over too.

David

For libraries like mozbase, I think the plan will be to support both 2 and 3 at
the same time. There are libraries (like 'six') that make this possible. I'd bet
there are even parts of the build system that will still need to support both at
the same time.

With that in mind, I don't think python 3 support for test harnesses needs to
block the build system.

Andrew

On 10 November 2017 at 23:27, Gregory Szorc <[hidden email]> wrote:
For reasons outlined at https://bugzilla.mozilla.org/show_bug.cgi?id=1388447#c7, we would like to make Python 3 a requirement to build Firefox sometime in the Firefox 59 development cycle. (Firefox 59 will be an ESR release.)

The requirement will likely be Python 3.5+. Although I would love to make that 3.6 if possible so we can fully harness modern features and performance.

I would love to hear feedback - positive or negative - from downstream packagers and users of various operating systems and distributions about this proposal.

Please send comments to [hidden email] or leave them on bug 1388447.

_______________________________________________
dev-builds mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-builds

_______________________________________________
dev-builds mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-builds

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

Re: Intent to require Python 3 to build Firefox 59 and later

David Burns-9
I am not saying it should but if we have a requirement for python 3, we are also going to have a requirement for py2 to both be available for local development.

David

On 11 November 2017 at 14:10, Andrew Halberstadt <[hidden email]> wrote:
On Fri, Nov 10, 2017 at 9:44 PM David Burns <[hidden email]> wrote:
My only concern about this is how local developer environments are going to be when it comes to testing. While I am sympathetic to moving to python 3 we need to make sure that all the test harnesses have been moved over and this is something that needs a bit of coordination. Luckily a lot of the mozbase stuff is already moving to python 3 support but that still means we need to have web servers and the actual test runners moved over too.

David

For libraries like mozbase, I think the plan will be to support both 2 and 3 at
the same time. There are libraries (like 'six') that make this possible. I'd bet
there are even parts of the build system that will still need to support both at
the same time.

With that in mind, I don't think python 3 support for test harnesses needs to
block the build system.

Andrew

On 10 November 2017 at 23:27, Gregory Szorc <[hidden email]> wrote:
For reasons outlined at https://bugzilla.mozilla.org/show_bug.cgi?id=1388447#c7, we would like to make Python 3 a requirement to build Firefox sometime in the Firefox 59 development cycle. (Firefox 59 will be an ESR release.)

The requirement will likely be Python 3.5+. Although I would love to make that 3.6 if possible so we can fully harness modern features and performance.

I would love to hear feedback - positive or negative - from downstream packagers and users of various operating systems and distributions about this proposal.

Please send comments to [hidden email] or leave them on bug 1388447.

_______________________________________________
dev-builds mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-builds

_______________________________________________
dev-builds mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-builds


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

Re: Intent to require Python 3 to build Firefox 59 and later

Ted Mielczarek-2
On Sun, Nov 12, 2017, at 12:12 PM, David Burns wrote:
I am not saying it should but if we have a requirement for python 3, we are also going to have a requirement for py2 to both be available for local development.

Correct, and as far as I know that's the plan of record. As Greg said, we're not going to convert all the code in the tree to run under Python 3 immediately, and we will likely have some laggards that stay on Python 2 for a while. We do have folks working on making the in-tree Python code Python 3 compatible (thanks ahal for leading that effort!), so hopefully we could get to a point where Python 3 is used for most things but it's a fair amount of work.

We'd simply like to have Python 3 available for some code that would benefit from its faster execution speed and things like asyncio. Greg floated the idea of doing moz.build evaluation in Python 3 last week, which seems like a great candidate.

-Ted


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

Re: Intent to require Python 3 to build Firefox 59 and later

Gregory Szorc-3
On Mon, Nov 13, 2017 at 5:22 AM, Ted Mielczarek <[hidden email]> wrote:
On Sun, Nov 12, 2017, at 12:12 PM, David Burns wrote:
I am not saying it should but if we have a requirement for python 3, we are also going to have a requirement for py2 to both be available for local development.

Correct, and as far as I know that's the plan of record. As Greg said, we're not going to convert all the code in the tree to run under Python 3 immediately, and we will likely have some laggards that stay on Python 2 for a while. We do have folks working on making the in-tree Python code Python 3 compatible (thanks ahal for leading that effort!), so hopefully we could get to a point where Python 3 is used for most things but it's a fair amount of work.

We'd simply like to have Python 3 available for some code that would benefit from its faster execution speed and things like asyncio. Greg floated the idea of doing moz.build evaluation in Python 3 last week, which seems like a great candidate.

Yes, the plan is to require Python 2.7 *and* Python 3 for an indeterminate amount of time. There's absolutely no way we can do a flag day conversion of all the Python in the repo. Unless we make porting an organizational priority (which I don't foresee happening because there is little to gain from touching code not under active development), porting will take years and will likely extend beyond 2020.

What we can do is enable people to write new code targeting Python 3 and port existing code that would benefit from Python 3. That's my main goal for establishing this requirement.

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

Re: Intent to require Python 3 to build Firefox 59 and later

Dustin Mitchell
There will come a point very soon when working on Python 2 code is
about as attractive as working on Perl (sorry, Perl afficionados!).

So this effort will get us to the point where heavily-developed things
run in Python 3, less-heavily-develped stuff is at least "ready to
port" (ensured via various source-code analysis tools), and there's a
long tail of stuff still running in Python 2 that is unlikely to be
touched anyway.

Dustin

2017-11-13 13:21 GMT-05:00 Gregory Szorc <[hidden email]>:

> On Mon, Nov 13, 2017 at 5:22 AM, Ted Mielczarek <[hidden email]> wrote:
>>
>> On Sun, Nov 12, 2017, at 12:12 PM, David Burns wrote:
>>
>> I am not saying it should but if we have a requirement for python 3, we
>> are also going to have a requirement for py2 to both be available for local
>> development.
>>
>>
>> Correct, and as far as I know that's the plan of record. As Greg said,
>> we're not going to convert all the code in the tree to run under Python 3
>> immediately, and we will likely have some laggards that stay on Python 2 for
>> a while. We do have folks working on making the in-tree Python code Python 3
>> compatible (thanks ahal for leading that effort!), so hopefully we could get
>> to a point where Python 3 is used for most things but it's a fair amount of
>> work.
>>
>> We'd simply like to have Python 3 available for some code that would
>> benefit from its faster execution speed and things like asyncio. Greg
>> floated the idea of doing moz.build evaluation in Python 3 last week, which
>> seems like a great candidate.
>
>
> Yes, the plan is to require Python 2.7 *and* Python 3 for an indeterminate
> amount of time. There's absolutely no way we can do a flag day conversion of
> all the Python in the repo. Unless we make porting an organizational
> priority (which I don't foresee happening because there is little to gain
> from touching code not under active development), porting will take years
> and will likely extend beyond 2020.
>
> What we can do is enable people to write new code targeting Python 3 and
> port existing code that would benefit from Python 3. That's my main goal for
> establishing this requirement.
>
> _______________________________________________
> dev-builds mailing list
> [hidden email]
> https://lists.mozilla.org/listinfo/dev-builds
>
_______________________________________________
dev-builds mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-builds
Reply | Threaded
Open this post in threaded view
|

Re: Intent to require Python 3 to build Firefox 59 and later

Jeff Gilbert-2
In reply to this post by David Burns-9
As long as we follow PEP 394, I'm super excited. (including on our
mozilla-build windows system, which counts as 'unix-like')

On Sun, Nov 12, 2017 at 9:12 AM, David Burns <[hidden email]> wrote:

> I am not saying it should but if we have a requirement for python 3, we are
> also going to have a requirement for py2 to both be available for local
> development.
>
> David
>
> On 11 November 2017 at 14:10, Andrew Halberstadt <[hidden email]>
> wrote:
>
>> On Fri, Nov 10, 2017 at 9:44 PM David Burns <[hidden email]> wrote:
>>
>>> My only concern about this is how local developer environments are going
>>> to be when it comes to testing. While I am sympathetic to moving to python
>>> 3 we need to make sure that all the test harnesses have been moved over and
>>> this is something that needs a bit of coordination. Luckily a lot of the
>>> mozbase stuff is already moving to python 3 support but that still means we
>>> need to have web servers and the actual test runners moved over too.
>>>
>>> David
>>>
>>
>> For libraries like mozbase, I think the plan will be to support both 2 and
>> 3 at
>> the same time. There are libraries (like 'six') that make this possible.
>> I'd bet
>> there are even parts of the build system that will still need to support
>> both at
>> the same time.
>>
>> With that in mind, I don't think python 3 support for test harnesses needs
>> to
>> block the build system.
>>
>> Andrew
>>
>> On 10 November 2017 at 23:27, Gregory Szorc <[hidden email]> wrote:
>>>
>>>> For reasons outlined at https://bugzilla.mozilla.org/
>>>> show_bug.cgi?id=1388447#c7, we would like to make Python 3 a
>>>> requirement to build Firefox sometime in the Firefox 59 development cycle.
>>>> (Firefox 59 will be an ESR release.)
>>>>
>>>> The requirement will likely be Python 3.5+. Although I would love to
>>>> make that 3.6 if possible so we can fully harness modern features and
>>>> performance.
>>>>
>>>> I would love to hear feedback - positive or negative - from downstream
>>>> packagers and users of various operating systems and distributions about
>>>> this proposal.
>>>>
>>>> Please send comments to [hidden email] or leave them on
>>>> bug 1388447.
>>>>
>>>> _______________________________________________
>>>> dev-builds mailing list
>>>> [hidden email]
>>>> https://lists.mozilla.org/listinfo/dev-builds
>>>>
>>>> _______________________________________________
>>> dev-builds mailing list
>>> [hidden email]
>>> https://lists.mozilla.org/listinfo/dev-builds
>>>
>>
> _______________________________________________
> dev-platform mailing list
> [hidden email]
> https://lists.mozilla.org/listinfo/dev-platform
_______________________________________________
dev-builds mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-builds
Reply | Threaded
Open this post in threaded view
|

Re: Intent to require Python 3 to build Firefox 59 and later

AllassoPraise
In reply to this post by Dustin Mitchell
I have python2.7, python3.5, and python (which links to 2.7) on my
linux machine.  Will mach build sort this out and know which version
to use for what?

Also, on OS X I  only have 2.7, so I assume I'll have to install 3.x
using port.  What variable do I need to set in my mozconfig to tell
mach build where to find 3.x?  eg, PY3=/opt/local/bin/python3.5 or
something like that?



On 11/13/17, Dustin Mitchell <[hidden email]> wrote:

> There will come a point very soon when working on Python 2 code is
> about as attractive as working on Perl (sorry, Perl afficionados!).
>
> So this effort will get us to the point where heavily-developed things
> run in Python 3, less-heavily-develped stuff is at least "ready to
> port" (ensured via various source-code analysis tools), and there's a
> long tail of stuff still running in Python 2 that is unlikely to be
> touched anyway.
>
> Dustin
>
> 2017-11-13 13:21 GMT-05:00 Gregory Szorc <[hidden email]>:
>> On Mon, Nov 13, 2017 at 5:22 AM, Ted Mielczarek <[hidden email]>
>> wrote:
>>>
>>> On Sun, Nov 12, 2017, at 12:12 PM, David Burns wrote:
>>>
>>> I am not saying it should but if we have a requirement for python 3, we
>>> are also going to have a requirement for py2 to both be available for
>>> local
>>> development.
>>>
>>>
>>> Correct, and as far as I know that's the plan of record. As Greg said,
>>> we're not going to convert all the code in the tree to run under Python
>>> 3
>>> immediately, and we will likely have some laggards that stay on Python 2
>>> for
>>> a while. We do have folks working on making the in-tree Python code
>>> Python 3
>>> compatible (thanks ahal for leading that effort!), so hopefully we could
>>> get
>>> to a point where Python 3 is used for most things but it's a fair amount
>>> of
>>> work.
>>>
>>> We'd simply like to have Python 3 available for some code that would
>>> benefit from its faster execution speed and things like asyncio. Greg
>>> floated the idea of doing moz.build evaluation in Python 3 last week,
>>> which
>>> seems like a great candidate.
>>
>>
>> Yes, the plan is to require Python 2.7 *and* Python 3 for an
>> indeterminate
>> amount of time. There's absolutely no way we can do a flag day conversion
>> of
>> all the Python in the repo. Unless we make porting an organizational
>> priority (which I don't foresee happening because there is little to gain
>> from touching code not under active development), porting will take years
>> and will likely extend beyond 2020.
>>
>> What we can do is enable people to write new code targeting Python 3 and
>> port existing code that would benefit from Python 3. That's my main goal
>> for
>> establishing this requirement.
>>
>> _______________________________________________
>> dev-builds mailing list
>> [hidden email]
>> https://lists.mozilla.org/listinfo/dev-builds
>>
> _______________________________________________
> dev-builds mailing list
> [hidden email]
> https://lists.mozilla.org/listinfo/dev-builds
>
_______________________________________________
dev-builds mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-builds
Reply | Threaded
Open this post in threaded view
|

Re: Intent to require Python 3 to build Firefox 59 and later

Gregory Szorc-3
In reply to this post by Gregory Szorc-3
On Mon, Nov 13, 2017 at 5:22 PM, Kevin Jones <[hidden email]> wrote:
I have python2.7, python3.5, and python (which links to 2.7) on my linux machine.  Will mach build sort this out and know which version to use for what?

That is the recommend binary naming convention for Python binaries. The build system will (and currently does) sort this out. There may be a few random scripts that don't do things correctly. But `mach` and `configure` should do the right thing. If they don't, it is a bug.
 

Also, on OS X I  only have 2.7, so I assume I'll have to install 3.x using port.  What variable do I need to set in my mozconfig to tell mach build where to find 3.x?  eg, PY3=/opt/local/bin/python3.5 or something like that?

The build system is smart enough to look in PATH to find an appropriate Python 3 binary. If you want to point configure to an explicit binary, use the PYTHON3 environment variable. From a mozconfig:

  ac_add_options PYTHON3=/opt/local/bin/python3.6

Configure's output will print the path and version of any discovered Python 3.5+ binary. You can also look for PYTHON3 in objdir/config.status.

 

On Mon, Nov 13, 2017 at 11:21 AM, Gregory Szorc <[hidden email]> wrote:
On Mon, Nov 13, 2017 at 5:22 AM, Ted Mielczarek <[hidden email]> wrote:
On Sun, Nov 12, 2017, at 12:12 PM, David Burns wrote:
I am not saying it should but if we have a requirement for python 3, we are also going to have a requirement for py2 to both be available for local development.

Correct, and as far as I know that's the plan of record. As Greg said, we're not going to convert all the code in the tree to run under Python 3 immediately, and we will likely have some laggards that stay on Python 2 for a while. We do have folks working on making the in-tree Python code Python 3 compatible (thanks ahal for leading that effort!), so hopefully we could get to a point where Python 3 is used for most things but it's a fair amount of work.

We'd simply like to have Python 3 available for some code that would benefit from its faster execution speed and things like asyncio. Greg floated the idea of doing moz.build evaluation in Python 3 last week, which seems like a great candidate.

Yes, the plan is to require Python 2.7 *and* Python 3 for an indeterminate amount of time. There's absolutely no way we can do a flag day conversion of all the Python in the repo. Unless we make porting an organizational priority (which I don't foresee happening because there is little to gain from touching code not under active development), porting will take years and will likely extend beyond 2020.

What we can do is enable people to write new code targeting Python 3 and port existing code that would benefit from Python 3. That's my main goal for establishing this requirement.

_______________________________________________
dev-builds mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-builds




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

Re: Intent to require Python 3 to build Firefox 59 and later

AllassoPraise
Hello,

When trying to do non-archive build on Linux I get error:

29:57.52    Compiling style v0.0.1
(file:///home/allasso/mozilla-central/mozilla-central_3/servo/components/style)
29:57.52 error[E0106]: missing lifetime specifier

This is after successfully running mach bootstrap.

Here is my config and complete error:

https://pastebin.com/fb9ahjA2

Any suggestions?

Thanks,
Kevin
_______________________________________________
dev-builds mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-builds
Reply | Threaded
Open this post in threaded view
|

Re: Intent to require Python 3 to build Firefox 59 and later

Rok Garbas
In reply to this post by Jeff Gilbert-2
It would make my heart sing if all python 3 code we write would have defined types (using mypy in in ./mach lint). It would definitely remove the feeling of "walking blindfolded" when doing any change with the python tooling. At least I hope providing types would be allowed if not required.

-- Rok




On Tue, Nov 14, 2017 at 12:31 AM Jeff Gilbert <[hidden email]> wrote:
As long as we follow PEP 394, I'm super excited. (including on our
mozilla-build windows system, which counts as 'unix-like')

On Sun, Nov 12, 2017 at 9:12 AM, David Burns <[hidden email]> wrote:
> I am not saying it should but if we have a requirement for python 3, we are
> also going to have a requirement for py2 to both be available for local
> development.
>
> David
>
> On 11 November 2017 at 14:10, Andrew Halberstadt <[hidden email]>
> wrote:
>
>> On Fri, Nov 10, 2017 at 9:44 PM David Burns <[hidden email]> wrote:
>>
>>> My only concern about this is how local developer environments are going
>>> to be when it comes to testing. While I am sympathetic to moving to python
>>> 3 we need to make sure that all the test harnesses have been moved over and
>>> this is something that needs a bit of coordination. Luckily a lot of the
>>> mozbase stuff is already moving to python 3 support but that still means we
>>> need to have web servers and the actual test runners moved over too.
>>>
>>> David
>>>
>>
>> For libraries like mozbase, I think the plan will be to support both 2 and
>> 3 at
>> the same time. There are libraries (like 'six') that make this possible.
>> I'd bet
>> there are even parts of the build system that will still need to support
>> both at
>> the same time.
>>
>> With that in mind, I don't think python 3 support for test harnesses needs
>> to
>> block the build system.
>>
>> Andrew
>>
>> On 10 November 2017 at 23:27, Gregory Szorc <[hidden email]> wrote:
>>>
>>>> For reasons outlined at https://bugzilla.mozilla.org/
>>>> show_bug.cgi?id=1388447#c7, we would like to make Python 3 a
>>>> requirement to build Firefox sometime in the Firefox 59 development cycle.
>>>> (Firefox 59 will be an ESR release.)
>>>>
>>>> The requirement will likely be Python 3.5+. Although I would love to
>>>> make that 3.6 if possible so we can fully harness modern features and
>>>> performance.
>>>>
>>>> I would love to hear feedback - positive or negative - from downstream
>>>> packagers and users of various operating systems and distributions about
>>>> this proposal.
>>>>
>>>> Please send comments to [hidden email] or leave them on
>>>> bug 1388447.
>>>>
>>>> _______________________________________________
>>>> dev-builds mailing list
>>>> [hidden email]
>>>> https://lists.mozilla.org/listinfo/dev-builds
>>>>
>>>> _______________________________________________
>>> dev-builds mailing list
>>> [hidden email]
>>> https://lists.mozilla.org/listinfo/dev-builds
>>>
>>
> _______________________________________________
> dev-platform mailing list
> [hidden email]
> https://lists.mozilla.org/listinfo/dev-platform
_______________________________________________
dev-platform mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-platform
--
-- Rok Garbas

_______________________________________________
dev-builds mailing list
[hidden email]
https://lists.mozilla.org/listinfo/dev-builds