Hi, On 6/29/20 4:04 PM, Matti Picus wrote:

The foss.heptapod.net team is working hard to convert bitbucket mercurial repos. This is good time to remind everyone to check that you have not left code on bitbucket: the deadline for removal of mercurial support there is the end of June.

The pypy/pypy and pypy/pypy.org repos will now allow anyone with "developer" status and above (so basically anyone who asks) to commit long-lived branches. Previously "developers" were restricted to only use topic branches, which are a new experimental mercurial feature. The ability to push long-lived branches is  similar to the way bitbucket worked.

For completeness I should add that Heptapod is publishing out of topics, meaning that changesets that don't have topics are automatically published once pushed to the server. The most traditional Mercurial setting is to automatically publish all drafts upon pushes. I know that Bitbucket could be set to be fully non-publishing on a per-repository basis. I don't what the setting was for PyPy on Bitbucket, so that may actually be a difference. Best, -- Georges Racinet https://octobus.net, https://about.heptapod.host, https://heptapod.net GPG: BF5456F4DC625443849B6E58EE20CA44EF691D39, sur serveurs publics

Hi, On 6/29/20 4:04 PM, Matti Picus wrote:

The foss.heptapod.net team is working hard to convert bitbucket mercurial repos. This is good time to remind everyone to check that you have not left code on bitbucket: the deadline for removal of mercurial support there is the end of June.

The pypy/pypy and pypy/pypy.org repos will now allow anyone with "developer" status and above (so basically anyone who asks) to commit long-lived branches. Previously "developers" were restricted to only use topic branches, which are a new experimental mercurial feature. The ability to push long-lived branches is  similar to the way bitbucket worked.

For completeness I should add that Heptapod is publishing out of topics, meaning that changesets that don't have topics are automatically published once pushed to the server. The most traditional Mercurial setting is to automatically publish all drafts upon pushes. I know that Bitbucket could be set to be fully non-publishing on a per-repository basis. I don't what the setting was for PyPy on Bitbucket, so that may actually be a difference. Best, -- Georges Racinet https://octobus.net, https://about.heptapod.host, https://heptapod.net GPG: BF5456F4DC625443849B6E58EE20CA44EF691D39, sur serveurs publics