[Bf-committers] Proposal for 2.36 release

[Ted Schundler]

While shorter releases isn't a bad idea, I don't know that it's a
solution to the issue at hand.

I think Bart's on the right track with official release candidate
versions - publicized and posted on b3d.o, Elysiun, etc., not buried
in the b.o forums. For a normal user, trying out a beta or test
version is sort of shaky business (if they even find it). But a
Release Candidate means it's effectively ready to go. And if it's
listed on an official download page, it looks a lot safer to try out.

To be safe with the official release, rather than release when it
seems good, wait for X there being no new significant bug reports for
X days or something. Then that RC becomes the release.

Ted


On Sun, 21 Nov 2004 14:02:25 -0800, Patrick Mullen <saluk64007 at gmail.com> wrote:
> Yes I think shorter releases would be a very big improvement!  With
> the long cycles, people expect to see a lot of improvement, because
> they haven't seen a release for a long time.  Then they get
> dissapointed when the thing they wanted isn't there yet, etc.  Shorter
> releases, with more publicitiy about testing, could make the community
> feel a bit more involved?
> 
> 
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at projects.blender.org
> http://projects.blender.org/mailman/listinfo/bf-committers
>