[TYPO3-dev] Extension versioning scheme - example ve_guestbook
Jigal van Hemert
jigal at xs4all.nl
Wed Jun 17 09:46:12 CEST 2009
Marcus Krause wrote:
> If a recent bulletin/advisory states that versions 2.7.1 and below of
> your extension are vulnerable, 2.7.2 is the new secure one and you want
> to fix a bug in this current version 2.7.2, it's certainly not a good
> idea to do following:
> * upload version 2.6.0 and overwrite a previous version
> * upload version 2.6.1
> * upload version 2.6.2
> within a couple of minutes.
To me it seems as if the developer had some problems getting the version
right. It sure doesn't help that ext_emconf.php states in its header:
"version" and "dependencies" must not be touched!
Did you contact the author to hear the reason and/or to help him with
this? I tried a quick search for any clues how to properly increase the
version myself, but other than a few patches which change the version in
emconf I didn't find anything (which doesn't mean that there is no
information).
So how does one properly set a version?
> I'd expect version 2.7.3. But, you know, I got used to it - thanks to
> powermail.
You sound frustrated. Maybe it's just (another) bad day for you, but I
think it would be more helpful if such an event would result in an
educational posting about version numbers in the extension, TER and SVN
instead of ... ehmm... this.
Regards,
--
Jigal van Hemert.
More information about the TYPO3-dev
mailing list