Re: Changes coming to CPython's code hosting

On Sun, 3 Jan 2016 at 02:14 Darjus Loktevic <[email protected]> wrote:

> Hey Brett,
>
> Thanks for the heads up. We've had a github mirror for a little while now,
> and "verbally" agreed to move development of Jython3 to github. With the
> news of hg.python.org going away, i guess we have no choice but to move
> all of Jython to github (personally really like github workflow, but can't
> speak for the rest of us).
>
> I think using jython org would be preferable/easier to manage, thought i
> assume we would still want to be covered under PSF contributor agreement
> procedure. Would that be a problem if we're not part of the python org (i
> doubt it but want to make sure)?
>

I specifically don't see why it would be a problem, but then again we need
to work out that procedure ourselves. :)


>
> Personally i don't mind moving issues to github (not sure we can actually
> move them), but i would hate for us to lose all the years of history. We
> need to discuss this internally, though i think we should follow what
> CPython is doing.
>

I'm not saying you have to shut it down, it's just an option if the tweaks
we make don't work for you.


>
> Cheers and Happy New Year!
>

Same to you!

-Brett


> Darjus
>
> On Sun, Jan 3, 2016 at 5:56 AM Brett Cannon <[email protected]> wrote:
>
>> I wanted to make sure you all are aware that the decision was made by me
>> yesterday to move CPython's development to GitHub. This means that
>> hg.python.org will most likely be shut down some time in the future.
>> Since this decision was reached literally on January 1 there are no
>> timelines yet, but my expectation is that hg.python.org and Rietveld
>> will be wound down this year (bugs.python.org isn't going anywhere).
>>
>> I know you host your code on hg.python.org and that you run an instance
>> of our issue tracker so I wanted to make sure you were aware of these
>> coming changes. I'm not sure if it still makes sense to have you work under
>> the python organization on GitHub vs. a jython org and if you want to stick
>> to your bugs.python.org clone with the changes we will be making to it,
>> but if you want that you can subscribe to [email protected] and
>> discuss it there (people also discussed using GitLab and people suggested
>> too late Bitbucket and Rhode Code if you want other options than GitHub if
>> you want to know what other options you have).
>>
>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Jython-dev mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/jython-dev
>>
>

------------------------------------------------------------------------------

_______________________________________________
Jython-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jython-dev