Re: [Jython-dev] Changes coming to CPython's code hosting

[Jim B. <jim...@py...>]

Brett,

Thanks for keeping us in the loop!

Sounds good about the switch to GitHub - this is in line with work we have
done to-date, including getting control of https://github.com/jython

Likely the switch to code management should be a top priority for 2.7.2
development, which should commence sometime in the next month or so
(depends on the delayed 2.7.1 getting out first!). We have an outstanding
bug, http://bugs.jython.org/issue2182, that needs to be solved first - this
will allow us to strip out third-party jars so we are no longer tracking
directly in the repo. Once #2182 is taken care of, we can then immediately
switch, and for the time being, mirror to hg.python.org/jython.

Except for a few cases, we haven't used Rietveld in our review process, so
that shutdown doesn't impact us.

We of course use bugs.jython.org - it's the essential tool for tracking
most dev in Jython - so we don't want that shut down. I'm pretty sure that
we would simply want whatever goodness that is being worked on for
bugs.python.org applied to our version, especially anything to help review
workflows.

I have subscribed to cor...@py..., and I encourage other
interested Jython developers to do so.

- Jim

On Sun, Jan 3, 2016 at 3:14 AM, Darjus Loktevic <da...@gm...> 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)?
>
> 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.
>
> Cheers and Happy New Year!
> Darjus
>
> On Sun, Jan 3, 2016 at 5:56 AM Brett Cannon <br...@py...> 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 cor...@py... 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
>> Jyt...@li...
>> https://lists.sourceforge.net/lists/listinfo/jython-dev
>>
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> Jython-dev mailing list
> Jyt...@li...
> https://lists.sourceforge.net/lists/listinfo/jython-dev
>
>