On 10/23/2015 8:25 PM, Mitchell Baker wrote:
Yes, this is a good topic and I agree i'm a necessary party here.
Is there some way of getting a good sense of the work that we're
talking about?
I'm not sure which work you're referring to here, but I will try to
answer to the best of my abilities.
The work required to actually do the merge is nothing more than a script
I've already written and tested, as well as a few days with a release
engineer to set up new configs. Ongoing maintenance would hopefully be
minimal, as the difference would hopefully just be using one config file
for Thunderbird and one for Firefox that differ only in things like
choosing which mozconfig to use or choosing which directory to upload
to, but I don't have a good enough insight into our build configuration
to know for sure. Ongoing build system maintenance would probably be
nil, excepting to-be-deprecated constructs which are used only in c-c
(which I do try to keep on top of anyways, so that shouldn't be an issue).
As for the work required in build system to maintain the current
state... There's a lot of hacks in the m-c build system to support
Thunderbird, particularly the --external-top-srcdir configure option,
the existence of multiple topsrcdirs, and checks for mozilla/ in several
places (yeah, don't add a new mozilla/ source directory to the build
system, things will break). The situation in release engineering is
worse, since at this point we're using completely different build
techniques, and it's hard or impossible for us to migrate to the
mozharness-based builds, since mozharness is in mozilla-central and
comm-central needs to do some build logic to figure out which version of
mozilla-central (particularly on the Try server) to support. The build
system support for the latter case also requires retaining partial
duplication of some functionality in comm-central, resulting in a
veritable Frankenbuild scenario.
On 10/23/15 6:15 PM, Doug Turner wrote:
Thunderbird is under supported and potentially harmful (as Brian
Smith pointed out on the mozilla-dev-security-policy back in Sept).
Before merging c-c into m-c, I think we should have agreement on what
kind of support the mozilla project and foundation is going to give
to Thunderbird.
FWIW, when Brian Smith made his comments on mozilla.dev.security.policy,
I did try to find a bug detailing what he was talking about... and I
couldn't find what he was talking about, which means that our security
team is finding problems in Thunderbird and not properly notifying any
Thunderbird developers of them.
--
Joshua Cranmer
Thunderbird and DXR developer
Source code archæologist
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
