New candidate JEP: 369: Migrate to GitHub

[Dalibor Topic]

On 14.11.2019 15:55, Mario Torre wrote:> Right, however none of those 
projects so far have real world, directly
> comparable, experiences to share. JMC for one is still running on
> mercurial and will only transition to GitHub for the 8.0 release
> train, which isn't yet even open.
> 
> I think we really need to get back to this proposal in an year or two
> when we understand more of the implications.
> 

Considering that Mercurial requires [0] Python 2.7 and Python 2.7 has 
six more weeks of life left [1], well ... I don't think it's realistic 
to expect Mercurial to remain a generally useful tool for two more 
years, in particular given that there is no roadmap [2] to move Python 3 
support in Mercurial out of experimental/beta status in the coming weeks.

And that doesn't even consider extensions, since

"3. Things need to be investigated"
[..]
" Nearly every extension will break in Python 3. "

So ... yeah.

cheers,
dalibor topic

[0] https://www.mercurial-scm.org/wiki/SupportedPythonVersions
[1] https://pythonclock.org/
[2] https://www.mercurial-scm.org/wiki/Python3
-- 
<http://www.oracle.com>
Dalibor Topic | Consulting Product Manager
Phone: +494089091214 <tel:+494089091214> | Mobile: +491737185961
<tel:+491737185961> | Video: dalibor.topic at oracle.com
<sip:dalibor.topic at oracle.com>

Oracle Global Services Germany GmbH
Hauptverwaltung: Riesstr. 25, D-80992 München
Registergericht: Amtsgericht München, HRB 246209
Geschäftsführer: Ralf Herrmann

<http://www.oracle.com/commitment> Oracle is committed to developing
practices and products that help protect the environment