[Seaside-dev] Remaining Issues for Seaside 3.0 release

[Julian Fitzell]

Yup. And maybe we could actually pick one (or two) major features as goals
for each release. When that (plus any low hanging fruit we come across in
the process) is done: release!

I have a few ideas and we should get a discussion going shortly, but agreed:
for now we need to get a release out last week. :)

Julian

On Thu, Apr 15, 2010 at 8:44 AM, Paolo Bonzini <bonzini at gnu.org> wrote:

>
>  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
>
> _______________________________________________
> seaside-dev mailing list
> seaside-dev at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside-dev/attachments/20100415/70413235/attachment.htm