Hi Geoffrey, thanks for uploading the report. Were you also planning on uploading the reports from the previous months? I've just read through the current one, and found it very interesting. For example, just this week, we also discovered the issue with SSM cancel. Due to travel, I've had to miss a couple of ASG weekly calls, and reading through the reports might bring me back up to speed on Sirocco's status... ---- unrelated --- Regarding bugs/issues with shared components: for aesop and triton, there is already a trac system for tracking bug reports. Is there something similar for SSM? Right now, it seems that each team independently has to stumble upon issues and bugs in SSM... (not implying that there are any ;-) ) Dries
Hi Dries, There are no previous reports, NNSA does not require that level of oversight. We have started doing monthly reports in order to better communicate with our remote team mates (you). I think your discovery with respect to cancel highlights why we should have been doing this all along :( --Lee On Aug 3, 2012, at 9:04 AM, Dries Kimpe wrote:
Hi Geoffrey,
thanks for uploading the report. Were you also planning on uploading the reports from the previous months?
I've just read through the current one, and found it very interesting. For example, just this week, we also discovered the issue with SSM cancel.
Due to travel, I've had to miss a couple of ASG weekly calls, and reading through the reports might bring me back up to speed on Sirocco's status...
---- unrelated ---
Regarding bugs/issues with shared components: for aesop and triton, there is already a trac system for tracking bug reports. Is there something similar for SSM?
Right now, it seems that each team independently has to stumble upon issues and bugs in SSM... (not implying that there are any ;-) )
Dries _______________________________________________ ASG mailing list [email protected] https://lists.mcs.anl.gov/mailman/listinfo/asg
participants (3)
-
Dries Kimpe -
Ward, Lee -
Wiki update: Asg-private: Gcdanie