Branching and maintenance strategy, tracking mozilla releases, notifying users?

[ajvincent]

Now that this is at least minimally working, one consideration is how to handle evolving changes to Mozilla which could break builds here.

In particular, Mozilla Firefox's release calendar shows:

• extended-support release branches are good for a little over a year,
• general releases are good for four weeks,
• mozilla-central is a moving target.

I don't know how to approach this yet.

[trickypr]

My recommendation would be to let the user chose the version to target. Store the current version in a config file, then a GitHub bot (e.g. this is my bot implementation) can come through and file an issue on each update (e.g. pulse-browser/browser#156).

[ajvincent]

Huh, I didn't know about Pulse. Awesome. 😎 If there's a mailing list for this project, I want to be on it.