[Users] Einstein Toolkit Meeting
knarf at cct.lsu.edu
Sun Feb 10 10:37:27 CST 2013
Please consider joining the weekly Einstein Toolkit phone call at
10 am US central time on Mondays. As usual, you can find instructions
how to join on the following web site:
I short: the number is (+1) 225-578-4942 or (+1) 866-573-0359 and
the conference id is 118682#.
Remember that today (Feb 10th), network connections to LSU might be
interrupted due to upgrades happening at LSU. This includes almost every
ET service, but should be finished by tomorrow.
Proposed, new thorns start to accumulate in
The meeting might be a good place to present/discuss these new thorns.
The current list is:
Also, backporting was an issue on the mailing list recently, mainly
because we tend to do this more often than in recent years.
The current status is:
- There is one development branch where most of the development is
supposed to be happening. This is not guaranteed to be stable, but
some effort in that direction should be visible.
- There might be separate development branches for features that are too
disruptive, even for the development branch. They should be
short-lived and be merged back as soon as possible.
- There are release branches. These received some care and testing and
are updated if major bugs are found.
- There have been (but are not for recent releases) release tags -
tagging specific versions of a release branch. This was used in the
beginning of the ET, but because we hardly ever changed the release
branch their usage was discontinued. This could of course be changed
again. Users should not checkout using the tags, as these will (of
course) not receive any fixes.
- There was the question of how to find out exactly which version
someone is using (keeping in mind that release branches are not a
fixed code base). It was proposed to add an option to GetComponents
which could list the revisions of all components and possibly even
creating a hash of all of them. This could be compared with 'known
versions' and would give some measure to get to this information. No
patch was proposed yet to my knowledge. It would also be nice if such
an option could detect any local changes/commits and flag them or
possibly even create a patch.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 836 bytes
Desc: Digital signature
Url : http://lists.einsteintoolkit.org/pipermail/users/attachments/20130210/0818b68f/attachment.bin
More information about the Users