Milestone releases had lots of unfinished *new* functionality, as we
only guaranteed that the *existing* functionality is working. Same
thing here, only the scope of unfinished functionality is limited to
the Modeler. We define what Milestone vs. Beta vs. RC means, and
historically the meaning has been what I just mentioned. Don't see any
problem with this approach going forward, as long as we explain the
rules to the users.
Also the downside of NOT declaring Beta until we reach some ideal
state throughout the board, is that the feature creep will continue,
and it will be hard to stop it.
Andrus
On Oct 8, 2009, at 9:39 PM, Andrey Razumovsky wrote:
Traditionally we don't freeze the Modeler in Beta, as officially
Modeler
code is a black box to the users. It is frozen for stability
reasons at the
next stage - RC (release candidate), so this one won't get in the
way.
Yes but release is sort of product, so I'd prefer it would not have
half-finished functionality. There's not that much to finish anyways
--
Andrey
