Changes between Version 51 and Version 52 of RoadMap
- Timestamp:
- Nov 5, 2016, 3:25:24 AM (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
RoadMap
v51 v52 31 31 32 32 - Milestones corresponding to //stable// releases: 33 - [milestone:0.12] -- the previous major release (June 2010), which we're going to support for the foreseeable future (it has earned the **LTS** label, Long Term Support release) 34 - [milestone:0.12.4] -- the next maintenance release for 0.12.x 33 - [milestone:0.12] -- the June 2010 release, which we're going to support for the foreseeable future (it has earned the **LTS** label, Long Term Support release) 35 34 - [milestone:next-minor-0.12.x] -- pool of tickets relevant for one of the upcoming minor maintenance releases for 0.12.x 36 - [milestone:1.0] -- the latest major release (July 2012)35 - [milestone:1.0] -- the July 2012 release 37 36 - [milestone:next-stable-1.0.x] -- pool of tickets relevant for one of the next minor maintenance releases for 1.0.x 38 - [milestone:1.2] -- the upcoming major release (May or July 2015) 37 - [milestone:1.2] -- the latest major release (November 2016) 38 - [milestone:next-stable-1.2.x] -- pool of tickets relevant for one of the next minor maintenance releases for 1.2.x 39 39 - Milestones corresponding to **development** releases: 40 - [milestone:next-dev-1. 1.x] -- pool of tickets relevant for one of the next minor feature releases,41 - starting with [milestone:1.1.1] which w ill bereleased shortly after [milestone:1.0], with features which couldn't have make it for 1.040 - [milestone:next-dev-1.3.x] -- pool of tickets relevant for one of the next minor feature releases, 41 - starting with [milestone:1.1.1] which was released shortly after [milestone:1.0], with features which couldn't have make it for 1.0 42 42 - [milestone:next-major-releases] -- pool of tickets relevant for one of the next next major feature releases 43 43 … … 46 46 - **[milestone:1.0]** 47 47 - [milestone:1.0.1] -> [milestone:1.0.2] -> ... -> [milestone:next-stable-1.0.x] 48 - [milestone:1.1.1] -> [milestone:1.1.2] -> ... -> [milestone:next-dev-1.1.x]48 - [milestone:1.1.1] -> [milestone:1.1.2] -> ... 49 49 - **[milestone:1.2]** 50 50 - [milestone:1.2.1] -> [milestone:1.2.2] -> ... -> [milestone:next-stable-1.2.x] … … 70 70 - from there (or directly if the triager is also the developer going to fix it), a developer eventually picks it and moves it to the current **1.0.x** minor stable release; factors that influence this selection are the impact of the issue (severity), but also how well the defect is explained and documented, if there's a patch provided or not, etc. 71 71 - the later we are in a stable cycle (//1.0.4//, //1.0.5//, ...), the more unlikely the defect will be fixed part of that cycle, if it's not a critical defect or a security issue 72 - if it's a proposed feature and we like it, or a minor defect we'll take care to fix one day, the ticket goes into the **[milestone:next-major-releases]** pool (mid or long-term) or **[milestone:next-dev-1. 1.x]** (short-term)72 - if it's a proposed feature and we like it, or a minor defect we'll take care to fix one day, the ticket goes into the **[milestone:next-major-releases]** pool (mid or long-term) or **[milestone:next-dev-1.3.x]** (short-term) 73 73 - from there, a developer eventually picks it and moves it to the current **1.1.x** minor development release, when there's some actual code ahead 74 74 - if we don't really like the proposed feature, or think the reported defect is not worth fixing, but we're not strongly opposed to it either, the ticket becomes [milestone:unscheduled]; it may eventually move from there to a more concrete milestone depending on the involvement of contributors