Re: 2.7.2 for the New Year?

Jim Baker <[email protected]>
Newsgroups gmane.comp.lang.jython.devel
Message-ID <CAOhO=aNRi0injd_er8MG+2D5aLue2+Q-1eP9c48rf4ghGP1erw@mail.gmail.com>
Yes! This really needs to be done. There have been some important bugs
fixed since 2.7.1, per
https://github.com/jythontools/jython/blob/master/NEWS#L6

Also agreed with 1) avoiding getting sidetracked during beta, because
that's been very expensive in terms of schedule; 2) focusing more on docs,
and especially making that sustainable/automated via github PRs and
publishing via read the docs.

The reality is that 2.7.2 is not a big release compared to what was in
2.7.1, so hopefully it's going to be also a smooth process.

Thanks for bringing this up. It's been in the back of my mind that we need
to do this. Focusing on the calendar like this gives us a good and
reasonable goal.

- Jim

On Tue, Nov 21, 2017 at 4:32 PM, Jeff Allen <[email protected]> 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 from https://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 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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.