Keeping track of MQ patchsets…

Hey Everyone!

First some brief Background, Mozilla Releng has our code in a *lot* of repos, most being in Mercurial (a few other needs are in git or svn, but those are very rare relatively). I also do work for SeaMonkey which has needs with m-c, m-i, m-*, c-c, c-* etc. And needs with l10n

I personally manage all my patches with MQ. Which presents a problem for me, “keeping track of it all”. I used to try keeping open bugs, but thats hard with releng because while a bug may be open, we tend to have a good handful of patches attached to it, for various repos, and they need to land in certain orders sometimes.

Other ways I’ve tried to cope have been with landing as soon as the review comes in and avoiding writing patches for parts that need to land later until the first parts are landed/deployed. I found that method encompasses unneeded end-to-end times on bugs, and unnecessary context-switching.

To curb that I wrote a mozilla-build (bash) script [in ~/.bash_profile ] that sets an alias `patchset` that I run, and it works!

It especially works because I keep my code in /c/Sources/hg/* some repos are multi-levels deep, so this code could/should be improved or at least edited for your uses, but without further ado, this is how I manage my patchset (again note, all my work is in Mercurial, I do convert my stuff over to git/etc as needed though):

Continue reading

Posted in Mozilla | Leave a comment

Android Mobile Marketshare, and how we (Mozilla) stack up. – Part 1

So, I should preface this with a few big caveats!

  • I am not a metrics guy, nor do I pretend to be.
  • This post will not give you absolute numbers of users.
  • This post is not meant to show any sense of penetration into the market
  • Ignores all things Firefox OS for the purposes herein.
  • I present this as an attempt at data only and no pre-judging of where we should go, nor what we should do.
  • I am explicitly trying to avoid color commentary here, and allowing the reader to draw their own conclusions based on the static data.¹

What this series will attempt to show is:

  • Where the current marketshare is on Android OS’s (with citations where possible)
  • Where our (Firefox for Android) userbase is
  • Where we invest in builds/tests (due to length, this will be in a Part 2 — Will link from here once published)
  • How what we do in Release Engineering correlates to our known market (based on these stats). (also in Part 2)

Now to the juicy bits!

Google’s own stats on Android Marketshare

Currently Android has a pretty healthy marketshare on the later OS’s, and the earlier ones are seeing very very diminishing returns.

Android Usage Share Pie Chart

Android Usage Share on Dec 3, 2013, from http://developer.android.com/about/dashboards/index.html

Version Codename API Distribution
2.2 Froyo 8 1.6%
2.3.3 -
2.3.7
Gingerbread 10 24.1%
3.2 Honeycomb 13 0.1%
4.0.3 -
4.0.4
Ice Cream Sandwich 15 18.6%
4.1.x Jelly Bean 16 37.4%
4.2.x 17 12.9%
4.3 18 4.2%
4.4 KitKat 19 1.1%

This data was all from http://developer.android.com/about/dashboards/index.html so feel free to see updated data as of whenever you are reading this.

Stats from Google Play for “Firefox for Android”

Before we begin with the data, I need to clarify something readers may not be aware of at first glance, “What is an Install

Install in this context is any currently active device which has Firefox installed on it. It does not actually indicate frequent use.

Installs by OS – Release (org.mozilla.firefox)

Android_play_org_moz_firefox_redactedYes, you see that right, this is 81.4% of our GA users on some version of Android 4.0+.

Installs by OS – Beta (org.mozilla.firefox_beta)

Android_play_org_moz_firefox_beta_redactedOur beta audience is pretty similar with 83.59% on an Android 4.x or higher.

Installs by Chipset

Selecting by Chipset is a bit harder, since to do so we have to take a factor of how Releng does our Play Store releases (different buildID’s to factor to different chipsets). I am doing this by a feature of the play store, namely “Export as CSV” which gives buildID infoexport_as_csv

So with that in mind, here is the data:

Arm V7 Arm V6 x86
Firefox Beta 96.19% 0.90% 2.91%
Firefox GA 98.61% 1.39% N/A

The caveats to note is that I only gathered data from today’s Google Play installs, and I aggregated all installs over all versions, even ones that are multiple years old. We also do not have x86 released officially yet, so we only have beta users using that version.

Coming in Part 2:

  • Where does Mozilla Invest build and test resources for Android?
  • How does this compare to Mozilla’s Testing Infrastructure?

¹ -  This post as-is is indeed intended to be data without analysis/commentary. I don’t feel I’m greatly suited for the latter compared to other people possibly reading. In Part 2 I intend to show some correlaries-as-data to what we are doing inside Release Engineering as it compares to our users at large. I’m currently hoping to also write it devoid of any assertions/commentary.
- The underlying reasoning here is to help spur thoughts and commentary in others in order to further our mission using data, while at the same time without inserting my own opinions or biases into what I am presenting with this 2-part series. I do not yet know if I will do a commentary piece referencing these posts or not, and I may do so, I just don’t yet plan to.

Posted in Mozilla | Leave a comment

Mozillians… Where are your summit pictures?

Hey Everyone!

I hope your #mozsummit was even half as good as my own!

I am looking for links to all photos taken at summit locations, selfishly looking for ones of me, but while I’m doing this I had heard from IRC that there was a suggestion of “one big album” of pictures on a by-location basis.

So I’m offering to do a few things:

  • Gather said list of pictures, be it albums or individual pics
  • Inform anyone I personally recognize from each picture that they are in them
  • Publish as a group-of-links and/or a real photo-album somewhere (with credits)

What I would need from you:

  • Link(s) you have to any summit photo’s you have (or ones snapped by others if you have their permission to share with me)
  • Which summit location you were at
  • Any requirements you have on publishing (Creative Commons License)
  • Any requirements you have on your own name being publically linked to said pictures (I’ll avoid doing this unless I get a direct “yea link me”)
  • If your photos are stored privately, how I’m able to access them (password, become your FB friend, etc.)

How to tell me:

  • Email: jwood@mozilla.com or Callek@gmail.com — please use include “Summit2013″ somewhere in the subject
  • This blogs comments
  • Facebook Message (if you are friends with me on Facebook)
  • Twitter: @mozCallek
  • Google+ : (Sorry but I _never_ check this, so please use one of the above methods, I do have an account there so I can check an album on it if thats where your photos are)

With time permitting I’ll have some sort of nice-looking web app to let you find yourself/others, if not I may just correlate all these to an individual blog post and list.

It was wonderful meeting all you Mozillians, and I have never been so proud of us as a community

EDIT: Seems I wasn’t clear enough, you do not need to e-mail me full collections of images, a link to anyplace already existing is perfectly fine.

Posted in Mozilla | 8 Comments

SeaMonkey 2.18 – Where are you?

Hey Everyone,

So SeaMonkey 2.18 was supposed to be out today, so where is it?

We have had a hardware error in the systems that allow us to reliably generate the release — Without these systems anything we create will be of unknown quality/stability.

In order to meet our own quality and stability requirements we are NOT releasing SeaMonkey 2.18.

While there is a chance we could have these systems back up in time to do an intermediate release (say something corresponding to a possible Gecko 21.0.1) we can not promise nor plan for it at this time.

We are actively working on repairing the system and its data, once that is complete we will go forth with a new BETA based on the SeaMonkey 2.19 train, and we expect to release SeaMonkey 2.19 on time, on June 25′th.

We thank you for your understanding.

Posted in Mozilla | 2 Comments

Welcome Back — Linux32 Tests!

As many of you know, last week we turned off many of our linux32 tests for desktop Firefox builds.

Yesterday, we were given the confirmation that we are now able to turn those tests back on, and we have done so.  You should now see Fedora32 tests on all your Inbound, Central, and Try pushes, as well as any twig/project-branches.

Any questions/issues join us in #releng on irc.mozilla.org.

Posted in Mozilla | 1 Comment

Blogging More…. About Mobile?

Hello Planet, Long time no see.

Since our last conversation a lot has changed with me (and Mozilla!) I was a contractor since March, and just got my official offer to come on as a “real” employee. I will be detailing my journey in the community to a full time employee through a series of upcoming blog posts. (now don’t get me wrong, I’m still working on SeaMonkey in my free time too)

To also mix it up, I intend to throw in many blog posts about the state of our Mobile Infrastructure/Tooling, and where we intend to go from here. However I need ideas on posts! So to get me started, I’d like to enlist you, planet readers, to send me questions/topics you would like to learn more about when it comes to Mobile Automation (in Release Engineering) that I could blog about for you. History Lessons, Future Direction, Current Setup, Whatever!

Send your Topics/Questions to me at callek+blog@mozilla.com I cannot promise I will address every question/topic requested, but I can promise to try.

This work so far has been both challenging and a thrill!

Until Next Time!

Posted in Mozilla | Leave a comment

New Addition to the Team!

Just wanted to say, that Edmund Wong, who I have previously written about here has just reproduced.

He and his lovely wife just had a baby!

I won’t share any more details than that, since I just found out, and have not asked permission, but I did grant him access to post on my blog here, and I invite him to do so pictures and all!

Posted in Mozilla | Leave a comment

SeaMonkey Build Machine Update

Today I finished up work I’ve been preparing most of this week to update our linux build machine software.

A few new software installs, as well as a few software upgrades.

Most notably is an upgrade to our buildbot code in production here (to match what is currently in use at Mozilla for Firefox). [special thanks to dustin for his help getting me rpms and files as mozilla prepared them for their own use]

There should be no issues, since most of the changes were in the way our automation is setup not in what actually produces/creates builds. and this work affects all branches. (SeaMonkey 2.4 final is already built, so did not affect that).

If you see anything that seems broken to you on linux, or any weird issues, please let me know by filing a bug (blocking Bug 687797), or finding me on IRC.

Posted in Mozilla | 1 Comment

Broken updater for Mac Nightly builds

Taking a queue from Nick Thomas (Post), and as he so deftly notes. This breakage is also for SeaMonkey. To quote him (while replacing with the SeaMonkey Info [in bold])

There was some accidental breakage in the Mac builds of Nightly last Friday (Sept 16th), which results in a crash when you try to update your build. The revision & buildID for the broken build is

  • ad202468df63, 20110916003001

You can check what you have by loading about:buildconfig, or evaluating navigator.buildID in the Error Console.

The solution is to download the latest Nightly build from http://ftp.mozilla.org/pub/mozilla.org/seamonkey/latest-comm-central-trunk.

Thank you Nick for calling out this issue!

Posted in Mozilla | Leave a comment

SeaMonkey 2.3.2 reports as 2.3.1…

Due to the relatively large quantity of reports we are getting, even with my comments in newsgroups, I think I should post this wider.

SeaMonkey 2.3.2′s download internal files, internal version, and all else of 2.3.2 except our website and files at our download directory location are indicating that it is SeaMonkey 2.3.1. (details in Bug 683473)

There is nothing to worry about there, we did properly include the DigiNotar cert block, as did Firefox 6.0.1. We are however also getting ready to release a SeaMonkey 2.3.3 release for a related Gecko issue, so we will correct our version number with that release, and not bother with any more updates with SeaMonkey 2.3.2 (See the bug driving this respin of Firefox at our bugzilla instance)

We are sorry about all confusion, and any issues this may have caused.

Stay tuned at our official blog for the release of SeaMonkey 2.3.3!

Posted in Mozilla | 1 Comment