Re: [SMARTY] new versions and quality
| From: | Monte Ohrt | Date: | Tue, 11 Feb 2003 23:32:25 +0000 |
| Subject: | Re: [SMARTY] new versions and quality | ||
| References: | 1 | Groups: | php.smarty.general |
| Request: | Send a blank email to php-smarty-general+get-7664@lists.php.net to get a copy of this message | ||
2.4.0 is a feature release, and 2.4.1, 2.4.2 are fixing issues found
within 2.4.0. That is typically how the cycle works, we release one when
CVS seems stable enough to do so. As for things not working or used to
work but now don't, those are largely getting discovered as more and
more people are using the releases, especially people using Smarty in
wasy it wasn't really meant for. The CVS version is always there for
anyone to test and report problems, but this doesn't mean all the
problems will be found before a release. I would think that is because
there just isn't a big enough bed of testers to find all the problems.
We could go to an RC scheme if that deems to be a more understandable
approach, I'm open to suggestions.
How to upgrade: delete all compiled and cached templates, replace the
new library files and all should be well. Problems that have been
encountered have been fixed, those can be seen in the change log (NEWS).
The only outstanding "problem" that I know of is variable catenation,
which has never been supported by Smarty but there are claims that it
worked in older releases which is purely accidental because of unstrict
syntax checking. If you really need it, you will have to either not
upgrade, make modifiers to work around it, or wait until Smarty supports
it which is not currently planned.
Monte
On Tue, 2003-02-11 at 16:47, Boštjan Žokš wrote:
> 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
>
--
Monte Ohrt <monte@ispi.net>