You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openoffice.apache.org by bu...@apache.org on 2014/06/25 12:17:05 UTC

[Issue 125155] New: add entry for 4.1.1 in version and latest confirmation fields

https://issues.apache.org/ooo/show_bug.cgi?id=125155

          Issue ID: 125155
        Issue Type: TASK
           Summary: add entry for 4.1.1 in version and latest confirmation
                    fields
           Product: Infrastructure
           Version: current
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: Bugzilla
          Assignee: issues@openoffice.apache.org
          Reporter: mroe.nospam@gmx.net

For testing the milestones to AOO 4.1.1 please add an entry for this version in
version and latest confirmation fields.

-- 
You are receiving this mail because:
You are the assignee for the issue.
You are watching all issue changes.

[Issue 125155] add entry for 4.1.1 in version and latest confirmation fields

Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=125155

jsc@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jsc@apache.org

--- Comment #1 from jsc@apache.org ---
we haven't released 4.1.1 yet, this fields make no sense for now.

-- 
You are receiving this mail because:
You are the assignee for the issue.
You are watching all issue changes.

[Issue 125155] add entry for 4.1.1 in version and latest confirmation fields

Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=125155

--- Comment #4 from mroe <mr...@gmx.net> ---
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?

-- 
You are receiving this mail because:
You are the assignee for the issue.
You are watching all issue changes.

[Issue 125155] add entry for 4.1.1 in version and latest confirmation fields

Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=125155

Andrea Pescetti <pe...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |CONFIRMED
                 CC|                            |pescetti@apache.org
     Ever confirmed|0                           |1

--- Comment #5 from Andrea Pescetti <pe...@apache.org> ---
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.

-- 
You are receiving this mail because:
You are the assignee for the issue.
You are watching all issue changes.

[Issue 125155] add entry for 4.1.1 in version and latest confirmation fields

Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=125155

--- Comment #3 from jsc@apache.org ---
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

-- 
You are receiving this mail because:
You are the assignee for the issue.
You are watching all issue changes.

[Issue 125155] add entry for 4.1.1 in version and latest confirmation fields

Posted by bu...@apache.org.
https://issues.apache.org/ooo/show_bug.cgi?id=125155

--- Comment #2 from mroe <mr...@gmx.net> ---
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?

-- 
You are receiving this mail because:
You are the assignee for the issue.
You are watching all issue changes.