ok, no problem here.

but how we can define core part of symfony,  as I said , can be usefull to
name next releases.

On 10/2/07, Fabien POTENCIER <[EMAIL PROTECTED]> wrote:
>
>
> even and odd versions were used before the symfony 1.0 release. We don't
>   use them anymore.
>
> Fabien
>
> Bert-Jan wrote:
> >> that point exposed by Tamcy is important.
> >>
> >> When talking in a business layer with other people in any project, the
> >> linux
> >> kernel method looks good.( 2.6.20.x stable, 2.6.21.x dev( it's become a
> 22
> >> stable)  ), much more with not IT people.
> >
> > Not really on topic anymore but FYI: the even=stable/odd=unstable scheme
> > has been abandoned in the kernel about 2 years ago. That's why they've
> > built quite a lot of new stuff into it but there still isn't a 2.7.x
> > branch for development. Currently, work is being done on the 2.6.23kernel
> > and when that's released it's officially a stable version. The release
> > candidates are for development and testing.
> >
> >> Why? to a quick assign of status of development and a speed/activity
> off
> >> dev
> >> that way can be more helpfull.
> >>
> >> according with first Francois post, IMHO, the next release can be named
> >> 1.5,
> >> or better 1.9. :-D.
> >>
> >> but, Francois, usually major versions increases when core part of
> >> framework/project/wathever did a BC or change much things of first
> >> concepts
> >> of the framework, then I ask you, what we can define what is core part
> of
> >> symfony and what is not ?
> >> this can help in that kind of questions
> >>
> >>
> >
> > >
> >
> >
>
> >
>


-- 
Lucas Stephanou

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"symfony developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/symfony-devs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to