Hi Tristan, Version numbers ARE marketing. Even if that marketing targets technical people. It is the very first indicator of maturity (but hehe, you should keep your promises here). The difference between version numbers is an indicator for change. And, as said also for compatibility indication. But if you are not tapestry, then you might manage to do a major version number without rewriting the whole api.
If you are really just interested in the technical numbering a build or revision number might be enough for you. Hey its symfony r8343! Doesn't sound exiting? For me +1.5 for 1.5! .: Fabian -----Original Message----- From: [EMAIL PROTECTED] om [mailto:[EMAIL PROTECTED] groups.com] On Behalf Of Tristan Rivoallan Sent: Mittwoch, 26. September 2007 15:37 To: [email protected] Subject: [symfony-devs] Re: Should symfony 1.1 be called symfony 2.0? 2007/9/26, Jo <[EMAIL PROTECTED]>: > I don't see any reason not to call it symfony 1.1. > It is the next release and one (big) step ahead. > > Calling it symfony 1.5 or 2.0 I would wonder if > I've missed the last releases and what happend > between release 1.0 and 1.5 (or 2.0). > > Does symfony really need marketing by release > numbers? +1. If we really want to do release marketing, then call it Symfony Millenium. Otherwise, keep a normal numbering scheme seems better to me. the linux kernel will not even go beyond 2.6 ... we want people to be attracted by framework's technical quality right ? a consistent numbering scheme is part of software component's quality 2 cents ++ tristan --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
