[Jani Taskinen <[EMAIL PROTECTED]>] > [this is more php-dev stuff, thus moved there] > > Warning: > > This is yet another beaten up issue but as it still hasn't > been fixed, we need to find a solution to fix it. > > > Problems: > > Viability, BBC, WTFF, old extensions used with new PHP version. > > > Proposals: > > My proposal is that first we come up with a versioning scheme > with which everybody can agree on. Then we can release this > scheme to 'public' and hopefully not have to discuss/fight > about this again. > > > Examples: > > >http://java.sun.com/products/jdk/1.2/docs/guide/versioning/spec/VersioningSpecification.html > http://java.sun.com/j2se/1.3/docs/guide/extensions/versioning.html > http://www.zenspider.com/ZSS/Definitions/Versions.html > > (the last one is something that I'd like to see for PHP) > > > Also, to make NEWS file more useful than it is now I (again) > propose that it is reorganized like this: > > Categories: > > ! Important note > * Changed > + Added > - Removed > > > Reasoning: > > There has to be clear document that describes when and why a version > number changes. If someone doesn't understand WHY this document is > needed they should read the rest of this email. :) > > > --Jani > > p.s. Rest can be safely ignored. It is just there to show what happens > everytime this issue raises it's ugly head and shouts: "BOO!".. Take a look at http://cvs.php.net/co.php/pearweb/sql/design.txt. There's a versioning section at the end there, intended for PEAR. Anything we can use? - Stig -- Stig Sæther Bakken <[EMAIL PROTECTED]> Fast Search & Transfer ASA, Trondheim, Norway -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] To contact the list administrators, e-mail: [EMAIL PROTECTED]
