Let's keep its quality then - I guess there is a big set of patches ready
for commit (that were accumulated during passed weeks of frozen code) - if
most of them are committed between two snapshot testings running by Stepan
and there will be regressions then
it will really take time to define the commit caused the regressions
which is ineffective
I do not propose any patch-committing arbitration process - just apply the
common sense: if (say) a major commit is done already today then let's wait
for Snapshot Testing results to see the effect.
Such a practice may be applied not only for "before freeze" / "after freeze"
time, but for regular development time also.
Thanks
Vova
2008/2/28, Tim Ellison <[EMAIL PROTECTED]>:
>
> Stepan Mishura wrote:
> > Thanks to everyone who invested efforts into M5 - r629320 build will
> > be promoted as M5 milestone build. So the code-base trunk is now open
> > for development.
>
> Hurray!
>
> > Well done! Thanks again to everyone!
>
> +1 -- our best build ever :-)
>
> Tim
>
