 |
 |
Hi I entered all S14 tasks we earlier discussed through the spreadsheet into jira. (for your reference the spreadsheet is attached with the corresponding jira numbers). It'd be really good if all of you could try to look, just to get familiar with jira. I am happy to carve 15-20 min at the meeting next week to walk you through various things in jira (I am still learning, but I spent many hours in jira by now, so I guess I learned a few things). We will be tracking all S14 things through jira, so there is virtually no way you could avoid using jira in the near future... We still don't have Fabrice's account there, so "his" tasks are temporarily assigned to me, I'll fix that once his account gets created. I took liberty to come up with a few "epics", and now it is time to get your opinion (including K-T's!) if that makes sense... it is basically: - hackathon - major refactoring of all qserv code (it is a big one!) - fully automated testbed - logging - configuration some tasks are not assigned to any epic. You can see all that by sorting by issue type, and tweaking which columns are displayed. Many "stories" are still at a high level, we will be adding subtasks covering actual work soon (and assigning many of them to you, as opposed to me :) Feel free to improve, tweak, add missing dependencies etc. Heads up: I am considering using jira in place of our weekly round table report (once you all get used to jira...), and use the time at meetings to focus on design topics/blockers and other things that actually need discussion for real. Jacek ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the QSERV-L list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1