Hi Rob, I think this should also go to maildev. Adding CC. So, a question: If we wanted to build test the current released code (or about-to-be released code), or if we wanted to backport patches that do not apply cleanly and create a clean branch patch, which repo URL would we use? In order to script things, it would be preferably to have a single URL that always gives the current release, instead of having to change from comm-esr60 to comm-esr68 to comm-esr78 to... yes, which one is the next? I don't know when to pull which URL. Also, it's easier for documentation when the URL is always the same, and stays identical for years. Ben Am 09.11.20 um 19:53 schrieb Rob Lemley: > > Starting with next week's merges, I do not plan on updating the > *comm-release* repository and intend to have it set to a read-only state. > > Thunderbird has not used comm-release in several years (except in > creation of new ESR repositories). I reviewed the push log going back > to pre-Thunderbird 60. There was one push that was not part of merge > day activities. The Seamonkey team has indicated that this change is > okay with them. > > With regard to the next ESR repository, it can be created from > comm-beta. There is no reason for the extra step. > > Additionally, there is the never-used *comm-moz-esr68* repository that > I will ask to be removed. > > -Rob > > -- > *Rob Lemley* > Thunderbird Release Engineer > rob@thunderbird.net - :rjl > -*- #thereisonlyxul -*- > > _______________________________________________ > tb-planning mailing list > tb-planning@mozilla.org > https://mail.mozilla.org/listinfo/tb-planning

Hi Ben, Thanks for your comments. Aside from cutting back on unnecessary maintenance work, another reason for doing this is to reduce confusion about which repository is what. Neither Thunderbird nor Seamonkey actively use comm-release. Let's stop updating it, label it as deprecated in the web UI, and mark it read only. Nothing changes which repository is used for (current) releases. Release builds will continue be from comm-esr78/mozilla-esr78 and betas from comm-beta/mozilla-beta. It looks like the next esr is going to be esr91[1]. I don't want to get ahead of myself too much, but the one-repo project is something being worked on for this development year, so things are going to change. I don't have any specifics yet since it's just getting started. -Rob [1] - https://wiki.mozilla.org/Release_Management/Calendar On 11/9/20 2:39 PM, Ben Bucksch wrote: > Hi Rob, > > I think this should also go to maildev. Adding CC. > > So, a question: If we wanted to build test the current released code > (or about-to-be released code), or if we wanted to backport patches > that do not apply cleanly and create a clean branch patch, which repo > URL would we use? > > In order to script things, it would be preferably to have a single URL > that always gives the current release, instead of having to change > from comm-esr60 to comm-esr68 to comm-esr78 to... yes, which one is > the next? I don't know when to pull which URL. Also, it's easier for > documentation when the URL is always the same, and stays identical for > years. > > Ben > > > Am 09.11.20 um 19:53 schrieb Rob Lemley: >> >> Starting with next week's merges, I do not plan on updating the >> *comm-release* repository and intend to have it set to a read-only state. >> >> Thunderbird has not used comm-release in several years (except in >> creation of new ESR repositories). I reviewed the push log going back >> to pre-Thunderbird 60. There was one push that was not part of merge >> day activities. The Seamonkey team has indicated that this change is >> okay with them. >> >> With regard to the next ESR repository, it can be created from >> comm-beta. There is no reason for the extra step. >> >> Additionally, there is the never-used *comm-moz-esr68* repository >> that I will ask to be removed. >> >> -Rob >> >> -- >> *Rob Lemley* >> Thunderbird Release Engineer >> rob@thunderbird.net - :rjl >> -*- #thereisonlyxul -*- >> >> _______________________________________________ >> tb-planning mailing list >> tb-planning@mozilla.org >> https://mail.mozilla.org/listinfo/tb-planning > > > > _______________________________________________ > tb-planning mailing list > tb-planning@mozilla.org > https://mail.mozilla.org/listinfo/tb-planning -- *Rob Lemley* Thunderbird Release Engineer rob@thunderbird.net - :rjl -*- #thereisonlyxul -*-

Am 09.11.20 um 22:17 schrieb Rob Lemley: > the one-repo project is something being worked on for this development > year, so things are going to change. I don't have any specifics yet > since it's just getting started. Yeah, I didn't want to distract this thread, but having all branches (dev, beta, release, past releases) in one repo is the obvious solution. After that, it should be easy.