|Re: Babel Language Packs R0.11.0 are now available! [message #1087861 is a reply to message #1073537]
||Fri, 16 August 2013 07:40
| Dirk Fauth
Registered: July 2012
may I raise a question? Why is the version number included in the official current update site URL? And why is the update site URL for the previous version invalid after the update. IMHO this causes some issues:
1. You can not check for updates, because the 0.10 update site does not know about an update to 0.11. And isn't this the idea of update sites that you can simply update?
2. When you update the current version and archive the old ones, the previous update site URL gets invalid. This causes serious issues in the build process when using Tycho against a target platform. We added the Babel plugins for version 0.10 to our update site. With the release of 0.11 our build process broke because the official update site URL changed and the 0.10 update site couldn't be retrieved anymore.
I know a lot of projects are adding the version number to the update site. In NatTable we also have that. Are updates only intended to be done within one version? It would make sense this way to ensure that the target platform really doesn't change and always the same version of a plugin is used and not updated automatically. So point 1. is more a question on how to do it right in specifying an update site. In NatTable we recently created a new update site for a bugfix version, which IMHO is not the right way, because people don't get the update automatically but need to change their target platform. But for feature or major releases it might make sense.
The second issue with replacing the update site with a new URL is quite annoying for automated builds. At least when the previous update site URL is not valid anymore. Or is it really intended that everyone needs to update their target platforms when a project they reference release an update? Why is it necessary to change the old update sites to the archive ones?
Powered by FUDForum
. Page generated in 0.09137 seconds