[Seaside-dev] Remaining Issues for Seaside 3.0 release

[Paolo Bonzini]

> Also I think we should go a little faster and give up on this crazy
> alpha1..n,beta1..n versioning scheme. It does not scale for us. Let's
> release 3.0 now, release 3.1 for ESUG, and 3.2 by the end of the year.
> Each increment with its own small set of valuable improvements and
> bug-fixes. Let's not strife for the "perfect" release.

Agreed.  Work out bigger features on branches, merge them when they're 
ready, release when there are no big outstanding bugs even if only one 
or two branches were merged.

Paolo