TYPO3 Mailingliste: nicht fragen - lesen!

Franz Holzinger schrieb:
> Hello Robert,
>> I'm curious, there are new minor versions of tt_products appearing in
>> TER now and then, but often the version number does not increase. Is
>> this by purpose?
> yes, this is to make some error corrections to the current or another
> version without adding addtional new features (if possible). So you need
> to update only in case of errors listed in the ChangeLog file. Some
> persons need to get these errors corrected asap. and do not want to wait
> for the next development version.

Hi Franz,
Sorry to dig up this old thread, but with the current version scheme I'm
having difficulties of keeping track if there are new "versions"
released or not.

I'm not able to look at the TER "New and updated" regularily enough to
see if a new version has been released that might fix the one or the
other annoying bug. The bug might have been fixed, but I can't know,
because the version number stays the same. That's really annoying,
especially if you tend to keep your extensions as up-to-date as possible.

Can't you, say, increase the sub-sub-version number (2.5.X) with every
bug fixing release and the sub-version number (2.X.2) with every feature
addition release?

Cheers,
Ro
_______________________________________________
TYPO3-project-tt-products mailing list
TYPO3-project-tt-products (AT) lists...netfielders.de
http://lists.netfielders.de/cgi-bin/...ct-tt-products

Hello Robert,

> Sorry to dig up this old thread, but with the current version scheme I'm
> having difficulties of keeping track if there are new "versions"
> released or not.
>
> I'm not able to look at the TER "New and updated" regularily enough to
> see if a new version has been released that might fix the one or the
> other annoying bug. The bug might have been fixed, but I can't know,
> because the version number stays the same. That's really annoying,
> especially if you tend to keep your extensions as up-to-date as possible.
>
> Can't you, say, increase the sub-sub-version number (2.5.X) with every
> bug fixing release and the sub-version number (2.X.2) with every feature
> addition release?

I think it would not help to have so many version numbers. It is not
possible any more to remove a not good working extension from TER.
Therefore the former version must be overridden with the same version
number. I would need an additional number at the end. 2.5.2,X, because
it is still a 2.5.2 but with only small bug fixes. The first number is
the compatibility number 2. So we would have only the second number to
discern. But then we could not discern between big and small code
changes. Therefore a forth number would be needed for this.

You shall use the SVN
http://typo3xdev.svn.sourceforge.net...roducts/trunk/
and not look into the TER.

This will give you the latest patches and info in the ChangeLog.

- Franz
_______________________________________________
TYPO3-project-tt-products mailing list
TYPO3-project-tt-products (AT) lists...netfielders.de
http://lists.netfielders.de/cgi-bin/...ct-tt-products