> On 17/10/2016, at 22:42, Erik Bray <erik.m.b...@gmail.com> wrote:
> On Mon, Oct 17, 2016 at 11:39 AM, Francois Bissey
> <francois.bis...@canterbury.ac.nz> wrote:
>>> On 17/10/2016, at 22:33, Erik Bray <erik.m.b...@gmail.com> wrote:
>>> My point is, as it is I see no way to divine when or why a Sage
>>> release is coming out.
>> Release early, release often. In my experience in the last 8 years,
>> especially release often - it has slowed down a bit, but it is still
>> often by any means.
> I'm afraid that's just not very useful--it's a platitude. It's
> especially made worse by the lack of maintenance branches and patch
> releases. I agree patch releases should be frequent. For a project
> like sage feature releases should be fairly frequent too, but with
> care not break compatibility.
Platitude or not, that’s the reality I have been experiencing.
Maintenance branch (or LTS release) have been brought up before,
usually by people coding for a living, but it never got anywhere.
I am fairly certain that it is a factor in said people getting less
active over time.
To move to the kind of release schedule you are talking about
we’ll need a new release manager who has the vision for this kind
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
To post to this group, send email to firstname.lastname@example.org.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.