Re: [Jython-dev] 2.7.2 for the New Year?

[James M. <jam...@gm...>]

Hi All

I think the idea of having a 2.7.2 release soon is a good one. There are a
few important fixes already included since 2.7.1 especially bug 2620 which
stops the launcher working on some Windows systems. I will look through the
2.7.2 tickets and see if I can help I don't have too much free time at the
moment though. I agree that narrowing down the bugs marked with milestone
2.7.2 will allow focus on what should be worked on.

The one which I currently have in progress 2639 is almost fixed but I have
added more tests and a few are still failing so I need to fix that up but
hopefully not much more work once I get round to it.

I think having a Github based website is a great idea. The current
jython.org site gives the impression the project is abandoned. Having one
place to go where you can see the code, latest news, docs and download
releases and contribute would be a benefit, in my opinion, but it will need
some effort to get started.

James

On 25 February 2018 at 19:40, Jeff Allen <ja...@fa...> wrote:

> (The jython-dev list has taken to rejecting my mail so resending to you
> explicitly. )
>
> 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". Very early days.
>
> 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.
>
> 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.
> Jeff
>
>
> Jeff Allen
>
> On 22/11/2017 19:42, fwi...@gm... wrote:
>
> A new year's 2.7.2 with a limited scope is definitely a great idea, as
> is an updated GitHub based website. I'm on board!
>
> -Frank
>
> On Tue, Nov 21, 2017 at 3:32 PM, Jeff Allen <ja...@fa...> <ja...@fa...> wrote:
>
> All:
>
> How about it? This seems like a reasonable interval since 2.7.1.
>
> Frank/Jim: would you care to set a goal? What else ought we to have in that
> release?
>
> I think we should mean by the answer, what we'd like to see in 2.7.2b1. Then
> we only take on fixes during beta we didn't foresee or can't avoid. That
> way, we hopefully don't stay in beta very long. I'm extrapolating a bit fromhttps://github.com/jython/devguide/blob/jython/devcycle.rst#stages (cloned
> from CPython) but it seems a good discipline to prevent late de-stabilising
> change.
>
> Is it perhaps as important to create a revised web site to back the release?
> (We have talked about a site we can all contribute to via GitHub.)
>
> Also, I've been meaning to ask, the current dev tip should identify as
> "2.7.1+" (not plain "2.7.1") shouldn't it? And 2.7.2a1 then 2.7.2a1+ as soon
> as we decide we're having a 2.7.2? I think I see how this works in
> build.xml.
>
> Jeff
>
> --
> Jeff Allen
>
>
> ------------------------------------------------------------------------------
> 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 lis...@li...https://lists.sourceforge.net/lists/listinfo/jython-dev
>
>
>