On Tue, Jul 7, 2020 at 9:41 PM Barry Warsaw wrote:
>
> That said, I also think that the general rule of only bug fix changes post
> beta 1 is the right policy. For other changes, or anything that you think
> straddles the line between bug fix and non-bug fix, ask the Release
> Manager. The
On 2020-07-07 21:35, Barry Warsaw wrote:
It’s true that as releases get closer to final, more people will start
exercising them. However, you really don’t have to wait. I maintain
“official” Linux (Ubuntu) Docker images that contain all the latest releases
(including alphas and betas), and
On 07Jul2020 0321, Raymond Hettinger wrote:
My two cents: I think this should be a little more liberal. At beta 1, freeze the addition of new features but continue to tweak the implementation with code clean-ups, additional tests, algorithmic improvements, and better docs.
All of those things
On Mon, Jul 6, 2020 at 7:21 PM Raymond Hettinger <
raymond.hettin...@gmail.com> wrote:
> My two cents: I think this should be a little more liberal. At beta 1,
> freeze the addition of new features but continue to tweak the
> implementation with code clean-ups, additional tests, algorithmic
>
It’s true that as releases get closer to final, more people will start
exercising them. However, you really don’t have to wait. I maintain
“official” Linux (Ubuntu) Docker images that contain all the latest releases
(including alphas and betas), and the git head of the development branch at
On Mon, Jul 6, 2020 at 7:21 PM Raymond Hettinger
wrote:
> If not, perhaps we should just have a single beta, frozen except for bugfixes.
+1 for having betas frozen, except for bug fixes. But the bug fixes
need to go somewhere, so I propose to have yet another frozen beta (if
there are bug
Le mar. 7 juil. 2020 à 04:21, Raymond Hettinger
a écrit :
> At beta 1, freeze the addition of new features but continue to tweak the
> implementation with code clean-ups, (...)
IMHO clean-ups should stop after beta1. Only the master branch should
receive cleanup changes. A clean-up doesn't
My two cents: I think this should be a little more liberal. At beta 1, freeze
the addition of new features but continue to tweak the implementation with code
clean-ups, additional tests, algorithmic improvements, and better docs. For
many of the devs (and users), the first time we get to