Issue 125155 - add entry for 4.1.1 in version and latest confirmation fields
Summary: add entry for 4.1.1 in version and latest confirmation fields
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:
Depends on:
Reported: 2014-06-25 10:17 UTC by mroe
Modified: 2014-09-01 12:06 UTC (History)
2 users (show)

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


Note You need to log in before you can comment on or make changes to this issue.
Description mroe 2014-06-25 10:17:05 UTC
For testing the milestones to AOO 4.1.1 please add an entry for this version in version and latest confirmation fields.
Comment 1 jsc 2014-07-01 07:00:13 UTC
we haven't released 4.1.1 yet, this fields make no sense for now.
Comment 2 mroe 2014-07-01 08:37:12 UTC
I don't understand this argument.
Is 4.2.0-dev released?
Is it not interesting for developers if we find bugs in the milestones which maybe different from 4.1.0?
Comment 3 jsc 2014-07-01 08:41:09 UTC
it is useful of course but then be precise and request 4.1.1-dev or whatever but 4.1.1 makes no sense.

Useful is as well to verify new uncomfirmed issues
Comment 4 mroe 2014-07-01 08:56:35 UTC
Because 4.1.1 seems to be a fixed version number there is no need for a 4.1.1-dev IMHO.

Bugs in 4.1.1 milestones will be fixed until 4.1.1 release or will stay in 4.1.1 so the version number is right. Isn't it?
Comment 5 Andrea Pescetti 2014-09-01 12:06:28 UTC
Well, now 4.1.1 is out, so the discussion on whether tagging issues with "4.1.1" before 4.1.1 is released is no longer needed.

4.1.1 is now available for the version field (see dev list, "We need some BZ changes now that 4.1.1. is out") but still needs to be added to the "Latest confirmation" field.

It would be nice, by the way, to document somewhere what must be done to add a version properly to Bugzilla.