[Squeakfoundation]Re: release prioritization (was "ClassBuilder problem")

Daniel Vainsencher danielv at netvision.net.il
Fri Feb 28 22:13:28 UTC 2003

Actually, I think it would require some changes, if only because the
process of making a release would need to be automated to the point that
it doesn't take too much time. But Doug is more qualified to answer


Simon Michael <simon at joyful.com> wrote:
> Daniel Vainsencher <danielv at netvision.net.il> writes:
> > If we have bugs (and we have more than just those handful that were
> > mentioned), the solution isn't to delay the release, it is to have SUnit
> > tests, use them, and keep them green. Think longer term - it's not about
> > making a perfect release - that'll always be a good excuse to delay a
> > little more. It's about having many releases, at quite frequent,
> > predictable intervals, that are getting better and better, and keeping
> > production and development close. That'll give us long term properties
> > that will keep Squeak getting better.
> +1, well said.
> I've found releasing on the first of every month to be a useful discipline.
> What changes would be needed to make this practical for squeak, I wonder ?
> Maybe none.
> Thanks for your work, guides.
> -Simon
> _______________________________________________
> Squeakfoundation mailing list
> Squeakfoundation at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/listinfo/squeakfoundation

More information about the Squeak-dev mailing list