Re: 2.7.1rc, to infinity and beyond!

> Agreed that getting on github will not be the most minor fix

It occurred to me that this change actually aligns with our focus shift to Jython 3. Maybe we can benefit from this by setting up the new workflow only for Jython 3. Then it would be kind of a reboot rather than a (potentially painful) migration. It would naturaly sort out Jython 3 stuff from Jython 2 stuff. (We could even consider to track Jython 3 issues on github and continue bjo just for Jython 2.) Think about it.

> I also felt it was important to highlight Stefan's contribution to helping finalize 2.7.1

It's a great honor for me to be mentioned for this. Thank you very much!

Looking at ACKNOWLEDGEMENTS I found that the file does not explicitly display who is actually core-developing Jython right now. Jeff, Jim, Darjus and Frank who are putting a lot of work into Jython (or did so in the last years) are mentioned randomly between all contributors, including persons with really minimal contributions (don't get me wrong - every contribution is very valuable!). While this is a very modest attitude I think the (active) core-dev team should be explicitly named somewhere at the beginning of the file, not lastly because users might need this info to assess who to ask. Also - maybe I overlooked it - it is nowhere stated that Frank is the project lead. This should be made clear IMO. In case we decided to add such a section I'd suggest to also mention James Mudd,
at least for this release, because he spent significantly more work on Jython than the average contributor.

> I'll get the soft release together this weekend. If there are no troubles, I'll get the hard RC2 out next week.

Looking forward to it! Thanks a lot.

Best regards

-Stefan

Gesendet: Samstag, 27. Mai 2017 um 20:43 Uhr

Von: "[email protected]" <[email protected]>

An: "Jim Baker" <[email protected]>

Cc: "Jython Developers" <[email protected]>

Betreff: Re: [Jython-dev] 2.7.1rc, to infinity and beyond!

Great news, and amazing work everyone! I'll get the soft release together this weekend. If there are no troubles, I'll get the hard RC2 out next week.

On May 27, 2017 10:46, "Jim Baker" <[email protected] > wrote:

Updated README to state RC2, plus fixed the typo. Thanks for the feedback!

Agreed that getting on github will not be the most minor fix (!), but it will be worth the effort. I do like Mercurial, and very much appreciate the Hg team's help in moving Jython to hg.python.org from Subversion. Nonetheless, we found out in using Mercurial for the last 5 or so years for Jython development that it didn't match our development processes. It's both time to move on, and join CPython upstream in its dev processes.

On Sat, May 27, 2017 at 5:07 AM, Adam Burke <[email protected] > wrote:

I know I'm a lurker and not an active dev, but I'd prefer the rc2 name as well, fwiw.

Cheers

Adam

On 27 May 2017 at 15:33, Jeff Allen <[email protected] > wrote:

Excellent news! A lot has gone on between 2.7.0 and 2.7.1. it's good to find we've all feel "done"at the same time :)

Small typo in your front page: "many others to thanks".

I have a weak preference for calling it RC2 given there was change after RC1. I think RC1 still identifies a release, even if it was announced softly, and what we have now is different.

There's a bit more to cutting over to Git than declaring it so. I've been watching CPython do this with the corner of one eye. We will have both bugs.jython.org and Git pull requests for a while ... essentially forever. There was some integration work (which we should steal, but that depends, I suspect, on upgrading the tracker) and conventions for how to refer to one from the other. It was tough at points because of disagreement on how it were best done, but we can just go along with their conclusion. And s/bpo/bjo/.

Jeff Allen

On 27/05/2017 01:12, Jim Baker wrote:

Agreed. It's time for putting this release candidate out! I'm also glad about the timing, because this mean Stefan has a great base to build this summer's work on JyNI. I believe it's technically RC1 still because the last RC was a soft release, but Frank knows those specifics.

I just ran the "yolk smoke test" from http://bugs.jython.org/issue2570 < http://bugs.jython.org/issue2570 > one last time, just to make sure. Everything looks great!

After this we can look into:

1. Finally get jython.org < http://jython.org > revamped. I suggest the simplicity — and modern look — of GitHub pages, where we can host and then point jython.org < http://jython.org > accordingly.

2. Switch to the Gradle build that Darjus has been working on

3. Cut over to https://github.com/jython/jython with rewritten history that removes extlib jars for a subsequent release of 2.7.x, where x > 1 (maybe it's 12 for the next release, but we can decide later).

Lastly, I also felt it was important to highlight Stefan's contribution to helping finalize 2.7.1, as well as our appreciation to Google for supporting him this summer for the Google Summer of Code. First win for GSOC 2017 in other words. Duly noted as of https://hg.python.org/jython/rev/ab5434be88aa

- Jim

On May 26, 2017 7:24 PM, "Stefan Richthofer" <[email protected] <mailto:[email protected] >> wrote:

> You can apply these updates to extlibs

Done as of https://hg.python.org/jython/rev/f6b3ddbc1df8

< https://hg.python.org/jython/rev/f6b3ddbc1df8 >.

From my point of view we can launch Jython 2.7.1-RC2 now.

- no open PRs on github left

- no release blockers left apparently except #2487

- all updates done as far as possible (python std-lib will be next

challenge on this front)

So, I'd suggest everybody pushes last-minute work and Frank hits

the release-button... :-)

What do you think?

Cheers!

-Stefan

<snip>

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

Check out the vibrant tech community on one of the world's most

engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________

Jython-dev mailing list

[email protected]

https://lists.sourceforge.net/lists/listinfo/jython-dev

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

Check out the vibrant tech community on one of the world's most

engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________

Jython-dev mailing list

[email protected]

https://lists.sourceforge.net/lists/listinfo/jython-dev

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

Check out the vibrant tech community on one of the world's most

engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________

Jython-dev mailing list

[email protected]

https://lists.sourceforge.net/lists/listinfo/jython-dev

------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ Jython-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jython-dev

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

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