ian.hinder at aei.mpg.de
Mon Apr 8 10:27:44 CDT 2013
As we are coming up to a release, it would be a good idea to run through the tickets in TRAC and decide which ones should be addressed. As we are now in "feature-freeze", this should be limited to bug fixes only. Regressions (cases where the code used to work, and has now been broken) should have much higher priority than bugs which have been around for a while.
We track tickets relevant to the release using the TRAC "milestone" feature. You can see all the tickets with milestone ET_2013_05 at this link:
(also linked from the trac.einsteintoolkit.org under "View all open tickets concerning the next Einstein Toolkit release") .
It would be very useful for people to run through the remaining open tickets
Open tickets: https://trac.einsteintoolkit.org/query?status=%21closed&group=component&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=reporter&col=time&col=component&order=priority
and add the release milestone (ET_2013_05) to those defects that they think should be addressed for this release, especially regressions. Many thorns have a certain "maintainer" listed in the README file; those people could start with those thorns. Later on, this list might be whittled down by the release manager (Frank), but we should get an idea now of what might need to be done.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 203 bytes
Desc: Message signed with OpenPGP using GPGMail
Url : http://lists.einsteintoolkit.org/pipermail/users/attachments/20130408/b13ff97f/attachment.bin
More information about the Users