[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: New JIRA for SCA-Policy TC
All, OSOA JIRA that we use for tracking our issues is going away end of this month. OASIS now has its own JIRA. I have requested the TC Admin to provide us with a JIRA project in the OASIS instance. Going forward we'll use OASIS JIRA to track our issues. Please **DO NOT** update the OSOA JIRA. There is a lot of history documented in OSOA JIRA. To preserve that I have uploaded the dump of our OSOA JIRA project in various formats: http://www.oasis-open.org/apps/org/workgroup/sca-policy/download.php/45072/SCA-Policy_TC_OSOA_JIRA.xml http://www.oasis-open.org/apps/org/workgroup/sca-policy/download.php/45070/SCA-Policy_TC_OSOA_JIRA.html http://www.oasis-open.org/apps/org/workgroup/sca-policy/download.php/45070/SCA-Policy_TC_OSOA_JIRA.html Sorry for the internal links, the public links seem to take time to appear. When OASIS JIRA is available to us, I'll migrate all our existing OSOA new/open/deferred issues to the new instance. There are 2 deferred right now. If we can figure out how to do a migration of ALL issues, we will do that too. Anish is looking into this for SCA-J TC and I plan to follow his lead if he can find a solution. Right now, it doesn't look possible. If there are any JIRA experts that might want to help Anish, please speak up. Thanks. Dave Booz STSM, BPM and SCA Architecture Co-Chair OASIS SCA-Policy TC and SCA-J TC "Distributed objects first, then world hunger" Poughkeepsie, NY (845)-435-6093 or 8-295-6093 e-mail:booz@us.ibm.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]