Issue 124418 - Add Target Milestone version item "4.1.1" for "AOO Trunk"
Summary: Add Target Milestone version item "4.1.1" for "AOO Trunk"
Status: CLOSED FIXED_WITHOUT_CODE
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: Bugzilla (show other issues)
Version: current
Hardware: All All
: P3 Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-13 16:27 UTC by Rainer Bielefeld
Modified: 2016-04-07 08:44 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Rainer Bielefeld 2014-03-13 16:27:02 UTC 
We now have AOO 4.1.0 Beta, so that the existing "4.1.0" TM will indicate that fixes with that TM will be in AOO 4.1.0 final.

But Fixes in Trunk for bugs without showstopper status will not be integrated into Branch 4.1.0. So we need an additional TM for these fixes in Trunk what will be available for AOO 4.0.1

Suggestion for new TM item: "4.0.1"
Comment 1 Rainer Bielefeld 2014-03-13 16:28:14 UTC 
Oops!

Suggestion of course: "4.1.1"
Comment 2 Oliver-Rainer Wittmann 2014-03-14 08:13:22 UTC 
I have already made a similar proposal on our mailing list - see http://markmail.org/thread/i4ovypklgjt5fpnc

Regarding new Target Milestone '4.1.1' my opinion is:
- This target milestone is needed once we know that we will release a 4.1.1.
- A possible 4.1.1 release will be made on branch AOO410 from my point of view as a micro release's purpose is to fix serious and critical issues showing up in the last made release. For me current trunk is more or less the code line for the next minor (or major) release.
just my 2cents.
Comment 3 Rainer Bielefeld 2014-03-17 08:57:29 UTC 
Fixed by new TM 4.2.0