Hi,
The Einstein Toolkit has releases every six months or so which are tested and tagged so that people can download a working version. However, some things change (for example machine configurations and directory locations) which mean that the old releases don't work any more.
How should we solve this problem? One proposal would be to check every commit and decide if it needs to be backported to old releases. This would only happen if the old release would no longer work without the commit (or maybe if the bug was very important?). How many releases should be backported to? Just the last one?
This issue is probably only really applicable to simfactory machine configurations and optionlists.
I would support only one release because we have limited manpower.
Regarding SimFactory: We could add instructions to the release note for obtaining the development version of SimFactory together with a release of the Einstein Toolkit. Preferable would probably be backporting of option lists, triggered by some automated tests that indicate failure when a system configuration changes.
-erik
On Sat, Apr 23, 2011 at 10:32 AM, Ian Hinder ian.hinder@aei.mpg.de wrote:
Hi,
The Einstein Toolkit has releases every six months or so which are tested and tagged so that people can download a working version. However, some things change (for example machine configurations and directory locations) which mean that the old releases don't work any more.
How should we solve this problem? One proposal would be to check every commit and decide if it needs to be backported to old releases. This would only happen if the old release would no longer work without the commit (or maybe if the bug was very important?). How many releases should be backported to? Just the last one?
This issue is probably only really applicable to simfactory machine configurations and optionlists.
-- Ian Hinder ian.hinder@aei.mpg.de
Users mailing list Users@einsteintoolkit.org http://lists.einsteintoolkit.org/mailman/listinfo/users
Hi,
On Sat, Apr 23, 2011 at 04:32:50PM +0200, Ian Hinder wrote:
One proposal would be to check every commit and decide if it needs to be backported to old releases. This would only happen if the old release would no longer work without the commit (or maybe if the bug was very important?).
I believe that this would be too much effort for every commit.
We don't have enough people (and interest) to do a lot of back-ports. Officially I would like to only support the current stable release. That means that important bug-fixes like especially out-dated simfactory data would be fixed in the current release; likewise for any important bugs. New features would probably always get a 'no'.
As to versions older than the current release: I don't think we will update those anymore even for those important bugs, unless there is enough interest by one of the maintainers to do the work of implementing a fix and testing it. I don't want to be in the way of someone updating older releases, but no one should expect us to have the time for that.
Frank
users@lists.einsteintoolkit.org
-
Erik Schnetter -
Frank Loeffler -
Ian Hinder