Extra meeting 10.1.2012 - Revision history

Tuukka Lehtonen at 20:29, 6 September 2012

2012-09-06T20:29:50Z

← Older revision		Revision as of 20:29, 6 September 2012
Line 1:		Line 1:
	[[Category:Meetings]]		[[Category:Meetings]]
	{{nav\|prev=Regular meeting 9.1.2012\|up=Platform development process\|next=Extra meeting 16.1.2012}}		{{nav\|prev=Regular meeting 9.1.2012\|up=Platform development process\|next=Extra meeting 17.1.2012}}
	== Agenda ==		== Agenda ==

Tuukka Lehtonen: /* Minutes */

2012-02-01T18:41:30Z

Minutes

← Older revision		Revision as of 18:41, 1 February 2012
Line 35:		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.

	:See [[Simantics 1.6]]		:See [[Simantics 1.6]] and [[Stable Branch]]

	;2. Planning of sprint 2012-1		;2. Planning of sprint 2012-1

Tuukka Lehtonen: /* Minutes */

2012-01-11T10:03:06Z

Minutes

← Older revision		Revision as of 10:03, 11 January 2012
Line 27:		Line 27:
	;Rationale: Improve trackability of repository changes. Facilitate generation of release notes for Simantics platform releases.		;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. ([[~~redmine~~:~~issues/~~3076]])		§ 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.		;Rationale: Less noise for application developers.

Tuukka Lehtonen: /* Minutes */

2012-01-10T23:51:32Z

Minutes

← Older revision		Revision as of 23:51, 10 January 2012
Line 27:		Line 27:
	;Rationale: Improve trackability of repository changes. Facilitate generation of release notes for Simantics platform releases.		;Rationale: Improve trackability of repository changes. Facilitate generation of release notes for Simantics platform releases.

	§ ~~([[redmine:issues/3076]])~~ 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. ([[redmine:issues/3076]])

	;Rationale: Less noise for application developers.		;Rationale: Less noise for application developers.

Tuukka Lehtonen: /* Minutes */

2012-01-10T23:50:57Z

Minutes

← Older revision		Revision as of 23:50, 10 January 2012
Line 27:		Line 27:
	;Rationale: Improve trackability of repository changes. Facilitate generation of release notes for Simantics platform releases.		;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.		§ ([[redmine:issues/3076]]) Stable branch is created ASAP. First official stable commit is done at the beginning of sprint 2012-2 after testing.

	;Rationale: Less noise for application developers.		;Rationale: Less noise for application developers.
	~~:See [[redmine:issues/3076]]~~

	§ 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.

Tuukka Lehtonen: /* Minutes */

2012-01-10T23:50:28Z

Minutes

← Older revision		Revision as of 23:50, 10 January 2012
Line 30:		Line 30:

	;Rationale: Less noise for application developers.		;Rationale: Less noise for application developers.
			:See [[redmine:issues/3076]]

	§ 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.

Tuukka Lehtonen at 21:37, 10 January 2012

2012-01-10T21:37:05Z

← Older revision		Revision as of 21:37, 10 January 2012
Line 1:		Line 1:
	[[Category:Meetings]]		[[Category:Meetings]]
			{{nav\|prev=Regular meeting 9.1.2012\|up=Platform development process\|next=Extra meeting 16.1.2012}}
	== Agenda ==		== Agenda ==

Tuukka Lehtonen at 21:11, 10 January 2012

2012-01-10T21:11:33Z

← Older revision		Revision as of 21:11, 10 January 2012
Line 1:		Line 1:
			[[Category:Meetings]]
	== Agenda ==		== Agenda ==

Tuukka Lehtonen: /* Minutes */

2012-01-10T18:31:25Z

Minutes

← Older revision		Revision as of 18:31, 10 January 2012
Line 19:		Line 19:
	== 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.
Line 33:		Line 33:
	§ 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.

	;See [[Simantics 1.6]]		:See [[Simantics 1.6]]

	2. Planning of sprint 2012-1		;2. Planning of sprint 2012-1

	§ Start to use only one backlog for Simantics platform.		§ Start to use only one backlog for Simantics platform.
Line 42:		Line 42:


	3. Survey of development areas		;3. Survey of development areas

	* Scrum and SVN process		* Scrum and SVN process
Line 100:		Line 100:
	§ 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.		§ 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		;4. Release 1.8 content planning

	Not discussed.		Not discussed.

	5. Other issues		;5. Other issues

	Next meeting Monday 16.1 @ 9.30		Next meeting Monday 16.1 @ 9.30

Tuukka Lehtonen: /* Minutes */

2012-01-10T18:30:22Z

Minutes

← Older revision		Revision as of 18:30, 10 January 2012
Line 32:		Line 32:

	§ 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.

			;See [[Simantics 1.6]]

	2. Planning of sprint 2012-1		2. Planning of sprint 2012-1