From: Adam B. <ada...@gm...> - 2019-01-07 10:55:57
|
I just checked out out the head for the first time in a while and regrtest is green for me under Windows and Java 8. Great to see. <0.02 put in jar> >From my (front-row?) spectator seat, I think more frequent patch releases wouldn't hurt. It's been a fair while since 2.7.1. If the tests are green, bugs have been fixed, and more stuff works in 2.7.2 than 2.7.1, I would vote to ship. If the gradle stuff is working well enough to produce a jar, it could be included and marked experimental? I'm sure it would be useful to projects with dependencies on jython from maven or gradle projects. Obviously it would be good to announce the beta on the website though. Cheers Adam On Wed, 2 Jan 2019 at 09:55, Jeff Allen <ja...@fa...> wrote: > Happy New Year. > > We didn't get 2.7.2 out in 2018, but I think it is within reach to do so > in the first half of 2019, with a beta in (say) February. > > The triage I did last Spring appears still to be valid. What looked like > a highly focussed list proved to contain some many-headed problems. > There are still 14 open issues in the milestone, but I would say that > the difficult ones have yielded most of the way. We have done some work > not in the original target because of enthusiasm or outside contributions. > > Web site: not sure what the blockage is, but I think we need it to > launch the beta release. > > Gradle support: I believe "support" means we produce artefacts others > may use in a Gradle build. Jim originally considered Gradle support to > be essential, but has moderated that (elsewhere in this thread). My view > is that it is highly desirable, but I don't know quite what to produce, > although another thread in this list contains a helpful discussion. I'd > like to make Gradle experimental in beta so we can get some experience > and feedback. > > Jeff > > Jeff Allen > > On 26/02/2018 03:00, fwi...@gm... wrote: > > Hi Jeff - some comments inline: > > > > On Sun, Feb 25, 2018 at 12:49 AM, Jeff Allen <ja...@fa...> 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. > > > >> 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. > > > > Thanks for looking into this and keeping the ball rolling! > > > > -Frank > > > > > _______________________________________________ > Jython-dev mailing list > Jyt...@li... > https://lists.sourceforge.net/lists/listinfo/jython-dev > |