Difference between revisions of "Extra meeting 10.1.2012"
| Line 22: | Line 22: | ||
§ 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. | § Stable branch is created ASAP. First official stable commit is done at the beginning of sprint 2012-2 after testing. | ||
| + | |||
§ 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. | ||
| + | |||
§ 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. | ||
Revision as of 08:10, 10 January 2012
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.
§ Stable branch is created ASAP. First official stable commit is done at the beginning of sprint 2012-2 after testing.
§ 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.
2. Planning of sprint 2012-1
3. Survey of development areas
- Scrum and SVN process
- Layer0
- Inverses
- ConsistsOf
- Export/import
- 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
- 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
- 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?
4. Release 1.8 content planning
5. Other issues
