Abandoning gecko@ maintainership
jbeich at FreeBSD.org
Wed Sep 2 12:07:22 UTC 2015
I don't have much time to hack on gecko@ nowadays. It's caused by burnout
From trying to keep things I don't use working, the fast pace of upstream
development, my aged hardware and poor teamplay (mea culpa). Hopefully, this
answers the question of why many gecko@ bugs remain untriaged. If other
gecko@ members are also inactive then maybe it's time to disband the team.
So, good luck with the next www/firefox update (to 41.0+). Useful tips:
- To avoid rush prepare for releases in advance using buindN candidates
- For a bit out-of-date list of ideas to work on see Gecko_TODO
- Many patches are tracked as issues/review on bugzilla.mozilla.org
- A few can be dropped if prove to be hard to maintain
- Non-official buildbot can be used for tracking upstream breakage
I'll probably keep www/firefox-esr up to date for esr38 lifecycle to avoid
security issues but no plans for after that. Not documenting my workflow as
it was way too inefficient.
 files/patch-z-bug517422 and files/patch-bug1021761
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 602 bytes
Desc: not available
More information about the freebsd-gecko