Open Bug 1551033 Opened 5 months ago Updated 5 months ago

Fork ChatZilla and DOM Inspector into SeaMonkey

Categories

(SeaMonkey :: Build Config, task)

SeaMonkey 2.49 Branch
task
Not set

Tracking

(Not tracked)

People

(Reporter: iann_bugzilla, Unassigned)

Details

In order to fold ChatZilla and DOM Inspector into SeaMonkey, the existing files (and preferably histories) need to be pulled into comm-* from their respective repositories but without any branches.
The first step for each would be to clone the repository and run hg convert --filemap to move the files into suite/extensions/[irc|inspector] and strip anything that is not the default branch
The next step would be to bring the information into comm-*.
Questions:
Is there a way of doing this, whilst keeping the history of about 2500 changes, without polluting the recent changelog?
What is the best way of importing the files and history?

Other times we have imported into an area of suite/ we have pulled the complete history in and attached to the tip of the comm repositories. We'd do as two sets, one for ChatZilla and one for DOM Inspector.
Any issues with this being done for comm-central, comm-esr60 and the SM2.53 branch on comm-release?

Flags: needinfo?(rob)
Flags: needinfo?(mkmelin+mozilla)

Why do you want to do it now, after all these years?
And aren't both of those super dead since at least a year or two?

I'm not sure anyone really cares if it's for comm-esr60 or the sm branch only, but I don't think we should add dead code to comm-central.

For how, hg convert indeed. I don't think there is any way of not polluting recent changelogs, at least the ones showing commits based on time.

Flags: needinfo?(rob)
Flags: needinfo?(mkmelin+mozilla)

(In reply to Magnus Melin [:mkmelin] from comment #2)

Why do you want to do it now, after all these years?
And aren't both of those super dead since at least a year or two?

I'm not sure anyone really cares if it's for comm-esr60 or the sm branch only, but I don't think we should add dead code to comm-central.

For how, hg convert indeed. I don't think there is any way of not polluting recent changelogs, at least the ones showing commits based on time.
The current long term plan is to integrate them into SM rather than them be add-ons, but also get localisation working smoothly for them which I think won't happen whilst they're in separate repos and not showing in comm-central

I wonder how useful this is for DOMI as we have a DOM inspection tool in devtools as well (I know, somewhat different, but still similar). For ChatZilla, I see a better case in general.

There are likely some changes coming for l10n and thunderbird (separate repo), so having the code in comm-central won't likely make anything any easier.

I think the better question is, do you actually see any chance for a seamonkey based on anything past 60? I have to say it would appear extremely unlikely you can pull that off from my POV.

You need to log in before you can comment on or make changes to this bug.