Hello! I noticed that WG9s' builds are not any longer based on specific commits of mozilla-release and comm-release on hg.mozilla.org/ but now refer to foss.heptapod.net. Since the patch queue has also dramatically shrunk in size: Am I correct in assuming that the heptapod repositories contain kind of the (already applied) stable part of the patch queue? Also, I was wondering why the code is...

...now on gitlab and on heptapod. Is this for convenience (hg vs. git) or do they serve different purposes?

teruna It became unmanagable and also the queue stabilized. I started the patch queue long ago and it was just meant as a stopgap then till we caught up with comm-central again. Will all the mozilla stuff ripped out and mangled since then became the lifeline it is now. See gitlab.com/frg/seamonkey-253-patches/-/blob/master/readme-first.txt for applying the queue.

frg_Away: Thanks, I already successfully built for Arch Linux from the new source repository and the shortened patch queue. But why gitlab and heptapod?

teruna Patch queue just started at gitlab. heptapod allows us the use hg and the mq extension. We could probably move the queue to heptapod too but if it is not broken ... The official gitlab repos are only used for releases not development.

frg_Away: Thanks for the explanation!

teruna we also use the patches to bring suite in comm-central up to date over time. comm-central is also hg based.

So anything for suite goes into 2.53 and central.

tada ibb.co/pxVKhM2

Well not enabled by default and missing more pieces than you can count.

And yes the polyfill add-on was disabled.