RE: [SMARTY] new versions and quality
| From: | SavaJr | Date: | Tue, 11 Feb 2003 23:02:41 +0000 |
| Subject: | RE: [SMARTY] new versions and quality | ||
| References: | 1 | Groups: | php.smarty.general |
| Request: | Send a blank email to php-smarty-general+get-7663@lists.php.net to get a copy of this message | ||
Boљtjan,
Possibly it makes sense just freeze with that version if you experience
incompartinbility with next ones?
But I'm agree with more detailed changes list from version to version or
some sort of incompartibility list.
It can be made like sort of Wiki.
---------------
Ruslan Savchyshyn
http://www.MagneticOne.com/
Web development and design services
-----Original Message-----
From: Boљtjan Ћokљ [mailto:bostjan.zoks@uni-mb.si]
Sent: Wednesday, February 12, 2003 12:47 AM
To: smarty-general@lists.php.net
Subject: [SMARTY] new versions and quality
Hi!
I wonder why dev-team doesn't feature-freeze some version and just
bugfix it before next release (using RCs or odd/even versioning
schemes).
Why? I started using Smarty at 2.3.0. Next version (2.3.1) worked great,
upgrade was smooth (no changes in templates/code necessary).
Right now I still can't upgrade to 2.4.*. Many people report template
incompatibilites, not-that-small bugs,... Don't get me wrong - I prefer
strict typing, but - I think we are missing a document or manual topic
saying something about "how to upgrade your templates" or "what YOU have
to change for new version to work". With "diff" through docs it isn't
that easy to find changes in a way Smarty operates in current version.
So... can please someone write such a document, so I will be able to
upgrade without rereading whole manual to "detect" necessary template
changes? I'm sure dev-team has all this in their heads...
Best regards,
Bostjan