Difference between revisions of "Extra meeting 10.1.2012"
| (18 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| + | [[Category:Meetings]] | ||
| + | {{nav|prev=Regular meeting 9.1.2012|up=Platform development process|next=Extra meeting 17.1.2012}} | ||
== Agenda == | == Agenda == | ||
| Line 19: | Line 21: | ||
== Minutes == | == Minutes == | ||
| − | 1. SVN and Scrum practices aftermath | + | ;1. SVN and Scrum practices aftermath |
§ Simantics SVN repository commit messages are prevalidated to contain at least one reference to a story in Simantics Platform Backlog. Tuukka notifies all parties using email. | § Simantics SVN repository commit messages are prevalidated to contain at least one reference to a story in Simantics Platform Backlog. Tuukka notifies all parties using email. | ||
| − | § Stable branch is created ASAP. First official stable commit is done at the beginning of sprint 2012-2 after testing. | + | ;Rationale: Improve trackability of repository changes. Facilitate generation of release notes for Simantics platform releases. |
| + | |||
| + | § Stable branch is created ASAP. First official stable commit is done at the beginning of sprint 2012-2 after testing. ([[issue:3076]]) | ||
| + | |||
| + | ;Rationale: Less noise for application developers. | ||
§ Jani Simomaa takes responsibility of automatic testing of Simantics platform. Support of automatic tests is provided for trunk and stable branches. Regression and others - suites are maintained for automatic testing. In regression suite all tests must pass and others contains all other test cases. | § Jani Simomaa takes responsibility of automatic testing of Simantics platform. Support of automatic tests is provided for trunk and stable branches. Regression and others - suites are maintained for automatic testing. In regression suite all tests must pass and others contains all other test cases. | ||
| Line 29: | Line 35: | ||
§ A wiki page for stable branch releases contains a list of completed stories from Redmine. The page is a responsibility of Tuukka. With all stories a description is attached. The description is taken from 'Description' field in the story. | § A wiki page for stable branch releases contains a list of completed stories from Redmine. The page is a responsibility of Tuukka. With all stories a description is attached. The description is taken from 'Description' field in the story. | ||
| − | 2. Planning of sprint 2012-1 | + | :See [[Simantics 1.6]] and [[Stable Branch]] |
| + | |||
| + | ;2. Planning of sprint 2012-1 | ||
| + | |||
| + | § Start to use only one backlog for Simantics platform. | ||
| + | § Quadruple story point resolution at the same time as in Apros. | ||
| − | 3. Survey of development areas | + | ;3. Survey of development areas |
* Scrum and SVN process | * Scrum and SVN process | ||
| Line 40: | Line 51: | ||
** ConsistsOf | ** ConsistsOf | ||
** Export/import | ** Export/import | ||
| + | ** Adapters vs. SCL values | ||
* SCL | * SCL | ||
** Function library design and development rules | ** Function library design and development rules | ||
| Line 47: | Line 59: | ||
** Interface cleanup and improvements | ** Interface cleanup and improvements | ||
** Implementation improvements | ** Implementation improvements | ||
| + | ** Persistent requests | ||
| + | ** Documentation | ||
* Variable | * Variable | ||
** Inteface improvements | ** Inteface improvements | ||
| Line 57: | Line 71: | ||
** Interfaces | ** Interfaces | ||
** Interplay with Variable | ** Interplay with Variable | ||
| + | * Commands | ||
| + | * Sheets | ||
* Structural | * Structural | ||
** Interface variables | ** Interface variables | ||
| Line 84: | Line 100: | ||
** Migration support? | ** Migration support? | ||
| − | 4. Release 1.8 content planning | + | § Organize previous list into a table into the next meeting minutes and all attendants prioritize the table before the meeting using priorities 1,2,3, lowest is the most important. |
| + | |||
| + | ;4. Release 1.8 content planning | ||
| + | |||
| + | Not discussed. | ||
| + | |||
| + | ;5. Other issues | ||
| − | + | Next meeting Monday 16.1 @ 9.30 | |
Latest revision as of 20:29, 6 September 2012
| Previous | Up | Next |
Agenda
1. SVN and Scrum practices aftermath
Timetables, SVN, backlogs, testing
2. Planning of sprint 2012-1
3. Survey of development areas
Create a list of most important epic stories in Simantics development.
4. Release 1.8 content planning
Start the discussion about the contents of 1.8
5. Other issues
Minutes
- 1. SVN and Scrum practices aftermath
§ Simantics SVN repository commit messages are prevalidated to contain at least one reference to a story in Simantics Platform Backlog. Tuukka notifies all parties using email.
- Rationale
- Improve trackability of repository changes. Facilitate generation of release notes for Simantics platform releases.
§ Stable branch is created ASAP. First official stable commit is done at the beginning of sprint 2012-2 after testing. (issue:3076)
- Rationale
- Less noise for application developers.
§ Jani Simomaa takes responsibility of automatic testing of Simantics platform. Support of automatic tests is provided for trunk and stable branches. Regression and others - suites are maintained for automatic testing. In regression suite all tests must pass and others contains all other test cases.
§ A wiki page for stable branch releases contains a list of completed stories from Redmine. The page is a responsibility of Tuukka. With all stories a description is attached. The description is taken from 'Description' field in the story.
- See Simantics 1.6 and Stable Branch
- 2. Planning of sprint 2012-1
§ Start to use only one backlog for Simantics platform.
§ Quadruple story point resolution at the same time as in Apros.
- 3. Survey of development areas
- Scrum and SVN process
- Layer0
- Inverses
- ConsistsOf
- Export/import
- Adapters vs. SCL values
- SCL
- Function library design and development rules
- Contexts in getRelatedValue2
- Technical details on using ReadGraph and indices
- DB client
- Interface cleanup and improvements
- Implementation improvements
- Persistent requests
- Documentation
- Variable
- Inteface improvements
- Standard property specification
- Standard implementation of graph-based variables
- Standard implementation of simulator variables?
- Modelled Selection view
- Model improvement
- Experiment control
- Interfaces
- Interplay with Variable
- Commands
- Sheets
- Structural
- Interface variables
- Standard implementation?
- Scenegraph
- Loaders
- Refactoring needs
- Diagram
- 3D
- Documents
- Views
- Diagram
- Refactoring towards Scenegraph
- Layers
- Testing
- Mapping framework
- SCL-based definition
- Testing
- Increasing automatic testing
- Squish
- Team features
- Implementation strategy
- Migration
- Tool development
- IDE integration
- SCL support
- Migration support?
§ Organize previous list into a table into the next meeting minutes and all attendants prioritize the table before the meeting using priorities 1,2,3, lowest is the most important.
- 4. Release 1.8 content planning
Not discussed.
- 5. Other issues
Next meeting Monday 16.1 @ 9.30
