[Reviewers] Mercurial 4.0.2 tagged

[Kevin Bullock]

> On Jan 4, 2017, at 12:00, Pierre-Yves David <pierre-yves.david at ens-lyon.org> wrote:
> 
> On 01/04/2017 06:58 PM, Kevin Bullock wrote:
>>> On Jan 4, 2017, at 11:54, Pierre-Yves David <pierre-yves.david at ens-lyon.org> wrote:
>>> 
>>> [Moving the discussion to reviewers]
>>> 
>>> On 01/04/2017 06:18 PM, Kevin Bullock wrote:
>>>> Please update your package builds, thanks.
>>>> 
>>>> Note that the tag and signature are only in hg-committed right now -- this is due to a known bug in our new patch acceptance process and will be fixed at some point. The tag and signature should land in main within the next day or two.
>>> 
>>> Can you "force push/pull" your tag in the main repository?
>>> If we have announced a version and published packaged, I think we needs these changesets to be public and in the main repository.
>> 
>> Theoretically I could use my admin rights to pull into main, but I'd rather not do that. The simpler solution is for another reviewer to accept the tag and sign changesets.
> 
> Ha, it felt like there was something more serious. I have already done so (second acceptance tag) so this should get published.

Looks like the second accept wasn't enough to land the changes in main, and the culprit seems to be the i18n change that I pushed in the process of releasing. That change was already public, which means neither it nor any of its descendents will get landed automatically.

I used admin rights to manually pull only the i18n change into main. The scripts went the rest of the way to land my tag+sign changesets. I don't remember hitting the same issue on last month's release, which is strange--there definitely was an i18n change pulled in at that time.

Anyway, this will be one more issue to keep in mind while we fix the i18n sync, accept, and release processes.

pacem in terris / мир / शान्ति / ‎‫سَلاَم‬ / 平和
Kevin R. Bullock