On Friday, 5 June 2015 at 14:11:06 UTC, Steven Schveighoffer
wrote:
On 6/5/15 1:53 AM, Andrei Alexandrescu wrote:
Rust will do it:
http://opensource.com/business/15/6/rust-6-week-release-cycle
Would be so nice if we had the resources to do that. There
have been a
couple of initiatives in the past, but the folks who wanted to
do the
release just got busy with other things.
I am fine with putting a time limit on adding features, but I'd
rather release based on minimized regressions.
We have to get better as a group with insisting to use
release/stable branches.
Do we have a plan written somewhere of how we want to do
branching? I know we did some this last release cycle, but I
don't remember it being formally written.
-Steve
I agree that releases could sometimes be more frequent. However,
to release for the sake of releasing is not a good idea, in my
opinion (that is based on bad experience). Maybe Rust will do it,
because they still have so much stuff to fix, dunno. D is more
mature and fixes/improvements have to be pondered on and tested
thoroughly. High quality releases you can rely on are more
important than frequent releases. I use Manjaro Linux (ArchLinux
based) at home and I appreciate their efforts to test things
thoroughly before passing possibly buggy things on to users. If
certain bug fixes are a priority for a given project, I'd
recommend offering nightly (or weekly) builds with a
well-documented change log.
