[Framework-Team] release schedule / phone conference

[alan runyan]

> I am +0 on this. In my experience, there is *no* way to plan 
> a release in detail. As all development is volunteer-driven, 
> you have to release what you have got come the time. So, if, 
> say, people go to the effort of organizing an AJAX sprint and 
> produce great results, do we really want to have their work 
> sit around for a year?

This is true.  I think the problem is ensuring that we do not repeat another
Christian Heimes and ATCT.  Where he and others get something done and now
its sort of in limbo.  We need *at the least* a champion to push it through.

 
> Stefan
> 
> 
> On 1. Nov 2005, at 22:03, whit wrote:
> 
> > Alternating UI/Feature releases and Infrastructure Improvement
> > Release:
> >
> > One of the ideas that came up in our conversation was that 
> there was 
> > significant value to alternating major release between User 
> Focus and 
> > Infrastructure Focus.  In this scenario, plone 2.2 would be 
> the first 
> > infrastructure release, plone 2.3 would be the first UI release.
> >
> > There are a number of benefits to this. It clarifies what we our  
> > focus is and gives the community a clear idea of what to expect.   
> > It makes us think in longer timeframes than the next 
> release, and does 
> > the needful in providing lead time for marketting and 
> eating our peas 
> > and carrot with our stack.
> >
> > I encourage list lurkers to give input.  right now the FWT core is
> > +1 on this and will push it out to plone-devel.
> 
> --
> Anything that happens, happens.  --Douglas Adams
> 
> 
> _______________________________________________
> Framework-Team mailing list
> Framework-Team at lists.plone.org
> http://lists.plone.org/mailman/listinfo/framework-team
>