Re: [Phpgroupware-developers] porting to proposal-branch

[Dan Kuykendall]

Kai Hofmann wrote:

> > I think we should get 16 out, work hard on making head 18, a 
> > well tested
> > 18.001 should become 1.0 
> >    
>
> I think we should skip head - make 1.0 from 0.16 and start from scratch with
> the new framework as 2.0
>  
I liked this idea initially as well. However there is a good argument to 
be made for putting the HEAD code out there as a migration step. Basicly 
take my new XSLT solution and get it ported into HEAD and allow 
developers to start moving over the UI layer.
After that step, porting to the new framework will be alot easier.

As far as jumping right to the new framework, that would cut down the 
time to release for the new code and therefore put us back into a 
leadership position all the faster.

At this point I can still go either way. I think the new framework is a 
quantum leap in performance and implementation from the current HEAD 
code and would give the project a better solution for our future needs. 
This is really probably going to come down to the developers. The 
direction each chooses to put their contributions into will factor in 
very heavily. If developers want to continue on the HEAD code, that is 
what will florish. If they prefer the new code Ive been building with 
Jengo, then that it what will florish.

Dan