[Bf-committers] release status update
Markus Schulz
schulz at alpharesearch.de
Sun Mar 23 18:06:22 CET 2008
I think it would be good to call it beta while still fixing features and
adding features from tracker and provide public test builds... and RC
only to fix little bugs, but no feature change at all (treat it like it
would have been released already). Alpha would be the trunk after a
release until the first beta (new features freeze) I guess...
Markus
----
Generally alpha software is tested by developers only, while beta
software is distributed for community testing.
However, if the pre-release version is for an existing software package
(e.g. version 2.5), then an "a" or "alpha" may be appended to the
version number. So the alpha version of the 2.5 release might be
identified as 2.5a or 2.5.a. Software packages which are soon to be
released as a particular version may carry that version tag followed by
"rc-#", indicating the number of the release candidate. When the version
is actually released, the "rc" tag disappears.
http://en.wikipedia.org/wiki/Software_versioning#Pre-release_versions
> what about alpha/beta ?
>
> On Sun, Mar 23, 2008 at 4:13 PM, Stephen Swaney <sswaney at centurytel.net> wrote:
>
>> On Sat, Mar 22, 2008 at 04:56:55PM -0800, Tom M wrote:
>> >
>> > For whatever reason RC naming scheme has been used for Blender test
>> > builds for builds that should more correctly be called tech preview
>> > and testing builds (I have argued against the RC naming method in the
>> > past for what it is worth..). Yes there is still work that is yet to
>> > be finished before a real release can be done.
>>
>> Bjornmose has a point. The phrase "Release Candidate" already has
>> a common meaning of "this is pretty much what you are going to get".
>> Our RCs are not that yet for the reasons already pointed out.
>>
>> Yes, changing the naming to something like Tech Preview or Test Builds
>> will be swimming uphill, but worth doing. Already on IRC, people have
>> made the argument that we cannot change something because we are doing
>> Release Candidates. I have no doubt the users are even more confused.
>>
>> The sooner we clear this up, the better.
>>
>> S.
>> --
>> Stephen Swaney
>> sswaney at centurytel.net
>>
>>
>>
>> _______________________________________________
>> Bf-committers mailing list
>> Bf-committers at blender.org
>> http://lists.blender.org/mailman/listinfo/bf-committers
>>
>>
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
>
>
More information about the Bf-committers
mailing list