On Fri, 15 Jun 2012, Raphael Hertzog wrote:
On Fri, 15 Jun 2012, Ariel wrote:
In any case, changing the version that Wordpress advertises is IMO a
serious risk of breaking random plugins that verify the current
version...
Not the internal version number, which would have this risk. The
number displayed in the html. No plugin checks that, nothing checks
that except spammers and google.
If I follow you, we should drop that field instead of updating it...
I guess that's your choice.
Updating it without changing the internal version number is more
work than just changing the internal version number. And I really
prefer to avoid divergence with upstream.
I wonder if upstream would be willing to include a local suffix option for
us.
But wouldn't dropping the field be an equal diversion to hardcoding
-debian in it? (Dynamic based on the actual debian localpart would be
better, but just -debian would do the job.)
BTW, it's not true that all the issues are closed in a timely fashion
in Debian stable. If you noticed, we had to jump from 3.0.5 to 3.3.2
to fix most of the security issues because it's next to impossible to
backport the relevant security fixes.
I guess that's why google stopped emailing me :)
-Ariel
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
