[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Next release from master

From: Eli Zaretskii
Subject: Re: Next release from master
Date: Sun, 24 Jan 2016 16:11:47 +0200

> From: Stefan Monnier <address@hidden>
> Date: Sat, 23 Jan 2016 23:26:32 -0500
> - coders should know where to install bug-fixes and new features.

The chances of them knowing this with any certainty close to 100% are
nil, IME.  Moreover, each branch we add only _adds_ to the uncertainty
and possible confusion.

The main problem here is that most coders don't follow this list and
emacs-diffs actively enough to be "in the know".  That problem cannot
be solved by procedures or by rearranging branches.

> - users should know where to get the current "stable bleeding-edge".

Same problems, for the same basic reasons.  (Also, I think "stable
bleeding-edge" is self-contradictory.)

> - "should know" means that it doesn't depend on whether we're in
>   feature-freeze, in pretest, or anything else.

That is an impossible requirement.  Even Barry's suggestion (which I
think is not right for Emacs, see below) doesn't promise that

> Currently, we don't satisfy those constraints, and Barry's suggestion
> would seem to help in this regard.

IMO, what Barry suggests cannot be done with our current resources and
level of proficiency.  Like many other similar proposals, it tries to
copy procedures from other projects, without considering the resources
each project has, relative to the project's size and the number and
interdependencies of distinct areas of expertise involved.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]