> my goodness did they beat around the bush w/regard to their actual contribution to this process (per the title).
Fair point. I came up with the title first. Then as the content grew large and diluted the essence of the title, I reconsidered, but ended up sticking to it as a shameless clickbait.
> Originally, separate clones was the recommended way to do "topic branches" in Mercurial (not to be confused with "named branches").
That still leaves the question "why topic branches rather than named branches?". For the needs of the rapid release process, named branches could have been used, but weren't. I haven't tried to contact the people involved at the time to have a definite answer. It's not /that/ important, and I'm not /that/ curious.
What a beautiful post it has become nevertheless rivaling the long reads of the New Yorker and the like.
I originally wanted to go to sleep but the writing was too captivating to put down, and every paragraph was motivated, and it wasn’t stretched. It was the length it needed to be.
One of the Firefox rapid release designers here :-)
IIRC, topic branches were used because:
- Mercurial named branches were half baked at the time and I was advised against them by folks who knew hg better than me.
- We were already using separate clones for security update versions (3.5.x and 3.6.x) so we just kept doing the same. Some tooling could be reused.
- Rapid release was a big change and we didn't want to disrupt mozilla-central dev. Having rapid release in different clones got us out of the way and reduced the risk of negatively affecting development. m-c was the domain of developers, the rr repos were the domain of the release team.
> Fair point. I came up with the title first. Then as the content grew large and diluted the essence of the title, I reconsidered, but ended up sticking to it as a shameless clickbait.
I enjoyed it. It could maybe have been two posts, but it's a headline, it's supposed to get you to click on it.
> my goodness did they beat around the bush w/regard to their actual contribution to this process (per the title).
Fair point. I came up with the title first. Then as the content grew large and diluted the essence of the title, I reconsidered, but ended up sticking to it as a shameless clickbait.
> Originally, separate clones was the recommended way to do "topic branches" in Mercurial (not to be confused with "named branches").
That still leaves the question "why topic branches rather than named branches?". For the needs of the rapid release process, named branches could have been used, but weren't. I haven't tried to contact the people involved at the time to have a definite answer. It's not /that/ important, and I'm not /that/ curious.