[Bf-committers] call for test build 2
mein at cs.umn.edu
Wed Apr 2 17:20:41 CEST 2008
In reply to Tom M (letterrip at gmail.com):
> Well the current plan is a release by between mid April and the end of
> April, that will give time to fix the remaining issues that are felt
> to be 'critical'. Brecht said it will take roughly two weeks to get
> the point cache issue ready to go. Then there is also the work of
> getting the rest of the particle system back up to full functionality,
> and getting the UV editing back to its 2.50 functionality.
> Once the bug tracker either 'hits 50' or gets down to what is agreed
> to be an acceptable level then we can do a release.
Not trying to fight. ;)
It sounds like were not ready for release yet, just looking for bugs to
fix but also trying to get the bugs below 50. (Again it sort of sounds
like we do not know what we are doing....)
I have two recommendations:
The first is when we call a release build from now on we should specify
the name to use: blender-2.46-test2-(platform) or blender-2.46-RC1-(platform)
And everyone should stick with the name given. Pretty much every RC
we have had different names and its a pain in the butt. Some people
do rc1 some do RC1, some add the - some don't.... In general I've
been fixing them up by hand after the fact, but its a lot of work
for pretty much nothing.
The second is we pick a name and stick with it, we have been doing
blender-(VERSION)-RC1, RC2 etc... so I'd say stick with that, even
if this release isn't quite the same as others. Honestly every
release is different some fix bugs, some add lots of new features,
some shouldn't have been maybe, and some are the best thing since sliced
bread. All software development deals with these issues.
Lets pick something and stick with it.
mein at cs.umn.edu
More information about the Bf-committers