Page 1 of 1

Non working versions and update packages

Posted: Tue Nov 12, 2013 6:45 pm
by Per Yngve Berg
When there is a non working version like the 2.5.15, why is there no update-package from 2.5.14->2.5.16 that most users will need as their will jump over the bogus 2.5.15 version? Those that have already installed 2.5.15, can still use the 2.5.14->2.5.15 package.

Re: Non working versions and update packages

Posted: Fri Nov 15, 2013 4:48 am
by mbabker
We only post update packages for the latest release in a series and one that will work for all releases in a series. In the case of 2.5, the Joomla_2.5.x_to_2.5.16 package covers all 2.5 releases and the Joomla_2.5.15_to_2.5.16 package is specific to 2.5.15. This was a deliberate decision so that we aren't posting packages covering every possible upgrade.

Re: Non working versions and update packages

Posted: Fri Nov 15, 2013 4:29 pm
by Per Yngve Berg
That not what I mean. The update to 2.5.15 may block further updates and the user cannot proceed. Is best to remove it and replace with a 2.5.14->2.5.16. This is only cases where two releases comes within a few days.

Re: Non working versions and update packages

Posted: Fri Nov 15, 2013 10:33 pm
by mbabker
And that's when you use the 2.5.X to 2.5.16 package. As I said before, that package covers all updates for the 2.5 series. Users updating via the update component will always get the 2.5.X to 2.5.16 package, the 2.5.15 to 2.5.16 package will only be deliberately used by individuals downloading that package, and given a couple of the issues addressed in 2.5.15 and the fact it was downloaded over 12,000 times before 2.5.16 was posted, it is just as important that they are supported.

Everyone has an upgrade path as described here. In reality, what you're describing all boils down to visuals (2.5.14 to 2.5.16 versus 2.5.X to 2.5.16) and the size of the package.