Simple Machines > News and Updates
SMF 2.0.2 and 1.1.16 critical security patches released
K@:
--- Quote from: 青山 素子 on June 20, 2012, 05:58:24 PM ---
The first part of my response was concerning K@ directing users to use the update archive as a package manager package, which will not work.
--- End quote ---
Actually, updates do (At least, they always have, for me). UpGRADES don't.
--- Quote from: Nodaz on June 20, 2012, 06:18:34 PM ---i went to browse packagse, it was there, i clicked on it and it installed fine...
--- End quote ---
WoOt!
Kindred:
why would there be a 2.0.3 or 1.1.17 if there are no security issues to patch?
Antes:
--- Quote from: Kindred on June 21, 2012, 08:53:36 AM ---why would there be a 2.0.3 or 1.1.17 if there are no security issues to patch?
--- End quote ---
So you prefer saying we fixed that glitch/bug whatever but included in next big version? If you fixed some bugs in 2.0.x circle you have to make new release. If I'm not wrong there is already 33 bugs (public) resolved/closed. Its enough to release another update.
Arantor:
That isn't how it works, that's never been how it works in the 9 year history of SMF.
Once a x.y.0 release is made (like 2.0.0), the ONLY things fixed after are security fixes. There have been no security issues fixed, ergo no new release.
It isn't about whether you'd 'prefer' it or not, it's how SMF development operates - keeping life easier for users and admins to manage upgrades.
You see, by that logic, you could release a new patch every single bug fix, which means we'd be up to 2.0.34 by now - and no-one needs that.
Antes:
Things can be changed nothing stands against it.
I didn't say release new update after every single bug/glitch fix. I said X is a good number to release update.
Living with "bugs" never made users life easier.
Beside all I'm completely happy with no-new release (that means there is no security issue in software)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version