incubator-ooo-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 118596] New: Side effect of closure @openoffice.org mailing list in Bugzilla
Date Fri, 11 Nov 2011 13:18:17 GMT
https://issues.apache.org/ooo/show_bug.cgi?id=118596

             Bug #: 118596
        Issue Type: DEFECT
           Summary: Side effect of closure @openoffice.org mailing list in
                    Bugzilla
    Classification: Infrastructure
           Product: www
           Version: current
          Platform: PC
        OS/Version: Windows 7
            Status: NEW
          Severity: enhancement
          Priority: P5
         Component: openoffice.org Bugzilla
        AssignedTo: issues@openoffice.org
        ReportedBy: r4zoli@openoffice.org
                CC: ooo-issues@incubator.apache.org


The closure of all mailing list running on openoffice.org discussed on
ooo-dev@i.a.o list.
One side effect will be default assignee in Bugzilla, who is responsible for
the bug will be abandoned. Every Product has own default assignee, such as for
this bug is: issues@openoffice.org. Other examples
writerneedsconfirm@openoffice.org, dbaneedconfirme@openoffice.org.

In past they used as a waiting list, until the developers appointed, not spam
all developers mailing lists, possibly used inside sun/oracle.
Usually when QA reviewed bug, assigned developer, or if the bug not confirmed
the default mail used as sink.   

I have no knowledge where these mails posted now. 
They needs to substituted until the closure happens.

Possible solution use ooo-issues mailing list instead cc-ing.

Another problem could be the already assigned bugs, where @openoffice.org email
addresses used.

-- 
Configure bugmail: https://issues.apache.org/ooo/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

Mime
View raw message