Re: 2.7.2 for the New Year?

I'm continuing the triage of issues, slowly. Given our rate of work and 
jointly-expressed desire for a release, I find the only rational course 
is to take off nearly all the 2.7.2 tags, unless it would be harmful to 
release with that issue. (I might add some on that basis.) I'll do my 
best to follow the comments on each issue first.

I'll get this wrong many times, so if I've taken 2.7.2 off where you can 
see Jython wouldn't be viable with that issue outstanding, please argue 
it on the issue. Also, a good patch or commit is close to an irrefutable 
argument for inclusion. Anyone is free to to fix something just because 
they think it worthwhile or fun to do: we're all volunteers.

That said, we have a fair number of issues related to sockets/SSL that I 
find difficult to assess accurately and could not easily work on. If 
your skills and interest run that way, they might be good choices.

Some projects tag issues as "suitable for beginners". We don't have such 
a tag, but as I go through the issues, I find Jim has often done the 
like in a comment or given a hint towards the likely solution, which is 
useful for the rest of us.

Other thoughts in line ...

Jeff

On 26/02/2018 03:00, [email protected] wrote:
> Hi Jeff - some comments inline:
>
> On Sun, Feb 25, 2018 at 12:49 AM, Jeff Allen <[email protected]> wrote:
>> It's still the New Year :)
>>
>> We currently have 85 open bugs tagged Milestone 2.7.2, and about 250 others.
>> (20 or so are tagged 2.7.1 or 2.7.0, but I think that's mostly a
>> misunderstanding at the time they were raised.) It's hard for me to say
>> which should be show-stoppers.
>>
>> I thought I'd at least read them all. So far I've got 2 categories: "fairly
>> sure I can close" and "that's not simple".
>>
>> I think we should have tagged as Milestone 2.7.2 only those things we have a
>> serious intention to fix by the end of 2.7.2b, and everything else
>> decisively put off. Knowledgeable contributions to this process would be
>> welcome.
> That sounds right to me, we can put others into a 2.7.3 Milestone perhaps.
No milestones are available for selection in the tracker beyond 2.7.2, 
so we can't express that idea at present. Also, I think it means very 
little to add 2.7.3 until we start to plan it. Anything not tagged is a 
candidate for 2.7.3 according to priority (or fancy). Priority and 
severity are useful at all times, I think.

A 2.7.3 milestone could be in the database ready, however. Oddly, I can 
report an error against 2.7.3 if I want, but not against 2.7.2.

>> I think (below) Frank bids a GitHub-based website as part of the 2.7.2,
>> which I think is highly desirable for communication reasons.
> Yes I need to look at the logistics of getting a github based website
> up and running. I'll try to find some time to look into that soonish.
That would be great. And we need the basic content, of course, before 
throwing the switch. I'm going to focus on the issues triage.

Jeff

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