Re: Typo3 version number for wheezy
On 2012-11-09 13:34, Christian Welzel wrote:
Am 09.11.2012 13:48, schrieb Jonathan Wiltshire:
currently TYPO3 4.5.19+dfsg1-2 is in testing. A security bulletin
was published yesterday and i prepared a new version of the
package.
I want to name it 4.5.19+dfsg1-2+wheezy1 because i hope this is the
version that goes into wheezy and want to communicate, that this is
not the vanilla upstream package.
Is this version ok for you?
Unofficial NACK; the same version is in sid and wheezy, so the
correct
version is either 4.5.19+dfsg1-3 or 4.5.19+dfsg2-1, however you want
to
express best the modification, and targetting sid. Alternatively
persuade upstream to make a proper minimal release with an
incremented
version.
The latest official release of TYPO3 4.5 branch is 4.5.21 which
contains
other bugfixes too (4.5.20 was skipped because of the freeze). So
when i
name it 4.5.19+dfsg1-3, it will enter wheezy by this version number,
and
peoeple could think, it is a security buggy version. But this new
version contains the bugfixes backported from 4.5.21. And this is not
really expressed by "4.5.19+dfsg1-3".
I fail to see how '+wheezy1' communicates this any better. Release
extensions are for squeezing versions in between suites. In either of
these cases the user is still going to have to inspect the package to
see what changed.
You could add a NEWS entry detailing it, but that's likely to be noise
for the majority of users.
After the freeze i can upload 4.5.21 or later to unstable and all
will
be ok. I dont believe, that a complete new version 4.5.21 will get a
freeze exception, will it?
Not unless it is purely RC-bug fixes, no.
--
Jonathan Wiltshire jmw@debian.org
Debian Developer http://people.debian.org/~jmw
4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51
<directhex> i have six years of solaris sysadmin experience, from
8->10. i am well qualified to say it is made from bonghits
layered on top of bonghits
Reply to: