New actions are added to the minutes of the current meeting and dated using the "task list" control
Do not copy actions from previous minutes, just add bullet version to reference the source minutes
In every IISOMI meeting, check the action item list and check for tasks that have passed their due date
If the due date is past, determine if the issue is still active
If the task is active, mark the over-due task as completed, and create a new task with a new due date in the minutes
If the task is not active, (i.e. not going to be progressed at this time), simply close the task and make a note in the minutes that the task was closed.
Description
Assignee
Label(s)
Due date
Task appears on
Bernd ZeunerTo update TR-515 (Papyrus Guidelines): Sections 7.4.6 (To add how to auto resize; to add how to use the local stylesheet); 5.2 (To point to the Wiki page for the versions of Eclipse & Papyrus that IISOMI are using); 5.4 (To add the link of the gendoc download site and also the IISOMI latest releases wiki page). To update the IISOMI Tooling wiki page to add the pointers/links to the tools. To update the IISOMI Deliverables wiki page to add (as for information) the pointers/links of the available mapping tools.
Scott MansfieldAndrea Mazzini Discuss xmi2yang tooling regarding to the translation of UML stereotype «Cond» (condition) into (if/when) feature statements.
New actions are added to the minutes of the current meeting and dated using the "task list" control
Do not copy actions from previous minutes, just add bullet version to reference the source minutes
In every IISOMI meeting, check the action item list and check for tasks that have passed their due date
If the due date is past, determine if the issue is still active
If the task is active, mark the over-due task as completed, and create a new task with a new due date in the minutes
If the task is not active, (i.e. not going to be progressed at this time), simply close the task and make a note in the minutes that the task was closed.