True, he very well might, but at least then we'd have documentation about what was wrong, when it was reported, whether it was resolved, and we wouldn't have to keep that information in our heads or hunt through old email looking for it. Nomi On Jun 25, 2013, at 8:33 PM, Robert Olson <[email protected]> wrote:
Not sure why he'd not ignore the ticket just like he ignored the email.
----- Original Message -----
I would make a JIRA ticket for this. This is exactly the sort of situation it's useful for--something's wrong, we need to see if it's been resolved before we do the release, without the release team having to remember exactly what the issue was and then try to figure out whether it ever got fixed.
We can even set a due date on the ticket so that JIRA will nag the person the ticket's assigned to. (We have not, so far, used that feature.)
Nomi
On Jun 25, 2013, at 3:40 PM, Robert Olson <[email protected]> wrote:
No, as far as I know the communities code has not been fixed (no reply from the mail to andreas about it).
----- Original Message -----
We really need to get the last release posted to the website.
My notes state:
DMG - missing communities_qc
VM - double gzipped, uuid needed changing
I can fix up the VM, has the DMG been fixed?
---- Daniel Murphy-Olson Systems Administrator Mathematics & Computer Science Division Argonne National Laboratory 630-252-0055