Yocto 2.3 Schedule - Revision history

Stephen K. Jolley at 18:27, 13 February 2017

2017-02-13T18:27:37Z

← Older revision		Revision as of 18:27, 13 February 2017
Line 89:		Line 89:
	* M3 release: 3/10/17		* M3 release: 3/10/17

	== M4 (Feb. 27, 2017 to ~~April 28~~, 2017 -- 8 weeks: planning done in week 1, bug fixes 2-4, stabilization week 5-7, release week 8) ==		== M4 (Feb. 27, 2017 to May 5, 2017 -- 9 weeks: planning done in week 1, bug fixes 2-5, stabilization week 6-8, release week 9) ==
	=== M4 Bug/fix Cutoff is April 3, 2017 ===		=== M4 Bug/fix Cutoff is April 10, 2017 ===

	{{#bugzilla:		{{#bugzilla:
Line 113:		Line 113:
	=== M4 Stabilize schedule ===		=== M4 Stabilize schedule ===
	'''Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)'''		'''Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)'''
	* RC1: 4/3/17		* RC1: 4/10/17
	* RC2: 4/10/17		* RC2: 4/17/17
	* RC3: 4/17/17		* RC3: 4/24/17
	* M4 release: 4/28/17		* M4 release: 5/5/17

	== Yocto Project 2.3 release unscheduled features/tasks list==		== Yocto Project 2.3 release unscheduled features/tasks list==

Stephen K. Jolley at 17:05, 4 November 2016

2016-11-04T17:05:32Z

← Older revision		Revision as of 17:05, 4 November 2016
Line 1:		Line 1:
	= Yocto Project 2.3 release milestone structure =		= Yocto Project 2.3 release milestone structure =
	[[File: YP1.3milestone.png]]		[[File: YP1.3milestone.png]]

			= =

	= Yocto Project 2.3 release schedule (release date: April 28, 2017) =		= Yocto Project 2.3 release schedule (release date: April 28, 2017) =

Stephen K. Jolley at 17:41, 24 October 2016

2016-10-24T17:41:37Z

← Older revision		Revision as of 17:41, 24 October 2016
Line 8:		Line 8:
	Please note that the estimation for each feature is done based on 'perfect day'. The purpose of the estimation is to estimate the relative size of features, NOT to predict when a single feature could be done.		Please note that the estimation for each feature is done based on 'perfect day'. The purpose of the estimation is to estimate the relative size of features, NOT to predict when a single feature could be done.

	== M1 (Oct. 31, 2016 to ~~TBD~~ -- 8? weeks: planning done in week 1, development week 2-5, stabilization week 6-7, release week 8) ==		== M1 (Oct. 31, 2016 to Dec. 23, 2016 -- 9 weeks: planning done in week 1, development week 2-6, stabilization week 7-8, release week 9) ==
	=== M1 Feature/Tasks Development / Cutoff is ~~TBD~~ ===		=== M1 Feature/Tasks Development / Cutoff is Dec. 12, 2016 ===

	{{#bugzilla:		{{#bugzilla:
Line 31:		Line 31:
	=== M1 Stabilize schedule ===		=== M1 Stabilize schedule ===
	'''Release Candidate and Milestone Release schedule'''		'''Release Candidate and Milestone Release schedule'''
	* RC1: ~~TBD~~		* RC1: 12/12/16
	* RC2: TBD		* M1 release: 12/23/16
	* M1 release: ~~TBD~~

	== M2 (~~TBD~~ to ~~TBD~~ -- 7? weeks: planning done in week 1, development week 2-4, stabilization week 5-6, release: week 7) ==		== M2 (Dec. 12, 2016 to Feb. 3, 2017 -- 9 weeks: planning done in week 1, development week 2-6, stabilization week 7-8, release: week 9) ==
	=== M2 Feature/tasks Development / Cutoff is ~~TBD~~ ===		=== M2 Feature/tasks Development / Cutoff is Jan. 23, 2017 ===

	{{#bugzilla:		{{#bugzilla:
Line 59:		Line 58:
	=== M2 Stabilize schedule ===		=== M2 Stabilize schedule ===
	'''Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)'''		'''Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)'''
	* RC1: ~~TBD~~		* RC1: 1/23/17
	* RC2: TBD		* M2 release: 2/3/17
	* M2 release: ~~TBD~~

	== M3 (~~TBD~~ to ~~TBD~~ -- 8? weeks: planning done in week 1, development week 2-5, stabilization week 6-7, release: week 8) ==		== M3 (Jan. 23, 2017 to Mar. 10, 2017 -- 8 weeks: planning done in week 1, development week 2-5, stabilization week 6-7, release: week 8) ==
	=== M3 Feature/tasks Development / Cutoff is ~~TBD~~ ===		=== M3 Feature/tasks Development / Cutoff is Feb. 27, 2017 ===
	{{#bugzilla:		{{#bugzilla:
	\|columns=id,from,to,estimated,summary,severity,priority,whiteboard,status		\|columns=id,from,to,estimated,summary,severity,priority,whiteboard,status
Line 86:		Line 84:
	=== M3 Stabilize schedule ===		=== M3 Stabilize schedule ===
	'''Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)'''		'''Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)'''
	* RC1: ~~TBD~~		* RC1: 2/27/17
	* RC2: TBD		* M3 release: 3/10/17
	* M3 release: ~~TBD~~

	== M4 (~~TBD~~ to 4/28/2017 -- 9? weeks: planning done in week 1, bug fixes 2-4, stabilization week 5-8, release week 9) ==		== M4 (Feb. 27, 2017 to April 28, 2017 -- 8 weeks: planning done in week 1, bug fixes 2-4, stabilization week 5-7, release week 8) ==
	=== M4 Bug/fix Cutoff is ~~TBD~~ ===		=== M4 Bug/fix Cutoff is April 3, 2017 ===

	{{#bugzilla:		{{#bugzilla:
Line 114:		Line 111:
	=== M4 Stabilize schedule ===		=== M4 Stabilize schedule ===
	'''Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)'''		'''Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)'''
	* RC1: ~~TBD~~		* RC1: 4/3/17
	* RC2: ~~TBD~~		* RC2: 4/10/17
	* RC3: ~~TBD~~		* RC3: 4/17/17
	* RC4: TBD
	* M4 release: 4/28/17		* M4 release: 4/28/17

Stephen K. Jolley: Created page with "= Yocto Project 2.3 release milestone structure = File: YP1.3milestone.png = Yocto Project 2.3 release schedule (release date: April 28, 2017) = ---- The detailed milest..."

2016-10-12T21:01:44Z

Created page with "= Yocto Project 2.3 release milestone structure = File: YP1.3milestone.png = Yocto Project 2.3 release schedule (release date: April 28, 2017) = ---- The detailed milest..."

New page

= Yocto Project 2.3 release milestone structure =
[[File: YP1.3milestone.png]]

= Yocto Project 2.3 release schedule (release date: April 28, 2017) =
----
The detailed milestone map for the 2.3 release of Yocto Project is as below. <br/><br/>
To view the Yocto schedule-at-a-glance, go to [[YoctoCalendar]]. <br/><br/>
Please note that the estimation for each feature is done based on 'perfect day'. The purpose of the estimation is to estimate the relative size of features, NOT to predict when a single feature could be done.

== M1 (Oct. 31, 2016 to TBD -- 8? weeks: planning done in week 1, development week 2-5, stabilization week 6-7, release week 8) ==
=== M1 Feature/Tasks Development / Cutoff is TBD ===

{{#bugzilla:
|columns=id,from,to,estimated,summary,severity,priority,whiteboard,status
|total=estimated
|milestone=2.3 M1
|severity=enhancement
|sort=to,priority
}}

=== M1 Bugs ===

{{#bugzilla:
|columns=id,from,to,estimated,summary,severity,priority,whiteboard,status
|total=estimated
|milestone=2.3 M1
|severity=!enhancement
|sort=to,priority
}}

=== M1 Stabilize schedule ===
'''Release Candidate and Milestone Release schedule'''
* RC1: TBD
* RC2: TBD
* M1 release: TBD

== M2 (TBD to TBD -- 7? weeks: planning done in week 1, development week 2-4, stabilization week 5-6, release: week 7) ==
=== M2 Feature/tasks Development / Cutoff is TBD ===

{{#bugzilla:
|columns=id,from,to,estimated,summary,severity,priority,whiteboard,status
|total=estimated
|milestone=2.3 M2
|severity=enhancement
|sort=to,priority
}}

=== M2 Bugs ===

{{#bugzilla:
|columns=id,from,to,estimated,summary,severity,priority,whiteboard,status
|total=estimated
|milestone=2.3 M2
|severity=!enhancement
|sort=to,priority
}}

=== M2 Stabilize schedule ===
'''Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)'''
* RC1: TBD
* RC2: TBD
* M2 release: TBD

== M3 (TBD to TBD -- 8? weeks: planning done in week 1, development week 2-5, stabilization week 6-7, release: week 8) ==
=== M3 Feature/tasks Development / Cutoff is TBD ===
{{#bugzilla:
|columns=id,from,to,estimated,summary,severity,priority,whiteboard,status
|total=estimated
|milestone=2.3 M3
|severity=enhancement
|sort=to,priority
}}

=== M3 Bugs ===

{{#bugzilla:
|columns=id,from,to,estimated,summary,severity,priority,whiteboard,status
|total=estimated
|milestone=2.3 M3
|severity=!enhancement
|sort=to,priority
}}

=== M3 Stabilize schedule ===
'''Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)'''
* RC1: TBD
* RC2: TBD
* M3 release: TBD

== M4 (TBD to 4/28/2017 -- 9? weeks: planning done in week 1, bug fixes 2-4, stabilization week 5-8, release week 9) ==
=== M4 Bug/fix Cutoff is TBD ===

{{#bugzilla:
|columns=id,from,to,estimated,summary,severity,priority,whiteboard,status
|total=estimated
|milestone=2.3 M4
|severity=enhancement
|sort=to,priority
}}

=== M4 Bugs ===

{{#bugzilla:
|columns=id,from,to,estimated,summary,severity,priority,whiteboard,status
|total=estimated
|milestone=2.3 M4
|severity=!enhancement
|sort=to,priority
}}

=== M4 Stabilize schedule ===
'''Release Candidate and Milestone Release schedule (Full Pass QA test follows every RC build)'''
* RC1: TBD
* RC2: TBD
* RC3: TBD
* RC4: TBD
* M4 release: 4/28/17

== Yocto Project 2.3 release unscheduled features/tasks list==
These features/tasks are planned for 2.3, but have not been scheduled to any specific milestone. As we move forward, more of these will be scheduled into each milestone, especially during milestone planning for each milestone above.
{{#bugzilla:
|columns=id,to,estimated,summary,severity,priority,milestone,whiteboard,status,
|milestone=2.3
|sort=to
|priority=high
|status=!(resolved,verified,closed)
}}

{{#bugzilla:
|columns=id,to,estimated,summary,severity,priority,milestone,whiteboard,status,
|milestone=2.3
|sort=to
|priority=medium%2B
|status=!(resolved,verified,closed)
}}

{{#bugzilla:
|columns=id,to,estimated,summary,severity,priority,milestone,whiteboard,status,
|milestone=2.3
|sort=to
|priority=medium
|status=!(resolved,verified,closed)
}}

{{#bugzilla:
|columns=id,to,estimated,summary,severity,priority,milestone,whiteboard,status,
|milestone=2.3
|sort=to
|priority=low
|status=!(resolved,verified,closed)
}}