On Mon, Oct 17, 2016 at 2:15 PM, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote:
> On 2016-10-17 11:33, Erik Bray wrote:
>> I'm mostly just talking about a policy that generates a (rough)
>> release schedule.
> Which problems would that solve? I don't really see the problem with the
> current "release whenever it's done" way of doing things, where "whenever
> it's done" is largely arbitrary.
I mostly brought this up in the first place just because I was
confused about how milestones are being used (they aren't). It would
be nice if they were used more as intended though.
What problems does it solve? First of all, I already mentioned
one--nobody but the "release manager" knows when a release is expected
to come out, or what the purpose of that release is, and what one can
expect to be in it. That's a problem in of itself. How do you
communicate to users how often/when they can expect releases? How,
also, do you communicate that to developers? How is one supposed to
know the urgency of an issue if one doesn't know the release schedule?
That's just the actual schedule though. Really that's not my chief
concern (though it would be good to have). More broadly, a lack of
development formality here leads to various other unnecessary
complications and difficulties. I could go on and on here, but you
wouldn't be hearing anything new from me...
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.