| 2018-06-06 16:28:11 |
Dimitri John Ledkov |
bug |
|
|
added bug |
| 2018-06-06 16:28:26 |
Dimitri John Ledkov |
bug task added |
|
flufl.bounce (Ubuntu) |
|
| 2018-06-06 16:28:33 |
Dimitri John Ledkov |
bug task added |
|
flufl.i18n (Ubuntu) |
|
| 2018-06-06 16:28:41 |
Dimitri John Ledkov |
bug task added |
|
flufl.lock (Ubuntu) |
|
| 2018-06-06 16:29:27 |
Dimitri John Ledkov |
bug task added |
|
lazr.config (Ubuntu) |
|
| 2018-06-06 16:29:45 |
Dimitri John Ledkov |
bug task added |
|
lazr.delegates (Ubuntu) |
|
| 2018-06-06 18:25:24 |
Dimitri John Ledkov |
bug task added |
|
nose (Ubuntu) |
|
| 2018-06-06 18:25:32 |
Dimitri John Ledkov |
bug task added |
|
python-aiosmtpd (Ubuntu) |
|
| 2018-06-06 18:25:43 |
Dimitri John Ledkov |
bug task added |
|
python-falcon (Ubuntu) |
|
| 2018-06-06 18:25:52 |
Dimitri John Ledkov |
bug task added |
|
python-public (Ubuntu) |
|
| 2018-06-06 18:26:00 |
Dimitri John Ledkov |
bug task added |
|
zope.component (Ubuntu) |
|
| 2018-06-06 18:26:08 |
Dimitri John Ledkov |
bug task added |
|
zope.configuration (Ubuntu) |
|
| 2018-06-06 18:26:16 |
Dimitri John Ledkov |
bug task added |
|
zope.event (Ubuntu) |
|
| 2018-06-06 18:26:23 |
Dimitri John Ledkov |
bug task added |
|
zope.hookable (Ubuntu) |
|
| 2018-06-06 18:39:03 |
Dimitri John Ledkov |
description |
mailman is python2, but mailman3 is python3, but also it has new dependency stack. |
mailman is python2, but mailman3 is python3, but also it has new dependency stack.
Do we want src:mailman3 in main?
bin:mailman3 pulls in above listed dependencies? (*)
Do we want bin:mailman3 or bin:mailman3-full in main (which pulls in src:mailman-suite as well)
src:mailman-suite has potentially more things - django, hyperkitty, ruby-sass, uwsgi...
(*) and lynx, but dropped to suggests |
|
| 2018-06-06 18:40:13 |
Dimitri John Ledkov |
description |
mailman is python2, but mailman3 is python3, but also it has new dependency stack.
Do we want src:mailman3 in main?
bin:mailman3 pulls in above listed dependencies? (*)
Do we want bin:mailman3 or bin:mailman3-full in main (which pulls in src:mailman-suite as well)
src:mailman-suite has potentially more things - django, hyperkitty, ruby-sass, uwsgi...
(*) and lynx, but dropped to suggests |
mailman is python2, but mailman3 is python3, but also it has new dependency stack.
Do we want src:mailman3 in main? bin:mailman3 pulls in above listed dependencies (*)
(*) and lynx, but dropped to suggests
Do we want bin:mailman3 or bin:mailman3-full in main? (the latter pulls in src:mailman-suite as well)
src:mailman-suite has potentially more things - django, hyperkitty, ruby-sass, uwsgi...
MIRs needed for all of the above listed. |
|
| 2018-06-06 18:40:29 |
Dimitri John Ledkov |
summary |
[MIR] mailman3 to replace mailman |
[MIR] mailman3 to replace mailman, or drop mailman to universe and off server iso |
|
| 2018-06-06 18:40:37 |
Dimitri John Ledkov |
bug task added |
|
mailman (Ubuntu) |
|
| 2018-06-06 18:50:58 |
Dimitri John Ledkov |
description |
mailman is python2, but mailman3 is python3, but also it has new dependency stack.
Do we want src:mailman3 in main? bin:mailman3 pulls in above listed dependencies (*)
(*) and lynx, but dropped to suggests
Do we want bin:mailman3 or bin:mailman3-full in main? (the latter pulls in src:mailman-suite as well)
src:mailman-suite has potentially more things - django, hyperkitty, ruby-sass, uwsgi...
MIRs needed for all of the above listed. |
mailman is python2, mailman3 is python3, but also it has new dependency stack.
Do we want src:mailman3 in main? bin:mailman3 pulls in above listed dependencies (*)
(*) and lynx, but dropped to suggests
Do we want bin:mailman3 or bin:mailman3-full in main? (the latter pulls in src:mailman-suite as well)
src:mailman-suite has potentially more things - django, hyperkitty, ruby-sass, uwsgi...
MIRs needed for all of the above listed. |
|
| 2018-06-06 18:52:30 |
Dimitri John Ledkov |
description |
mailman is python2, mailman3 is python3, but also it has new dependency stack.
Do we want src:mailman3 in main? bin:mailman3 pulls in above listed dependencies (*)
(*) and lynx, but dropped to suggests
Do we want bin:mailman3 or bin:mailman3-full in main? (the latter pulls in src:mailman-suite as well)
src:mailman-suite has potentially more things - django, hyperkitty, ruby-sass, uwsgi...
MIRs needed for all of the above listed. |
mailman is python2, mailman3 is python3, but also it has new dependency stack.
Do we want src:mailman3 in main? bin:mailman3 pulls in above listed dependencies (*)
(*) and lynx, but dropped to suggests
Do we want bin:mailman3 or bin:mailman3-full in main? (the latter pulls in src:mailman-suite as well)
src:mailman-suite has potentially more things - django, hyperkitty, ruby-sass, uwsgi...
MIRs needed for all of the above listed.
Before proceeding further with assignment/doing technical work in driving above MIRs, a product level yes/no answers should probably be answered for above two questions. |
|
| 2018-06-06 21:31:50 |
Dimitri John Ledkov |
mailman3 (Ubuntu): assignee |
|
Don Bennett (dpb) |
|
| 2018-06-06 21:32:52 |
Dimitri John Ledkov |
mailman3 (Ubuntu): assignee |
Don Bennett (dpb) |
David Britton (davidpbritton) |
|
| 2018-09-11 21:08:27 |
Dimitri John Ledkov |
mailman (Ubuntu): assignee |
|
Joshua Powers (powersj) |
|
| 2018-09-13 16:06:22 |
Dimitri John Ledkov |
bug task added |
|
mailman-suite (Ubuntu) |
|
| 2018-12-04 21:36:04 |
Joshua Powers |
mailman3 (Ubuntu): assignee |
David Britton (davidpbritton) |
Christian Ehrhardt (paelzer) |
|
| 2018-12-04 21:36:16 |
Joshua Powers |
mailman (Ubuntu): assignee |
Joshua Powers (powersj) |
|
|
| 2018-12-04 21:36:21 |
Joshua Powers |
bug |
|
|
added subscriber Joshua Powers |
| 2018-12-05 13:16:01 |
Christian Ehrhardt |
attachment added |
|
dependencies if we "only" select the core mailman3 https://bugs.launchpad.net/ubuntu/+source/mailman3/+bug/1775427/+attachment/5219445/+files/mailman3-main-promotion-dependencies.txt |
|
| 2018-12-05 13:16:31 |
Christian Ehrhardt |
attachment added |
|
dependencies if we select the core mailman3-full as one might expect https://bugs.launchpad.net/ubuntu/+source/mailman3/+bug/1775427/+attachment/5219446/+files/mailman3-main-promotion-dependencies-all.txt |
|
| 2018-12-05 13:17:00 |
Christian Ehrhardt |
bug task added |
|
zope.i18nmessageid (Ubuntu) |
|
| 2018-12-05 13:20:31 |
Christian Ehrhardt |
bug task added |
|
zope.schema (Ubuntu) |
|
| 2018-12-05 14:05:38 |
Christian Ehrhardt |
attachment added |
|
dependencies for mailman3-web which is most of the superset of extra packages https://bugs.launchpad.net/ubuntu/+source/zope.schema/+bug/1775427/+attachment/5219449/+files/mailman3-main-promotion-dependencies-web.txt |
|
| 2018-12-05 14:08:19 |
Christian Ehrhardt |
attachment added |
|
hyperkitty deps on top of mailman3 and mailman3-web https://bugs.launchpad.net/ubuntu/+source/zope.schema/+bug/1775427/+attachment/5219450/+files/mailman3-main-promotion-dependencies-hyperkitty.txt |
|
| 2018-12-06 08:40:46 |
Christian Ehrhardt |
bug task deleted |
django-allauth (Ubuntu Disco) |
|
|
| 2018-12-06 08:41:20 |
Christian Ehrhardt |
bug task added |
|
django-allauth (Ubuntu) |
|
| 2019-03-13 09:38:03 |
Christian Ehrhardt |
bug task deleted |
django-allauth (Ubuntu) |
|
|
| 2019-03-13 09:38:08 |
Christian Ehrhardt |
bug task deleted |
django-filter (Ubuntu) |
|
|
| 2019-03-13 09:38:16 |
Christian Ehrhardt |
bug task deleted |
django-guardian (Ubuntu) |
|
|
| 2019-03-13 09:38:20 |
Christian Ehrhardt |
bug task deleted |
django-haystack (Ubuntu) |
|
|
| 2019-03-13 09:38:27 |
Christian Ehrhardt |
bug task deleted |
django-mailman3 (Ubuntu) |
|
|
| 2019-03-13 09:38:31 |
Christian Ehrhardt |
bug task deleted |
django-paintstore (Ubuntu) |
|
|
| 2019-03-13 09:38:35 |
Christian Ehrhardt |
bug task deleted |
django-picklefield (Ubuntu) |
|
|
| 2019-03-13 09:38:39 |
Christian Ehrhardt |
bug task deleted |
django-q (Ubuntu) |
|
|
| 2019-03-13 09:38:44 |
Christian Ehrhardt |
bug task deleted |
djangorestframework (Ubuntu) |
|
|
| 2019-03-13 09:38:48 |
Christian Ehrhardt |
bug task deleted |
flufl.bounce (Ubuntu) |
|
|
| 2019-03-13 09:38:53 |
Christian Ehrhardt |
bug task deleted |
flufl.i18n (Ubuntu) |
|
|
| 2019-03-13 09:38:58 |
Christian Ehrhardt |
bug task deleted |
flufl.lock (Ubuntu) |
|
|
| 2019-03-13 09:39:02 |
Christian Ehrhardt |
bug task deleted |
glewlwyd (Ubuntu) |
|
|
| 2019-03-13 09:39:06 |
Christian Ehrhardt |
bug task deleted |
hyperkitty (Ubuntu) |
|
|
| 2019-03-13 09:39:09 |
Christian Ehrhardt |
bug task deleted |
lazr.config (Ubuntu) |
|
|
| 2019-03-13 09:39:14 |
Christian Ehrhardt |
bug task deleted |
lazr.delegates (Ubuntu) |
|
|
| 2019-03-13 09:39:18 |
Christian Ehrhardt |
bug task deleted |
less.js (Ubuntu) |
|
|
| 2019-03-13 09:39:22 |
Christian Ehrhardt |
bug task deleted |
libjs-jquery-colorpicker (Ubuntu) |
|
|
| 2019-03-13 09:39:27 |
Christian Ehrhardt |
bug task deleted |
mailman-hyperkitty (Ubuntu) |
|
|
| 2019-03-13 09:39:35 |
Christian Ehrhardt |
bug task deleted |
mailman-suite (Ubuntu) |
|
|
| 2019-03-13 09:39:43 |
Christian Ehrhardt |
mailman3 (Ubuntu): status |
New |
In Progress |
|
| 2019-03-13 09:39:59 |
Christian Ehrhardt |
bug task deleted |
mailmanclient (Ubuntu) |
|
|
| 2019-03-13 09:40:04 |
Christian Ehrhardt |
bug task deleted |
node-amdefine (Ubuntu) |
|
|
| 2019-03-13 09:40:10 |
Christian Ehrhardt |
bug task deleted |
node-source-map (Ubuntu) |
|
|
| 2019-03-13 09:40:15 |
Christian Ehrhardt |
bug task deleted |
nose (Ubuntu) |
|
|
| 2019-03-13 09:40:20 |
Christian Ehrhardt |
bug task deleted |
postorius (Ubuntu) |
|
|
| 2019-03-13 09:40:24 |
Christian Ehrhardt |
bug task deleted |
python-aiosmtpd (Ubuntu) |
|
|
| 2019-03-13 09:40:28 |
Christian Ehrhardt |
bug task deleted |
python-blessed (Ubuntu) |
|
|
| 2019-03-13 09:40:32 |
Christian Ehrhardt |
bug task deleted |
python-csscompressor (Ubuntu) |
|
|
| 2019-03-13 09:40:36 |
Christian Ehrhardt |
bug task deleted |
python-django-compressor (Ubuntu) |
|
|
| 2019-03-13 09:40:42 |
Christian Ehrhardt |
bug task deleted |
python-django-extensions (Ubuntu) |
|
|
| 2019-03-13 09:40:47 |
Christian Ehrhardt |
bug task deleted |
python-django-gravatar2 (Ubuntu) |
|
|
| 2019-03-13 09:40:51 |
Christian Ehrhardt |
bug task deleted |
python-falcon (Ubuntu) |
|
|
| 2019-03-13 09:40:55 |
Christian Ehrhardt |
bug task deleted |
python-public (Ubuntu) |
|
|
| 2019-03-13 09:40:59 |
Christian Ehrhardt |
bug task deleted |
python-rcssmin (Ubuntu) |
|
|
| 2019-03-13 09:41:03 |
Christian Ehrhardt |
bug task deleted |
python-requests-oauthlib (Ubuntu) |
|
|
| 2019-03-13 09:41:06 |
Christian Ehrhardt |
bug task deleted |
python-rjsmin (Ubuntu) |
|
|
| 2019-03-13 09:41:11 |
Christian Ehrhardt |
bug task deleted |
python-whoosh (Ubuntu) |
|
|
| 2019-03-13 09:41:14 |
Christian Ehrhardt |
bug task deleted |
python3-openid (Ubuntu) |
|
|
| 2019-03-13 09:41:19 |
Christian Ehrhardt |
bug task deleted |
robot-detection (Ubuntu) |
|
|
| 2019-03-13 09:44:18 |
Christian Ehrhardt |
bug task deleted |
ruby-sass (Ubuntu) |
|
|
| 2019-03-13 09:44:23 |
Christian Ehrhardt |
bug task deleted |
uwsgi (Ubuntu) |
|
|
| 2019-03-13 09:44:28 |
Christian Ehrhardt |
bug task deleted |
wcwidth (Ubuntu) |
|
|
| 2019-03-13 09:44:33 |
Christian Ehrhardt |
bug task deleted |
zope.component (Ubuntu) |
|
|
| 2019-03-13 09:44:37 |
Christian Ehrhardt |
bug task deleted |
zope.configuration (Ubuntu) |
|
|
| 2019-03-13 09:44:42 |
Christian Ehrhardt |
bug task deleted |
zope.event (Ubuntu) |
|
|
| 2019-03-13 09:44:46 |
Christian Ehrhardt |
bug task deleted |
zope.hookable (Ubuntu) |
|
|
| 2019-03-13 09:44:50 |
Christian Ehrhardt |
bug task deleted |
zope.i18nmessageid (Ubuntu) |
|
|
| 2019-03-13 09:44:53 |
Christian Ehrhardt |
bug task deleted |
zope.schema (Ubuntu) |
|
|
| 2019-03-13 10:29:55 |
Christian Ehrhardt |
description |
mailman is python2, mailman3 is python3, but also it has new dependency stack.
Do we want src:mailman3 in main? bin:mailman3 pulls in above listed dependencies (*)
(*) and lynx, but dropped to suggests
Do we want bin:mailman3 or bin:mailman3-full in main? (the latter pulls in src:mailman-suite as well)
src:mailman-suite has potentially more things - django, hyperkitty, ruby-sass, uwsgi...
MIRs needed for all of the above listed.
Before proceeding further with assignment/doing technical work in driving above MIRs, a product level yes/no answers should probably be answered for above two questions. |
TODO - references to all the MIR bug - one per affected package.
---
mailman is python2, mailman3 is python3, but also it has new dependency stack due to adopting django but also splitting or rewriting a lot of its components.
Q: Do we want bin:mailman3 or bin:mailman3-full in main? (the latter pulls
in src:mailman-suite as well). src:mailman-suite has potentially more
things - django, hyperkitty, ruby-sass, uwsgi...
A: We analyzed this and we will need the full set of dependencies, even
meaning MIRs are needed for all of the above listed (and more).
Q: Before proceeding further with assignment/doing technical work in
driving above MIRs, a product level yes/no answers should probably be
answered for above two questions.
A: Discussed in several sprints now, as uncomfortable as it is we will go
through the mass-MIR processing
FYI: the paperwork for this is so massive that we prepare it as team effort in git before going to open LP bugs. If interested you can peek at:
https://git.launchpad.net/~ubuntu-server/+git/mailman3-MIR-party |
|
| 2019-03-15 10:12:15 |
Christian Ehrhardt |
description |
TODO - references to all the MIR bug - one per affected package.
---
mailman is python2, mailman3 is python3, but also it has new dependency stack due to adopting django but also splitting or rewriting a lot of its components.
Q: Do we want bin:mailman3 or bin:mailman3-full in main? (the latter pulls
in src:mailman-suite as well). src:mailman-suite has potentially more
things - django, hyperkitty, ruby-sass, uwsgi...
A: We analyzed this and we will need the full set of dependencies, even
meaning MIRs are needed for all of the above listed (and more).
Q: Before proceeding further with assignment/doing technical work in
driving above MIRs, a product level yes/no answers should probably be
answered for above two questions.
A: Discussed in several sprints now, as uncomfortable as it is we will go
through the mass-MIR processing
FYI: the paperwork for this is so massive that we prepare it as team effort in git before going to open LP bugs. If interested you can peek at:
https://git.launchpad.net/~ubuntu-server/+git/mailman3-MIR-party |
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for https://lists.canonical.com/mailman3/postorius/lists/
This source builds only docs and mailman3 itself (which provides mailman3-core).
[Rationale]
This is part of the MIR activity for all dependencies of mailman3
The "main" MIR of it is at bug 1775427:
Mailman (2) has only python2 support, but we strive for python3,
therefore Mailman3 which has python3 support should be promoted to main.
This is an evolution of the mailman2 core delivery engine of the system, but I can't guess how much it deviated so we need to recheck security (IMHO)
[Security]
No known CVEs found.
A few old issues can be found against mailman2 and one (but long fixed) for mailman 3
=> https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=mailman
[Quality assurance]
The mailman3 stacks as of now (Disco) installs fine and provides a base
config. But due to the nature of the package that needs further modification
to be of real use.
The package does in error cases ask a debconf-high question, but it is not going to be installed by default - so that is no MIR problem.
There are a few (2) Ubuntu bugs outstanding, but none of them is critical and stopping this MIR request.
There are a few (2) Debian bugs outstanding all seems to "just work" still, but when we main this in 19.10 we should at least evaluate and maybe adress this one:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921445
There are regular upstream releases and Debian packages them and fixes regularly.
No exotic HW involved.
The package ships a test suite, but it is not run at build time for upstream bug #400.
It tests things in a dep8 test thou to provide coverage.
d/watch is set up and ok.
No Lintian warning except fairly recent newer Standards version.
The package does not rely on demoted or obsolete packages.
[UI standards]
Comes with 7 translations in .po files
No End-user applications that needs a standard conformant desktop file.
[Dependencies]
Some dependencies are not in main, but we drive MIR for all related packages
that are not in main at the same time.
Please check the list of bugs from the main Mailman3 MIR in bug 1775427 to get an overview.
[Standards compliance]
The package meets the FHS and Debian Policy standards.
The packaging itself is very straight forward and uses dh_* as much as possible - the d/rules fits on one screen.
[Maintenance]
The Server team will subscribe for the package for maintenance
[Background]
The package description explains the general purpose and context of the package well.
---
TODO - references to all the related MIR bug - one per affected package.
This might sometimes be slightly out of date, to cross check and for history on all of them check git at:
https://git.launchpad.net/~ubuntu-server/+git/mailman3-MIR-party/tree/package-list.txt
---
Past Decisions in regard to this:
mailman is python2, mailman3 is python3, but also it has new dependency stack due to adopting django but also splitting or rewriting a lot of its components.
Q: Do we want bin:mailman3 or bin:mailman3-full in main? (the latter pulls
in src:mailman-suite as well). src:mailman-suite has potentially more
things - django, hyperkitty, ruby-sass, uwsgi...
A: We analyzed this and we will need the full set of dependencies, even
meaning MIRs are needed for all of the above listed (and more).
Q: Before proceeding further with assignment/doing technical work in
driving above MIRs, a product level yes/no answers should probably be
answered for above two questions.
A: Discussed in several sprints now, as uncomfortable as it is we will go
through the mass-MIR processing |
|
| 2019-03-15 10:12:29 |
Christian Ehrhardt |
bug |
|
|
added subscriber MIR approval team |
| 2019-03-15 10:19:19 |
Christian Ehrhardt |
description |
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for https://lists.canonical.com/mailman3/postorius/lists/
This source builds only docs and mailman3 itself (which provides mailman3-core).
[Rationale]
This is part of the MIR activity for all dependencies of mailman3
The "main" MIR of it is at bug 1775427:
Mailman (2) has only python2 support, but we strive for python3,
therefore Mailman3 which has python3 support should be promoted to main.
This is an evolution of the mailman2 core delivery engine of the system, but I can't guess how much it deviated so we need to recheck security (IMHO)
[Security]
No known CVEs found.
A few old issues can be found against mailman2 and one (but long fixed) for mailman 3
=> https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=mailman
[Quality assurance]
The mailman3 stacks as of now (Disco) installs fine and provides a base
config. But due to the nature of the package that needs further modification
to be of real use.
The package does in error cases ask a debconf-high question, but it is not going to be installed by default - so that is no MIR problem.
There are a few (2) Ubuntu bugs outstanding, but none of them is critical and stopping this MIR request.
There are a few (2) Debian bugs outstanding all seems to "just work" still, but when we main this in 19.10 we should at least evaluate and maybe adress this one:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921445
There are regular upstream releases and Debian packages them and fixes regularly.
No exotic HW involved.
The package ships a test suite, but it is not run at build time for upstream bug #400.
It tests things in a dep8 test thou to provide coverage.
d/watch is set up and ok.
No Lintian warning except fairly recent newer Standards version.
The package does not rely on demoted or obsolete packages.
[UI standards]
Comes with 7 translations in .po files
No End-user applications that needs a standard conformant desktop file.
[Dependencies]
Some dependencies are not in main, but we drive MIR for all related packages
that are not in main at the same time.
Please check the list of bugs from the main Mailman3 MIR in bug 1775427 to get an overview.
[Standards compliance]
The package meets the FHS and Debian Policy standards.
The packaging itself is very straight forward and uses dh_* as much as possible - the d/rules fits on one screen.
[Maintenance]
The Server team will subscribe for the package for maintenance
[Background]
The package description explains the general purpose and context of the package well.
---
TODO - references to all the related MIR bug - one per affected package.
This might sometimes be slightly out of date, to cross check and for history on all of them check git at:
https://git.launchpad.net/~ubuntu-server/+git/mailman3-MIR-party/tree/package-list.txt
---
Past Decisions in regard to this:
mailman is python2, mailman3 is python3, but also it has new dependency stack due to adopting django but also splitting or rewriting a lot of its components.
Q: Do we want bin:mailman3 or bin:mailman3-full in main? (the latter pulls
in src:mailman-suite as well). src:mailman-suite has potentially more
things - django, hyperkitty, ruby-sass, uwsgi...
A: We analyzed this and we will need the full set of dependencies, even
meaning MIRs are needed for all of the above listed (and more).
Q: Before proceeding further with assignment/doing technical work in
driving above MIRs, a product level yes/no answers should probably be
answered for above two questions.
A: Discussed in several sprints now, as uncomfortable as it is we will go
through the mass-MIR processing |
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for https://lists.canonical.com/mailman3/postorius/lists/
This source builds only docs and mailman3 itself (which provides mailman3-core).
[Rationale]
This is part of the MIR activity for all dependencies of mailman3
The "main" MIR of it is at bug 1775427:
Mailman (2) has only python2 support, but we strive for python3,
therefore Mailman3 which has python3 support should be promoted to main.
This is an evolution of the mailman2 core delivery engine of the system, but I can't guess how much it deviated so we need to recheck security (IMHO)
[Security]
No known CVEs found.
A few old issues can be found against mailman2 and one (but long fixed) for mailman 3
=> https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=mailman
[Quality assurance]
The mailman3 stacks as of now (Disco) installs fine and provides a base
config. But due to the nature of the package that needs further modification
to be of real use.
The package does in error cases ask a debconf-high question, but it is not going to be installed by default - so that is no MIR problem.
There are a few (2) Ubuntu bugs outstanding, but none of them is critical and stopping this MIR request.
There are a few (2) Debian bugs outstanding all seems to "just work" still, but when we main this in 19.10 we should at least evaluate and maybe adress this one:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921445
There are regular upstream releases and Debian packages them and fixes regularly.
No exotic HW involved.
The package ships a test suite, but it is not run at build time for upstream bug #400.
It tests things in a dep8 test thou to provide coverage.
d/watch is set up and ok.
No Lintian warning except fairly recent newer Standards version.
The package does not rely on demoted or obsolete packages.
[UI standards]
Comes with 7 translations in .po files
No End-user applications that needs a standard conformant desktop file.
[Dependencies]
Some dependencies are not in main, but we drive MIR for all related packages
that are not in main at the same time.
Please check the list of bugs from the main Mailman3 MIR in bug 1775427 to get an overview.
[Standards compliance]
The package meets the FHS and Debian Policy standards.
The packaging itself is very straight forward and uses dh_* as much as possible - the d/rules fits on one screen.
[Maintenance]
The Server team will subscribe for the package for maintenance
[Background]
The package description explains the general purpose and context of the package well.
---
References to all the related MIR bug - one per affected package.
Status (simplified version of https://wiki.ubuntu.com/MIRTeam#Process_states)
(nothing) means we have not even prepared the MIR yet
- MIR not needed (e.g. dependency will be dropped)
* all of the template fields for the MIR are complete
! waiting for MIR review
? cpaelzer needs experienced MIR team members to continue
S needs security review to be accepted
+ MIR accepted
x MIR nacked
Extra Flags which team members or on review feedback can be added:
T extra work for the team that should be done before 20.04 (state todo after package)
M extra work for the team before getting MIR to be acceptable (read as asap)
C needed if only promoting mailman3 (core)
H needed if only promoting mailman3 (core) plus Hyperkitty
J no more needed for mailman3-web if we can cut node-less out
FLAGS | MIR-Bug | Package (Notes)
TC
MH
----------------------------------------
! | bug 1820179 | coreapi
! | bug 1820180 | coreschema
! | bug 1820181 | django-allauth
! | bug 1820182 | django-filter
! | bug 1820183 | django-guardian
! | bug 1820185 | django-haystack
! | bug 1820186 | django-mailman3
- | | django-paintstore ((no dep hyperkitty >=1.2.2-1)
! | bug 1820188 | django-picklefield
! | bug 1820189 | django-q
! | bug 1820190 | djangorestframework
! C | bug 1820191 | flufl.bounce
! C | bug 1820192 | flufl.i18n
! C | bug 1820193 | flufl.lock
! | bug 1820195 | glewlwyd
! | bug 1820196 | hyperkitty
! | bug 1820197 | itypes
- | n/a | jqueryui (no dep hyperkitty >=1.2.2-1)
! C | bug 1820199 | lazr.config
!TC | bug 1820200 | lazr.delegates (opt: update version before 20.04)
*MJ | bug 1820201 | less.js (opt: update version before 20.04)
- | n/a | libjs-jquery-colorpicker (no dep hyperkitty >=1.2.2-1)
! | bug 1820202 | libmatheval
! | bug 1820203 | libpgm
! C | bug 1775427 | mailman3
! | bug 1820204 | mailmanclient
! H | bug 1820205 | mailman-hyperkitty
! | bug 1820206 | mailman-suite
*MJ | bug 1820207 | node-source-map
*MJ | bug 1820208 | nodejs
! | bug 1820209 | norm
-M | n/a | nose (important: drop dep from lazr.delegates to this)
! | bug 1820210 | postorius
! | bug 1820211 | python3-openid
! C | bug 1820212 | python-aiosmtpd
! | bug 1820213 | python-arrow
! | bug 1820214 | python-blessed
! | bug 1820215 | python-django-extensions
! | bug 1820216 | python-django-gravatar2
!TC | bug 1820217 | python-falcon (opt: update version before 20.04)
*M | bug 1820218 | python-lockfile (demotion since 686045?)
!TC | bug 1820220 | python-public (opt: update version before 20.04)
! | bug 1820221 | python-requests-oauthlib
!T | bug 1820223 | python-uritemplate (feed delta to Debian, become a sync)
! | bug 1820224 | python-whoosh
! | bug 1820225 | robot-detection
-M | n/a | ruby-sass (deprecated, use sassc - Debian 924629)
M | TBD | sassc (waits for ruby-sass dep to be resolved first)
M | TBD | libsass (waits for ruby-sass dep to be resolved first)
! | bug 1820226 | twitter-bootstrap3
! | bug 1820227 | uwsgi
! | bug 1820229 | wcwidth
*M | bug 1820232 | zeromq3 (fix FTBFS in Disco, demotion since 1597439?)
!TC | bug 1820233 | zope.component (version update)
!TC | bug 1820234 | zope.configuration (version update)
!TC | bug 1820236 | zope.event (version update)
!TC | bug 1820237 | zope.hookable (version update)
!TC | bug 1820238 | zope.i18nmessageid (version update)
*TC | bug 1820239 | zope.schema (version update)
This might sometimes be slightly out of date, to cross check and for history on all of them check git at:
https://git.launchpad.net/~ubuntu-server/+git/mailman3-MIR-party/tree/package-list.txt
---
Past Decisions in regard to this:
mailman is python2, mailman3 is python3, but also it has new dependency stack due to adopting django but also splitting or rewriting a lot of its components.
Q: Do we want bin:mailman3 or bin:mailman3-full in main? (the latter pulls
in src:mailman-suite as well). src:mailman-suite has potentially more
things - django, hyperkitty, ruby-sass, uwsgi...
A: We analyzed this and we will need the full set of dependencies, even
meaning MIRs are needed for all of the above listed (and more).
Q: Before proceeding further with assignment/doing technical work in
driving above MIRs, a product level yes/no answers should probably be
answered for above two questions.
A: Discussed in several sprints now, as uncomfortable as it is we will go
through the mass-MIR processing |
|
| 2019-03-19 08:00:09 |
Christian Ehrhardt |
description |
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for https://lists.canonical.com/mailman3/postorius/lists/
This source builds only docs and mailman3 itself (which provides mailman3-core).
[Rationale]
This is part of the MIR activity for all dependencies of mailman3
The "main" MIR of it is at bug 1775427:
Mailman (2) has only python2 support, but we strive for python3,
therefore Mailman3 which has python3 support should be promoted to main.
This is an evolution of the mailman2 core delivery engine of the system, but I can't guess how much it deviated so we need to recheck security (IMHO)
[Security]
No known CVEs found.
A few old issues can be found against mailman2 and one (but long fixed) for mailman 3
=> https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=mailman
[Quality assurance]
The mailman3 stacks as of now (Disco) installs fine and provides a base
config. But due to the nature of the package that needs further modification
to be of real use.
The package does in error cases ask a debconf-high question, but it is not going to be installed by default - so that is no MIR problem.
There are a few (2) Ubuntu bugs outstanding, but none of them is critical and stopping this MIR request.
There are a few (2) Debian bugs outstanding all seems to "just work" still, but when we main this in 19.10 we should at least evaluate and maybe adress this one:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921445
There are regular upstream releases and Debian packages them and fixes regularly.
No exotic HW involved.
The package ships a test suite, but it is not run at build time for upstream bug #400.
It tests things in a dep8 test thou to provide coverage.
d/watch is set up and ok.
No Lintian warning except fairly recent newer Standards version.
The package does not rely on demoted or obsolete packages.
[UI standards]
Comes with 7 translations in .po files
No End-user applications that needs a standard conformant desktop file.
[Dependencies]
Some dependencies are not in main, but we drive MIR for all related packages
that are not in main at the same time.
Please check the list of bugs from the main Mailman3 MIR in bug 1775427 to get an overview.
[Standards compliance]
The package meets the FHS and Debian Policy standards.
The packaging itself is very straight forward and uses dh_* as much as possible - the d/rules fits on one screen.
[Maintenance]
The Server team will subscribe for the package for maintenance
[Background]
The package description explains the general purpose and context of the package well.
---
References to all the related MIR bug - one per affected package.
Status (simplified version of https://wiki.ubuntu.com/MIRTeam#Process_states)
(nothing) means we have not even prepared the MIR yet
- MIR not needed (e.g. dependency will be dropped)
* all of the template fields for the MIR are complete
! waiting for MIR review
? cpaelzer needs experienced MIR team members to continue
S needs security review to be accepted
+ MIR accepted
x MIR nacked
Extra Flags which team members or on review feedback can be added:
T extra work for the team that should be done before 20.04 (state todo after package)
M extra work for the team before getting MIR to be acceptable (read as asap)
C needed if only promoting mailman3 (core)
H needed if only promoting mailman3 (core) plus Hyperkitty
J no more needed for mailman3-web if we can cut node-less out
FLAGS | MIR-Bug | Package (Notes)
TC
MH
----------------------------------------
! | bug 1820179 | coreapi
! | bug 1820180 | coreschema
! | bug 1820181 | django-allauth
! | bug 1820182 | django-filter
! | bug 1820183 | django-guardian
! | bug 1820185 | django-haystack
! | bug 1820186 | django-mailman3
- | | django-paintstore ((no dep hyperkitty >=1.2.2-1)
! | bug 1820188 | django-picklefield
! | bug 1820189 | django-q
! | bug 1820190 | djangorestframework
! C | bug 1820191 | flufl.bounce
! C | bug 1820192 | flufl.i18n
! C | bug 1820193 | flufl.lock
! | bug 1820195 | glewlwyd
! | bug 1820196 | hyperkitty
! | bug 1820197 | itypes
- | n/a | jqueryui (no dep hyperkitty >=1.2.2-1)
! C | bug 1820199 | lazr.config
!TC | bug 1820200 | lazr.delegates (opt: update version before 20.04)
*MJ | bug 1820201 | less.js (opt: update version before 20.04)
- | n/a | libjs-jquery-colorpicker (no dep hyperkitty >=1.2.2-1)
! | bug 1820202 | libmatheval
! | bug 1820203 | libpgm
! C | bug 1775427 | mailman3
! | bug 1820204 | mailmanclient
! H | bug 1820205 | mailman-hyperkitty
! | bug 1820206 | mailman-suite
*MJ | bug 1820207 | node-source-map
*MJ | bug 1820208 | nodejs
! | bug 1820209 | norm
-M | n/a | nose (important: drop dep from lazr.delegates to this)
! | bug 1820210 | postorius
! | bug 1820211 | python3-openid
! C | bug 1820212 | python-aiosmtpd
! | bug 1820213 | python-arrow
! | bug 1820214 | python-blessed
! | bug 1820215 | python-django-extensions
! | bug 1820216 | python-django-gravatar2
!TC | bug 1820217 | python-falcon (opt: update version before 20.04)
*M | bug 1820218 | python-lockfile (demotion since 686045?)
!TC | bug 1820220 | python-public (opt: update version before 20.04)
! | bug 1820221 | python-requests-oauthlib
!T | bug 1820223 | python-uritemplate (feed delta to Debian, become a sync)
! | bug 1820224 | python-whoosh
! | bug 1820225 | robot-detection
-M | n/a | ruby-sass (deprecated, use sassc - Debian 924629)
M | TBD | sassc (waits for ruby-sass dep to be resolved first)
M | TBD | libsass (waits for ruby-sass dep to be resolved first)
! | bug 1820226 | twitter-bootstrap3
! | bug 1820227 | uwsgi
! | bug 1820229 | wcwidth
*M | bug 1820232 | zeromq3 (fix FTBFS in Disco, demotion since 1597439?)
!TC | bug 1820233 | zope.component (version update)
!TC | bug 1820234 | zope.configuration (version update)
!TC | bug 1820236 | zope.event (version update)
!TC | bug 1820237 | zope.hookable (version update)
!TC | bug 1820238 | zope.i18nmessageid (version update)
*TC | bug 1820239 | zope.schema (version update)
This might sometimes be slightly out of date, to cross check and for history on all of them check git at:
https://git.launchpad.net/~ubuntu-server/+git/mailman3-MIR-party/tree/package-list.txt
---
Past Decisions in regard to this:
mailman is python2, mailman3 is python3, but also it has new dependency stack due to adopting django but also splitting or rewriting a lot of its components.
Q: Do we want bin:mailman3 or bin:mailman3-full in main? (the latter pulls
in src:mailman-suite as well). src:mailman-suite has potentially more
things - django, hyperkitty, ruby-sass, uwsgi...
A: We analyzed this and we will need the full set of dependencies, even
meaning MIRs are needed for all of the above listed (and more).
Q: Before proceeding further with assignment/doing technical work in
driving above MIRs, a product level yes/no answers should probably be
answered for above two questions.
A: Discussed in several sprints now, as uncomfortable as it is we will go
through the mass-MIR processing |
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for https://lists.canonical.com/mailman3/postorius/lists/
This source builds only docs and mailman3 itself (which provides mailman3-core).
[Rationale]
This is part of the MIR activity for all dependencies of mailman3
The "main" MIR of it is at bug 1775427:
Mailman (2) has only python2 support, but we strive for python3,
therefore Mailman3 which has python3 support should be promoted to main.
This is an evolution of the mailman2 core delivery engine of the system, but I can't guess how much it deviated so we need to recheck security (IMHO)
[Security]
No known CVEs found.
A few old issues can be found against mailman2 and one (but long fixed) for mailman 3
=> https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=mailman
[Quality assurance]
The mailman3 stacks as of now (Disco) installs fine and provides a base
config. But due to the nature of the package that needs further modification
to be of real use.
The package does in error cases ask a debconf-high question, but it is not going to be installed by default - so that is no MIR problem.
There are a few (2) Ubuntu bugs outstanding, but none of them is critical and stopping this MIR request.
There are a few (2) Debian bugs outstanding all seems to "just work" still, but when we main this in 19.10 we should at least evaluate and maybe adress this one:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921445
There are regular upstream releases and Debian packages them and fixes regularly.
No exotic HW involved.
The package ships a test suite, but it is not run at build time for upstream bug #400.
It tests things in a dep8 test thou to provide coverage.
d/watch is set up and ok.
No Lintian warning except fairly recent newer Standards version.
The package does not rely on demoted or obsolete packages.
[UI standards]
Comes with 7 translations in .po files
No End-user applications that needs a standard conformant desktop file.
[Dependencies]
Some dependencies are not in main, but we drive MIR for all related packages
that are not in main at the same time.
Please check the list of bugs from the main Mailman3 MIR in bug 1775427 to get an overview.
[Standards compliance]
The package meets the FHS and Debian Policy standards.
The packaging itself is very straight forward and uses dh_* as much as possible - the d/rules fits on one screen.
[Maintenance]
The Server team will subscribe for the package for maintenance
[Background]
The package description explains the general purpose and context of the package well.
---
References to all the related MIR bug - one per affected package.
Status (simplified version of https://wiki.ubuntu.com/MIRTeam#Process_states)
(nothing) means we have not even prepared the MIR yet
- MIR not needed (e.g. dependency will be dropped)
* all of the template fields for the MIR are complete
! waiting for MIR review
? cpaelzer needs experienced MIR team members to continue
S needs security review to be accepted
+ MIR accepted
x MIR nacked
Extra Flags which team members or on review feedback can be added:
T extra work for the team that should be done before 20.04 (state todo after package)
M extra work for the team before getting MIR to be acceptable (read as asap)
C needed if only promoting mailman3 (core)
H needed if only promoting mailman3 (core) plus Hyperkitty
J no more needed for mailman3-web if we can cut node-less out
FLAGS | MIR-Bug | Package (Notes)
TC
MH
----------------------------------------
! | bug 1820179 | coreapi
! | bug 1820180 | coreschema
! | bug 1820181 | django-allauth
! | bug 1820182 | django-filter
! | bug 1820183 | django-guardian
! | bug 1820185 | django-haystack
! | bug 1820186 | django-mailman3
- | | django-paintstore ((no dep hyperkitty >=1.2.2-1)
! | bug 1820188 | django-picklefield
! | bug 1820189 | django-q
! | bug 1820190 | djangorestframework
! C | bug 1820191 | flufl.bounce
! C | bug 1820192 | flufl.i18n
! C | bug 1820193 | flufl.lock
! | bug 1820195 | glewlwyd
! | bug 1820196 | hyperkitty
! | bug 1820197 | itypes
- | n/a | jqueryui (no dep hyperkitty >=1.2.2-1)
! C | bug 1820199 | lazr.config
!TC | bug 1820200 | lazr.delegates (opt: update version before 20.04)
-MJ | bug 1820201 | less.js (Dep will be cut out in Debian bug 924961)
- | n/a | libjs-jquery-colorpicker (no hyperkitty >=1.2.2-1)
! | bug 1820202 | libmatheval
! | bug 1820203 | libpgm
! C | bug 1775427 | mailman3
! | bug 1820204 | mailmanclient
! H | bug 1820205 | mailman-hyperkitty
! | bug 1820206 | mailman-suite
-MJ | bug 1820207 | node-source-map (wait for node-less dep to be cut)
-MJ | bug 1820208 | nodejs (wait for node-less dep to be cut)
! | bug 1820209 | norm
-M | n/a | nose (important: drop dep from lazr.delegates)
! | bug 1820210 | postorius
! | bug 1820211 | python3-openid
! C | bug 1820212 | python-aiosmtpd
! | bug 1820213 | python-arrow
! | bug 1820214 | python-blessed
! | bug 1820215 | python-django-extensions
! | bug 1820216 | python-django-gravatar2
!TC | bug 1820217 | python-falcon (opt: update version before 20.04)
*M | bug 1820218 | python-lockfile (demotion since 686045?)
!TC | bug 1820220 | python-public (opt: update version before 20.04)
! | bug 1820221 | python-requests-oauthlib
!T | bug 1820223 | python-uritemplate (feed delta back, be a sync)
! | bug 1820224 | python-whoosh
! | bug 1820225 | robot-detection
-M | n/a | ruby-sass (deprecated, use sassc - Debian 924629)
-M | TBD | sassc (Dep will be cut by Debian bug 924961)
-M | TBD | libsass (Dep will be cut by Debian bug 924961)
! | bug 1820226 | twitter-bootstrap3
! | bug 1820227 | uwsgi (FTBFS: #1820095)
! | bug 1820229 | wcwidth
*M | bug 1820232 | zeromq3 (FTBFS #1820282, demotion since 1597439?)
!TC | bug 1820233 | zope.component (version update)
!TC | bug 1820234 | zope.configuration (version update)
!TC | bug 1820236 | zope.event (version update)
!TC | bug 1820237 | zope.hookable (version update)
!TC | bug 1820238 | zope.i18nmessageid (version update)
*TC | bug 1820239 | zope.schema (version update)
List Debian bugs we depend on being resolved as expected before
the dependency tree can completely be MIRed:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924629
- https://bugs.debian.org/cgi-bin/gbugreport.cgi?bug=924961
This might sometimes be slightly out of date, to cross check and for history on all of them check git at:
https://git.launchpad.net/~ubuntu-server/+git/mailman3-MIR-party/tree/package-list.txt
---
Past Decisions in regard to this:
mailman is python2, mailman3 is python3, but also it has new dependency stack due to adopting django but also splitting or rewriting a lot of its components.
Q: Do we want bin:mailman3 or bin:mailman3-full in main? (the latter pulls
in src:mailman-suite as well). src:mailman-suite has potentially more
things - django, hyperkitty, ruby-sass, uwsgi...
A: We analyzed this and we will need the full set of dependencies, even
meaning MIRs are needed for all of the above listed (and more).
Q: Before proceeding further with assignment/doing technical work in
driving above MIRs, a product level yes/no answers should probably be
answered for above two questions.
A: Discussed in several sprints now, as uncomfortable as it is we will go
through the mass-MIR processing |
|
| 2019-03-19 08:03:46 |
Christian Ehrhardt |
bug watch added |
|
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924629 |
|
| 2019-03-19 08:34:27 |
Christian Ehrhardt |
description |
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for https://lists.canonical.com/mailman3/postorius/lists/
This source builds only docs and mailman3 itself (which provides mailman3-core).
[Rationale]
This is part of the MIR activity for all dependencies of mailman3
The "main" MIR of it is at bug 1775427:
Mailman (2) has only python2 support, but we strive for python3,
therefore Mailman3 which has python3 support should be promoted to main.
This is an evolution of the mailman2 core delivery engine of the system, but I can't guess how much it deviated so we need to recheck security (IMHO)
[Security]
No known CVEs found.
A few old issues can be found against mailman2 and one (but long fixed) for mailman 3
=> https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=mailman
[Quality assurance]
The mailman3 stacks as of now (Disco) installs fine and provides a base
config. But due to the nature of the package that needs further modification
to be of real use.
The package does in error cases ask a debconf-high question, but it is not going to be installed by default - so that is no MIR problem.
There are a few (2) Ubuntu bugs outstanding, but none of them is critical and stopping this MIR request.
There are a few (2) Debian bugs outstanding all seems to "just work" still, but when we main this in 19.10 we should at least evaluate and maybe adress this one:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921445
There are regular upstream releases and Debian packages them and fixes regularly.
No exotic HW involved.
The package ships a test suite, but it is not run at build time for upstream bug #400.
It tests things in a dep8 test thou to provide coverage.
d/watch is set up and ok.
No Lintian warning except fairly recent newer Standards version.
The package does not rely on demoted or obsolete packages.
[UI standards]
Comes with 7 translations in .po files
No End-user applications that needs a standard conformant desktop file.
[Dependencies]
Some dependencies are not in main, but we drive MIR for all related packages
that are not in main at the same time.
Please check the list of bugs from the main Mailman3 MIR in bug 1775427 to get an overview.
[Standards compliance]
The package meets the FHS and Debian Policy standards.
The packaging itself is very straight forward and uses dh_* as much as possible - the d/rules fits on one screen.
[Maintenance]
The Server team will subscribe for the package for maintenance
[Background]
The package description explains the general purpose and context of the package well.
---
References to all the related MIR bug - one per affected package.
Status (simplified version of https://wiki.ubuntu.com/MIRTeam#Process_states)
(nothing) means we have not even prepared the MIR yet
- MIR not needed (e.g. dependency will be dropped)
* all of the template fields for the MIR are complete
! waiting for MIR review
? cpaelzer needs experienced MIR team members to continue
S needs security review to be accepted
+ MIR accepted
x MIR nacked
Extra Flags which team members or on review feedback can be added:
T extra work for the team that should be done before 20.04 (state todo after package)
M extra work for the team before getting MIR to be acceptable (read as asap)
C needed if only promoting mailman3 (core)
H needed if only promoting mailman3 (core) plus Hyperkitty
J no more needed for mailman3-web if we can cut node-less out
FLAGS | MIR-Bug | Package (Notes)
TC
MH
----------------------------------------
! | bug 1820179 | coreapi
! | bug 1820180 | coreschema
! | bug 1820181 | django-allauth
! | bug 1820182 | django-filter
! | bug 1820183 | django-guardian
! | bug 1820185 | django-haystack
! | bug 1820186 | django-mailman3
- | | django-paintstore ((no dep hyperkitty >=1.2.2-1)
! | bug 1820188 | django-picklefield
! | bug 1820189 | django-q
! | bug 1820190 | djangorestframework
! C | bug 1820191 | flufl.bounce
! C | bug 1820192 | flufl.i18n
! C | bug 1820193 | flufl.lock
! | bug 1820195 | glewlwyd
! | bug 1820196 | hyperkitty
! | bug 1820197 | itypes
- | n/a | jqueryui (no dep hyperkitty >=1.2.2-1)
! C | bug 1820199 | lazr.config
!TC | bug 1820200 | lazr.delegates (opt: update version before 20.04)
-MJ | bug 1820201 | less.js (Dep will be cut out in Debian bug 924961)
- | n/a | libjs-jquery-colorpicker (no hyperkitty >=1.2.2-1)
! | bug 1820202 | libmatheval
! | bug 1820203 | libpgm
! C | bug 1775427 | mailman3
! | bug 1820204 | mailmanclient
! H | bug 1820205 | mailman-hyperkitty
! | bug 1820206 | mailman-suite
-MJ | bug 1820207 | node-source-map (wait for node-less dep to be cut)
-MJ | bug 1820208 | nodejs (wait for node-less dep to be cut)
! | bug 1820209 | norm
-M | n/a | nose (important: drop dep from lazr.delegates)
! | bug 1820210 | postorius
! | bug 1820211 | python3-openid
! C | bug 1820212 | python-aiosmtpd
! | bug 1820213 | python-arrow
! | bug 1820214 | python-blessed
! | bug 1820215 | python-django-extensions
! | bug 1820216 | python-django-gravatar2
!TC | bug 1820217 | python-falcon (opt: update version before 20.04)
*M | bug 1820218 | python-lockfile (demotion since 686045?)
!TC | bug 1820220 | python-public (opt: update version before 20.04)
! | bug 1820221 | python-requests-oauthlib
!T | bug 1820223 | python-uritemplate (feed delta back, be a sync)
! | bug 1820224 | python-whoosh
! | bug 1820225 | robot-detection
-M | n/a | ruby-sass (deprecated, use sassc - Debian 924629)
-M | TBD | sassc (Dep will be cut by Debian bug 924961)
-M | TBD | libsass (Dep will be cut by Debian bug 924961)
! | bug 1820226 | twitter-bootstrap3
! | bug 1820227 | uwsgi (FTBFS: #1820095)
! | bug 1820229 | wcwidth
*M | bug 1820232 | zeromq3 (FTBFS #1820282, demotion since 1597439?)
!TC | bug 1820233 | zope.component (version update)
!TC | bug 1820234 | zope.configuration (version update)
!TC | bug 1820236 | zope.event (version update)
!TC | bug 1820237 | zope.hookable (version update)
!TC | bug 1820238 | zope.i18nmessageid (version update)
*TC | bug 1820239 | zope.schema (version update)
List Debian bugs we depend on being resolved as expected before
the dependency tree can completely be MIRed:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924629
- https://bugs.debian.org/cgi-bin/gbugreport.cgi?bug=924961
This might sometimes be slightly out of date, to cross check and for history on all of them check git at:
https://git.launchpad.net/~ubuntu-server/+git/mailman3-MIR-party/tree/package-list.txt
---
Past Decisions in regard to this:
mailman is python2, mailman3 is python3, but also it has new dependency stack due to adopting django but also splitting or rewriting a lot of its components.
Q: Do we want bin:mailman3 or bin:mailman3-full in main? (the latter pulls
in src:mailman-suite as well). src:mailman-suite has potentially more
things - django, hyperkitty, ruby-sass, uwsgi...
A: We analyzed this and we will need the full set of dependencies, even
meaning MIRs are needed for all of the above listed (and more).
Q: Before proceeding further with assignment/doing technical work in
driving above MIRs, a product level yes/no answers should probably be
answered for above two questions.
A: Discussed in several sprints now, as uncomfortable as it is we will go
through the mass-MIR processing |
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for https://lists.canonical.com/mailman3/postorius/lists/
This source builds only docs and mailman3 itself (which provides mailman3-core).
[Rationale]
This is part of the MIR activity for all dependencies of mailman3
The "main" MIR of it is at bug 1775427:
Mailman (2) has only python2 support, but we strive for python3,
therefore Mailman3 which has python3 support should be promoted to main.
This is an evolution of the mailman2 core delivery engine of the system, but I can't guess how much it deviated so we need to recheck security (IMHO)
[Security]
No known CVEs found.
A few old issues can be found against mailman2 and one (but long fixed) for mailman 3
=> https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=mailman
[Quality assurance]
The mailman3 stacks as of now (Disco) installs fine and provides a base
config. But due to the nature of the package that needs further modification
to be of real use.
The package does in error cases ask a debconf-high question, but it is not going to be installed by default - so that is no MIR problem.
There are a few (2) Ubuntu bugs outstanding, but none of them is critical and stopping this MIR request.
There are a few (2) Debian bugs outstanding all seems to "just work" still, but when we main this in 19.10 we should at least evaluate and maybe adress this one:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921445
There are regular upstream releases and Debian packages them and fixes regularly.
No exotic HW involved.
The package ships a test suite, but it is not run at build time for upstream bug #400.
It tests things in a dep8 test thou to provide coverage.
d/watch is set up and ok.
No Lintian warning except fairly recent newer Standards version.
The package does not rely on demoted or obsolete packages.
[UI standards]
Comes with 7 translations in .po files
No End-user applications that needs a standard conformant desktop file.
[Dependencies]
Some dependencies are not in main, but we drive MIR for all related packages
that are not in main at the same time.
Please check the list of bugs from the main Mailman3 MIR in bug 1775427 to get an overview.
[Standards compliance]
The package meets the FHS and Debian Policy standards.
The packaging itself is very straight forward and uses dh_* as much as possible - the d/rules fits on one screen.
[Maintenance]
The Server team will subscribe for the package for maintenance
[Background]
The package description explains the general purpose and context of the package well.
---
References to all the related MIR bug - one per affected package.
Status (simplified version of https://wiki.ubuntu.com/MIRTeam#Process_states)
(nothing) means we have not even prepared the MIR yet
- MIR not needed (e.g. dependency will be dropped)
* all of the template fields for the MIR are complete
! waiting for MIR review
? cpaelzer needs experienced MIR team members to continue
S needs security review to be accepted
+ MIR accepted
x MIR nacked
Extra Flags which team members or on review feedback can be added:
T extra work for the team that should be done before 20.04 (state todo after package)
M extra work for the team before getting MIR to be acceptable (read as asap)
C needed if only promoting mailman3 (core)
H needed if only promoting mailman3 (core) plus Hyperkitty
J no more needed for mailman3-web if we can cut node-less out
FLAGS | MIR-Bug | Package (Notes)
TC
MH
----------------------------------------
! | bug 1820179 | coreapi
! | bug 1820180 | coreschema
! | bug 1820181 | django-allauth
! | bug 1820182 | django-filter
! | bug 1820183 | django-guardian
! | bug 1820185 | django-haystack
! | bug 1820186 | django-mailman3
- | | django-paintstore ((no dep hyperkitty >=1.2.2-1)
! | bug 1820188 | django-picklefield
! | bug 1820189 | django-q
! | bug 1820190 | djangorestframework
! C | bug 1820191 | flufl.bounce
! C | bug 1820192 | flufl.i18n
! C | bug 1820193 | flufl.lock
! | bug 1820195 | glewlwyd
! | bug 1820196 | hyperkitty
! | bug 1820197 | itypes
- | n/a | jqueryui (no dep hyperkitty >=1.2.2-1)
! C | bug 1820199 | lazr.config
!TC | bug 1820200 | lazr.delegates (opt: update version before 20.04)
-MJ | bug 1820201 | less.js (Dep will be cut out in Debian bug 924961)
- | n/a | libjs-jquery-colorpicker (no hyperkitty >=1.2.2-1)
! | bug 1820202 | libmatheval
! | bug 1820203 | libpgm
! C | bug 1775427 | mailman3
! | bug 1820204 | mailmanclient
! H | bug 1820205 | mailman-hyperkitty
! | bug 1820206 | mailman-suite
-MJ | bug 1820207 | node-source-map (wait for node-less dep to be cut)
-MJ | bug 1820208 | nodejs (wait for node-less dep to be cut)
! | bug 1820209 | norm
-M | n/a | nose (important: drop dep from lazr.delegates)
! | bug 1820210 | postorius
! | bug 1820211 | python3-openid
! C | bug 1820212 | python-aiosmtpd
! | bug 1820213 | python-arrow
! | bug 1820214 | python-blessed
! | bug 1820215 | python-django-extensions
! | bug 1820216 | python-django-gravatar2
!TC | bug 1820217 | python-falcon (opt: update version before 20.04)
*M | bug 1820218 | python-lockfile (demotion since 686045?)
!TC | bug 1820220 | python-public (opt: update version before 20.04)
! | bug 1820221 | python-requests-oauthlib
!T | bug 1820223 | python-uritemplate (feed delta back, be a sync)
! | bug 1820224 | python-whoosh
! | bug 1820225 | robot-detection
-M | n/a | ruby-sass (deprecated, use sassc - Debian 924629)
-M | TBD | sassc (Dep will be cut by Debian bug 924961)
-M | TBD | libsass (Dep will be cut by Debian bug 924961)
! | bug 1820226 | twitter-bootstrap3
! | bug 1820227 | uwsgi (FTBFS: #1820095)
! | bug 1820229 | wcwidth
*M | bug 1820232 | zeromq3 (FTBFS #1820282, demotion since 1597439?)
!TC | bug 1820233 | zope.component (version update)
!TC | bug 1820234 | zope.configuration (version update)
!TC | bug 1820236 | zope.event (version update)
!TC | bug 1820237 | zope.hookable (version update)
!TC | bug 1820238 | zope.i18nmessageid (version update)
*TC | bug 1820239 | zope.schema (version update)
List Debian bugs we depend on being resolved as expected before
the dependency tree can completely be MIRed:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924629
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924961
This might sometimes be slightly out of date, to cross check and for history on all of them check git at:
https://git.launchpad.net/~ubuntu-server/+git/mailman3-MIR-party/tree/package-list.txt
---
Past Decisions in regard to this:
mailman is python2, mailman3 is python3, but also it has new dependency stack due to adopting django but also splitting or rewriting a lot of its components.
Q: Do we want bin:mailman3 or bin:mailman3-full in main? (the latter pulls
in src:mailman-suite as well). src:mailman-suite has potentially more
things - django, hyperkitty, ruby-sass, uwsgi...
A: We analyzed this and we will need the full set of dependencies, even
meaning MIRs are needed for all of the above listed (and more).
Q: Before proceeding further with assignment/doing technical work in
driving above MIRs, a product level yes/no answers should probably be
answered for above two questions.
A: Discussed in several sprints now, as uncomfortable as it is we will go
through the mass-MIR processing |
|
| 2019-03-19 10:20:42 |
Christian Ehrhardt |
description |
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for https://lists.canonical.com/mailman3/postorius/lists/
This source builds only docs and mailman3 itself (which provides mailman3-core).
[Rationale]
This is part of the MIR activity for all dependencies of mailman3
The "main" MIR of it is at bug 1775427:
Mailman (2) has only python2 support, but we strive for python3,
therefore Mailman3 which has python3 support should be promoted to main.
This is an evolution of the mailman2 core delivery engine of the system, but I can't guess how much it deviated so we need to recheck security (IMHO)
[Security]
No known CVEs found.
A few old issues can be found against mailman2 and one (but long fixed) for mailman 3
=> https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=mailman
[Quality assurance]
The mailman3 stacks as of now (Disco) installs fine and provides a base
config. But due to the nature of the package that needs further modification
to be of real use.
The package does in error cases ask a debconf-high question, but it is not going to be installed by default - so that is no MIR problem.
There are a few (2) Ubuntu bugs outstanding, but none of them is critical and stopping this MIR request.
There are a few (2) Debian bugs outstanding all seems to "just work" still, but when we main this in 19.10 we should at least evaluate and maybe adress this one:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921445
There are regular upstream releases and Debian packages them and fixes regularly.
No exotic HW involved.
The package ships a test suite, but it is not run at build time for upstream bug #400.
It tests things in a dep8 test thou to provide coverage.
d/watch is set up and ok.
No Lintian warning except fairly recent newer Standards version.
The package does not rely on demoted or obsolete packages.
[UI standards]
Comes with 7 translations in .po files
No End-user applications that needs a standard conformant desktop file.
[Dependencies]
Some dependencies are not in main, but we drive MIR for all related packages
that are not in main at the same time.
Please check the list of bugs from the main Mailman3 MIR in bug 1775427 to get an overview.
[Standards compliance]
The package meets the FHS and Debian Policy standards.
The packaging itself is very straight forward and uses dh_* as much as possible - the d/rules fits on one screen.
[Maintenance]
The Server team will subscribe for the package for maintenance
[Background]
The package description explains the general purpose and context of the package well.
---
References to all the related MIR bug - one per affected package.
Status (simplified version of https://wiki.ubuntu.com/MIRTeam#Process_states)
(nothing) means we have not even prepared the MIR yet
- MIR not needed (e.g. dependency will be dropped)
* all of the template fields for the MIR are complete
! waiting for MIR review
? cpaelzer needs experienced MIR team members to continue
S needs security review to be accepted
+ MIR accepted
x MIR nacked
Extra Flags which team members or on review feedback can be added:
T extra work for the team that should be done before 20.04 (state todo after package)
M extra work for the team before getting MIR to be acceptable (read as asap)
C needed if only promoting mailman3 (core)
H needed if only promoting mailman3 (core) plus Hyperkitty
J no more needed for mailman3-web if we can cut node-less out
FLAGS | MIR-Bug | Package (Notes)
TC
MH
----------------------------------------
! | bug 1820179 | coreapi
! | bug 1820180 | coreschema
! | bug 1820181 | django-allauth
! | bug 1820182 | django-filter
! | bug 1820183 | django-guardian
! | bug 1820185 | django-haystack
! | bug 1820186 | django-mailman3
- | | django-paintstore ((no dep hyperkitty >=1.2.2-1)
! | bug 1820188 | django-picklefield
! | bug 1820189 | django-q
! | bug 1820190 | djangorestframework
! C | bug 1820191 | flufl.bounce
! C | bug 1820192 | flufl.i18n
! C | bug 1820193 | flufl.lock
! | bug 1820195 | glewlwyd
! | bug 1820196 | hyperkitty
! | bug 1820197 | itypes
- | n/a | jqueryui (no dep hyperkitty >=1.2.2-1)
! C | bug 1820199 | lazr.config
!TC | bug 1820200 | lazr.delegates (opt: update version before 20.04)
-MJ | bug 1820201 | less.js (Dep will be cut out in Debian bug 924961)
- | n/a | libjs-jquery-colorpicker (no hyperkitty >=1.2.2-1)
! | bug 1820202 | libmatheval
! | bug 1820203 | libpgm
! C | bug 1775427 | mailman3
! | bug 1820204 | mailmanclient
! H | bug 1820205 | mailman-hyperkitty
! | bug 1820206 | mailman-suite
-MJ | bug 1820207 | node-source-map (wait for node-less dep to be cut)
-MJ | bug 1820208 | nodejs (wait for node-less dep to be cut)
! | bug 1820209 | norm
-M | n/a | nose (important: drop dep from lazr.delegates)
! | bug 1820210 | postorius
! | bug 1820211 | python3-openid
! C | bug 1820212 | python-aiosmtpd
! | bug 1820213 | python-arrow
! | bug 1820214 | python-blessed
! | bug 1820215 | python-django-extensions
! | bug 1820216 | python-django-gravatar2
!TC | bug 1820217 | python-falcon (opt: update version before 20.04)
*M | bug 1820218 | python-lockfile (demotion since 686045?)
!TC | bug 1820220 | python-public (opt: update version before 20.04)
! | bug 1820221 | python-requests-oauthlib
!T | bug 1820223 | python-uritemplate (feed delta back, be a sync)
! | bug 1820224 | python-whoosh
! | bug 1820225 | robot-detection
-M | n/a | ruby-sass (deprecated, use sassc - Debian 924629)
-M | TBD | sassc (Dep will be cut by Debian bug 924961)
-M | TBD | libsass (Dep will be cut by Debian bug 924961)
! | bug 1820226 | twitter-bootstrap3
! | bug 1820227 | uwsgi (FTBFS: #1820095)
! | bug 1820229 | wcwidth
*M | bug 1820232 | zeromq3 (FTBFS #1820282, demotion since 1597439?)
!TC | bug 1820233 | zope.component (version update)
!TC | bug 1820234 | zope.configuration (version update)
!TC | bug 1820236 | zope.event (version update)
!TC | bug 1820237 | zope.hookable (version update)
!TC | bug 1820238 | zope.i18nmessageid (version update)
*TC | bug 1820239 | zope.schema (version update)
List Debian bugs we depend on being resolved as expected before
the dependency tree can completely be MIRed:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924629
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924961
This might sometimes be slightly out of date, to cross check and for history on all of them check git at:
https://git.launchpad.net/~ubuntu-server/+git/mailman3-MIR-party/tree/package-list.txt
---
Past Decisions in regard to this:
mailman is python2, mailman3 is python3, but also it has new dependency stack due to adopting django but also splitting or rewriting a lot of its components.
Q: Do we want bin:mailman3 or bin:mailman3-full in main? (the latter pulls
in src:mailman-suite as well). src:mailman-suite has potentially more
things - django, hyperkitty, ruby-sass, uwsgi...
A: We analyzed this and we will need the full set of dependencies, even
meaning MIRs are needed for all of the above listed (and more).
Q: Before proceeding further with assignment/doing technical work in
driving above MIRs, a product level yes/no answers should probably be
answered for above two questions.
A: Discussed in several sprints now, as uncomfortable as it is we will go
through the mass-MIR processing |
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for https://lists.canonical.com/mailman3/postorius/lists/
This source builds only docs and mailman3 itself (which provides mailman3-core).
[Rationale]
This is part of the MIR activity for all dependencies of mailman3
The "main" MIR of it is at bug 1775427:
Mailman (2) has only python2 support, but we strive for python3,
therefore Mailman3 which has python3 support should be promoted to main.
This is an evolution of the mailman2 core delivery engine of the system, but I can't guess how much it deviated so we need to recheck security (IMHO)
[Security]
No known CVEs found.
A few old issues can be found against mailman2 and one (but long fixed) for mailman 3
=> https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=mailman
[Quality assurance]
The mailman3 stacks as of now (Disco) installs fine and provides a base
config. But due to the nature of the package that needs further modification
to be of real use.
The package does in error cases ask a debconf-high question, but it is not going to be installed by default - so that is no MIR problem.
There are a few (2) Ubuntu bugs outstanding, but none of them is critical and stopping this MIR request.
There are a few (2) Debian bugs outstanding all seems to "just work" still, but when we main this in 19.10 we should at least evaluate and maybe adress this one:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921445
There are regular upstream releases and Debian packages them and fixes regularly.
No exotic HW involved.
The package ships a test suite, but it is not run at build time for upstream bug #400.
It tests things in a dep8 test thou to provide coverage.
d/watch is set up and ok.
No Lintian warning except fairly recent newer Standards version.
The package does not rely on demoted or obsolete packages.
[UI standards]
Comes with 7 translations in .po files
No End-user applications that needs a standard conformant desktop file.
[Dependencies]
Some dependencies are not in main, but we drive MIR for all related packages
that are not in main at the same time.
Please check the list of bugs from the main Mailman3 MIR in bug 1775427 to get an overview.
[Standards compliance]
The package meets the FHS and Debian Policy standards.
The packaging itself is very straight forward and uses dh_* as much as possible - the d/rules fits on one screen.
[Maintenance]
The Server team will subscribe for the package for maintenance
[Background]
The package description explains the general purpose and context of the package well.
---
References to all the related MIR bug - one per affected package.
Status (simplified version of https://wiki.ubuntu.com/MIRTeam#Process_states)
(nothing) means we have not even prepared the MIR yet
- MIR not needed (e.g. dependency will be dropped)
* all of the template fields for the MIR are complete
! waiting for MIR review
? cpaelzer needs experienced MIR team members to continue
S needs security review to be accepted
+ MIR accepted
x MIR nacked
Extra Flags which team members or on review feedback can be added:
T extra work for the team that should be done before 20.04 (state todo after package)
M extra work for the team before getting MIR to be acceptable (read as asap)
C needed if only promoting mailman3 (core)
H needed if only promoting mailman3 (core) plus Hyperkitty
J no more needed for mailman3-web if we can cut node-less out
FLAGS | MIR-Bug | Package (Notes)
TC
MH
----------------------------------------
! | bug 1820179 | coreapi
! | bug 1820180 | coreschema
! | bug 1820181 | django-allauth
! | bug 1820182 | django-filter
! | bug 1820183 | django-guardian
! | bug 1820185 | django-haystack
! | bug 1820186 | django-mailman3
- | | django-paintstore ((no dep hyperkitty >=1.2.2-1)
! | bug 1820188 | django-picklefield
! | bug 1820189 | django-q
! | bug 1820190 | djangorestframework
! C | bug 1820191 | flufl.bounce
! C | bug 1820192 | flufl.i18n
! C | bug 1820193 | flufl.lock
! | bug 1820195 | glewlwyd
! | bug 1820196 | hyperkitty
! | bug 1820197 | itypes
- | n/a | jqueryui (no dep hyperkitty >=1.2.2-1)
! C | bug 1820199 | lazr.config
!TC | bug 1820200 | lazr.delegates (opt: update version before 20.04)
-MJ | bug 1820201 | less.js (Dep will be cut out in Debian bug 924961)
- | n/a | libjs-jquery-colorpicker (no hyperkitty >=1.2.2-1)
! | bug 1820202 | libmatheval
! | bug 1820203 | libpgm
! C | bug 1775427 | mailman3
! | bug 1820204 | mailmanclient
! H | bug 1820205 | mailman-hyperkitty
! | bug 1820206 | mailman-suite
-MJ | bug 1820207 | node-source-map (wait for node-less dep to be cut)
-MJ | bug 1820208 | nodejs (wait for node-less dep to be cut)
! | bug 1820209 | norm
-M | n/a | nose (important: drop dep from lazr.delegates)
! | bug 1820210 | postorius
! | bug 1820211 | python3-openid
! C | bug 1820212 | python-aiosmtpd
! | bug 1820213 | python-arrow
! | bug 1820214 | python-blessed
! | bug 1820215 | python-django-extensions
! | bug 1820216 | python-django-gravatar2
!TC | bug 1820217 | python-falcon (opt: update version before 20.04)
+ | bug 686045 | python-lockfile
!TC | bug 1820220 | python-public (opt: update version before 20.04)
! | bug 1820221 | python-requests-oauthlib
!T | bug 1820223 | python-uritemplate (feed delta back, be a sync)
! | bug 1820224 | python-whoosh
! | bug 1820225 | robot-detection
-M | n/a | ruby-sass (deprecated, use sassc - Debian 924629)
-M | TBD | sassc (Dep will be cut by Debian bug 924961)
-M | TBD | libsass (Dep will be cut by Debian bug 924961)
! | bug 1820226 | twitter-bootstrap3
! | bug 1820227 | uwsgi (FTBFS: #1820095)
! | bug 1820229 | wcwidth
*M | bug 1820232 | zeromq3 (FTBFS #1820282, demotion since 1597439?)
STC | bug 1820233 | zope.component (version update)
STC | bug 1820234 | zope.configuration (version update)
STC | bug 1820236 | zope.event (version update)
STC | bug 1820237 | zope.hookable (version update)
STC | bug 1820238 | zope.i18nmessageid (version update)
STC | bug 1820239 | zope.schema (version update)
List Debian bugs we depend on being resolved as expected before
the dependency tree can completely be MIRed:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924629
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924961
This might sometimes be slightly out of date, to cross check and for history on all of them check git at:
https://git.launchpad.net/~ubuntu-server/+git/mailman3-MIR-party/tree/package-list.txt
---
Past Decisions in regard to this:
mailman is python2, mailman3 is python3, but also it has new dependency stack due to adopting django but also splitting or rewriting a lot of its components.
Q: Do we want bin:mailman3 or bin:mailman3-full in main? (the latter pulls
in src:mailman-suite as well). src:mailman-suite has potentially more
things - django, hyperkitty, ruby-sass, uwsgi...
A: We analyzed this and we will need the full set of dependencies, even
meaning MIRs are needed for all of the above listed (and more).
Q: Before proceeding further with assignment/doing technical work in
driving above MIRs, a product level yes/no answers should probably be
answered for above two questions.
A: Discussed in several sprints now, as uncomfortable as it is we will go
through the mass-MIR processing |
|
| 2019-03-19 11:33:42 |
Christian Ehrhardt |
description |
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for https://lists.canonical.com/mailman3/postorius/lists/
This source builds only docs and mailman3 itself (which provides mailman3-core).
[Rationale]
This is part of the MIR activity for all dependencies of mailman3
The "main" MIR of it is at bug 1775427:
Mailman (2) has only python2 support, but we strive for python3,
therefore Mailman3 which has python3 support should be promoted to main.
This is an evolution of the mailman2 core delivery engine of the system, but I can't guess how much it deviated so we need to recheck security (IMHO)
[Security]
No known CVEs found.
A few old issues can be found against mailman2 and one (but long fixed) for mailman 3
=> https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=mailman
[Quality assurance]
The mailman3 stacks as of now (Disco) installs fine and provides a base
config. But due to the nature of the package that needs further modification
to be of real use.
The package does in error cases ask a debconf-high question, but it is not going to be installed by default - so that is no MIR problem.
There are a few (2) Ubuntu bugs outstanding, but none of them is critical and stopping this MIR request.
There are a few (2) Debian bugs outstanding all seems to "just work" still, but when we main this in 19.10 we should at least evaluate and maybe adress this one:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921445
There are regular upstream releases and Debian packages them and fixes regularly.
No exotic HW involved.
The package ships a test suite, but it is not run at build time for upstream bug #400.
It tests things in a dep8 test thou to provide coverage.
d/watch is set up and ok.
No Lintian warning except fairly recent newer Standards version.
The package does not rely on demoted or obsolete packages.
[UI standards]
Comes with 7 translations in .po files
No End-user applications that needs a standard conformant desktop file.
[Dependencies]
Some dependencies are not in main, but we drive MIR for all related packages
that are not in main at the same time.
Please check the list of bugs from the main Mailman3 MIR in bug 1775427 to get an overview.
[Standards compliance]
The package meets the FHS and Debian Policy standards.
The packaging itself is very straight forward and uses dh_* as much as possible - the d/rules fits on one screen.
[Maintenance]
The Server team will subscribe for the package for maintenance
[Background]
The package description explains the general purpose and context of the package well.
---
References to all the related MIR bug - one per affected package.
Status (simplified version of https://wiki.ubuntu.com/MIRTeam#Process_states)
(nothing) means we have not even prepared the MIR yet
- MIR not needed (e.g. dependency will be dropped)
* all of the template fields for the MIR are complete
! waiting for MIR review
? cpaelzer needs experienced MIR team members to continue
S needs security review to be accepted
+ MIR accepted
x MIR nacked
Extra Flags which team members or on review feedback can be added:
T extra work for the team that should be done before 20.04 (state todo after package)
M extra work for the team before getting MIR to be acceptable (read as asap)
C needed if only promoting mailman3 (core)
H needed if only promoting mailman3 (core) plus Hyperkitty
J no more needed for mailman3-web if we can cut node-less out
FLAGS | MIR-Bug | Package (Notes)
TC
MH
----------------------------------------
! | bug 1820179 | coreapi
! | bug 1820180 | coreschema
! | bug 1820181 | django-allauth
! | bug 1820182 | django-filter
! | bug 1820183 | django-guardian
! | bug 1820185 | django-haystack
! | bug 1820186 | django-mailman3
- | | django-paintstore ((no dep hyperkitty >=1.2.2-1)
! | bug 1820188 | django-picklefield
! | bug 1820189 | django-q
! | bug 1820190 | djangorestframework
! C | bug 1820191 | flufl.bounce
! C | bug 1820192 | flufl.i18n
! C | bug 1820193 | flufl.lock
! | bug 1820195 | glewlwyd
! | bug 1820196 | hyperkitty
! | bug 1820197 | itypes
- | n/a | jqueryui (no dep hyperkitty >=1.2.2-1)
! C | bug 1820199 | lazr.config
!TC | bug 1820200 | lazr.delegates (opt: update version before 20.04)
-MJ | bug 1820201 | less.js (Dep will be cut out in Debian bug 924961)
- | n/a | libjs-jquery-colorpicker (no hyperkitty >=1.2.2-1)
! | bug 1820202 | libmatheval
! | bug 1820203 | libpgm
! C | bug 1775427 | mailman3
! | bug 1820204 | mailmanclient
! H | bug 1820205 | mailman-hyperkitty
! | bug 1820206 | mailman-suite
-MJ | bug 1820207 | node-source-map (wait for node-less dep to be cut)
-MJ | bug 1820208 | nodejs (wait for node-less dep to be cut)
! | bug 1820209 | norm
-M | n/a | nose (important: drop dep from lazr.delegates)
! | bug 1820210 | postorius
! | bug 1820211 | python3-openid
! C | bug 1820212 | python-aiosmtpd
! | bug 1820213 | python-arrow
! | bug 1820214 | python-blessed
! | bug 1820215 | python-django-extensions
! | bug 1820216 | python-django-gravatar2
!TC | bug 1820217 | python-falcon (opt: update version before 20.04)
+ | bug 686045 | python-lockfile
!TC | bug 1820220 | python-public (opt: update version before 20.04)
! | bug 1820221 | python-requests-oauthlib
!T | bug 1820223 | python-uritemplate (feed delta back, be a sync)
! | bug 1820224 | python-whoosh
! | bug 1820225 | robot-detection
-M | n/a | ruby-sass (deprecated, use sassc - Debian 924629)
-M | TBD | sassc (Dep will be cut by Debian bug 924961)
-M | TBD | libsass (Dep will be cut by Debian bug 924961)
! | bug 1820226 | twitter-bootstrap3
! | bug 1820227 | uwsgi (FTBFS: #1820095)
! | bug 1820229 | wcwidth
*M | bug 1820232 | zeromq3 (FTBFS #1820282, demotion since 1597439?)
STC | bug 1820233 | zope.component (version update)
STC | bug 1820234 | zope.configuration (version update)
STC | bug 1820236 | zope.event (version update)
STC | bug 1820237 | zope.hookable (version update)
STC | bug 1820238 | zope.i18nmessageid (version update)
STC | bug 1820239 | zope.schema (version update)
List Debian bugs we depend on being resolved as expected before
the dependency tree can completely be MIRed:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924629
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924961
This might sometimes be slightly out of date, to cross check and for history on all of them check git at:
https://git.launchpad.net/~ubuntu-server/+git/mailman3-MIR-party/tree/package-list.txt
---
Past Decisions in regard to this:
mailman is python2, mailman3 is python3, but also it has new dependency stack due to adopting django but also splitting or rewriting a lot of its components.
Q: Do we want bin:mailman3 or bin:mailman3-full in main? (the latter pulls
in src:mailman-suite as well). src:mailman-suite has potentially more
things - django, hyperkitty, ruby-sass, uwsgi...
A: We analyzed this and we will need the full set of dependencies, even
meaning MIRs are needed for all of the above listed (and more).
Q: Before proceeding further with assignment/doing technical work in
driving above MIRs, a product level yes/no answers should probably be
answered for above two questions.
A: Discussed in several sprints now, as uncomfortable as it is we will go
through the mass-MIR processing |
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for https://lists.canonical.com/mailman3/postorius/lists/
This source builds only docs and mailman3 itself (which provides mailman3-core).
[Rationale]
This is part of the MIR activity for all dependencies of mailman3
The "main" MIR of it is at bug 1775427:
Mailman (2) has only python2 support, but we strive for python3,
therefore Mailman3 which has python3 support should be promoted to main.
This is an evolution of the mailman2 core delivery engine of the system, but I can't guess how much it deviated so we need to recheck security (IMHO)
[Security]
No known CVEs found.
A few old issues can be found against mailman2 and one (but long fixed) for mailman 3
=> https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=mailman
[Quality assurance]
The mailman3 stacks as of now (Disco) installs fine and provides a base
config. But due to the nature of the package that needs further modification
to be of real use.
The package does in error cases ask a debconf-high question, but it is not going to be installed by default - so that is no MIR problem.
There are a few (2) Ubuntu bugs outstanding, but none of them is critical and stopping this MIR request.
There are a few (2) Debian bugs outstanding all seems to "just work" still, but when we main this in 19.10 we should at least evaluate and maybe adress this one:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921445
There are regular upstream releases and Debian packages them and fixes regularly.
No exotic HW involved.
The package ships a test suite, but it is not run at build time for upstream bug #400.
It tests things in a dep8 test thou to provide coverage.
d/watch is set up and ok.
No Lintian warning except fairly recent newer Standards version.
The package does not rely on demoted or obsolete packages.
[UI standards]
Comes with 7 translations in .po files
No End-user applications that needs a standard conformant desktop file.
[Dependencies]
Some dependencies are not in main, but we drive MIR for all related packages
that are not in main at the same time.
Please check the list of bugs from the main Mailman3 MIR in bug 1775427 to get an overview.
[Standards compliance]
The package meets the FHS and Debian Policy standards.
The packaging itself is very straight forward and uses dh_* as much as possible - the d/rules fits on one screen.
[Maintenance]
The Server team will subscribe for the package for maintenance
[Background]
The package description explains the general purpose and context of the package well.
---
References to all the related MIR bug - one per affected package.
Status (simplified version of https://wiki.ubuntu.com/MIRTeam#Process_states)
(nothing) means we have not even prepared the MIR yet
- MIR not needed (e.g. dependency will be dropped)
* all of the template fields for the MIR are complete
! waiting for MIR review
? cpaelzer needs experienced MIR team members to continue
S needs security review to be accepted
+ MIR accepted
x MIR nacked
Extra Flags which team members or on review feedback can be added:
T extra work for the team that should be done before 20.04 (state todo after package)
M extra work for the team before getting MIR to be acceptable (read as asap)
C needed if only promoting mailman3 (core)
H needed if only promoting mailman3 (core) plus Hyperkitty
J no more needed for mailman3-web if we can cut node-less out
FLAGS | MIR-Bug | Package (Notes)
TC
MH
----------------------------------------
! | bug 1820179 | coreapi
! | bug 1820180 | coreschema
! | bug 1820181 | django-allauth
! | bug 1820182 | django-filter
! | bug 1820183 | django-guardian
! | bug 1820185 | django-haystack
! | bug 1820186 | django-mailman3
- | | django-paintstore ((no dep hyperkitty >=1.2.2-1)
! | bug 1820188 | django-picklefield
! | bug 1820189 | django-q
! | bug 1820190 | djangorestframework
S C | bug 1820191 | flufl.bounce
+ C | bug 1820192 | flufl.i18n
+ C | bug 1820193 | flufl.lock
! | bug 1820195 | glewlwyd
! | bug 1820196 | hyperkitty
! | bug 1820197 | itypes
- | n/a | jqueryui (no dep hyperkitty >=1.2.2-1)
+ C | bug 1820199 | lazr.config
+TC | bug 1820200 | lazr.delegates (opt: update version before 20.04)
-MJ | bug 1820201 | less.js (Dep will be cut out in Debian bug 924961)
- | n/a | libjs-jquery-colorpicker (no hyperkitty >=1.2.2-1)
! | bug 1820202 | libmatheval
! | bug 1820203 | libpgm
! C | bug 1775427 | mailman3
! | bug 1820204 | mailmanclient
! H | bug 1820205 | mailman-hyperkitty
! | bug 1820206 | mailman-suite
-MJ | bug 1820207 | node-source-map (wait for node-less dep to be cut)
-MJ | bug 1820208 | nodejs (wait for node-less dep to be cut)
! | bug 1820209 | norm
-M | n/a | nose (important: drop dep from lazr.delegates)
! | bug 1820210 | postorius
! | bug 1820211 | python3-openid
! C | bug 1820212 | python-aiosmtpd
! | bug 1820213 | python-arrow
! | bug 1820214 | python-blessed
! | bug 1820215 | python-django-extensions
! | bug 1820216 | python-django-gravatar2
!TC | bug 1820217 | python-falcon (opt: update version before 20.04)
+ | bug 686045 | python-lockfile
!TC | bug 1820220 | python-public (opt: update version before 20.04)
! | bug 1820221 | python-requests-oauthlib
!T | bug 1820223 | python-uritemplate (feed delta back, be a sync)
! | bug 1820224 | python-whoosh
! | bug 1820225 | robot-detection
-M | n/a | ruby-sass (deprecated, use sassc - Debian 924629)
-M | TBD | sassc (Dep will be cut by Debian bug 924961)
-M | TBD | libsass (Dep will be cut by Debian bug 924961)
! | bug 1820226 | twitter-bootstrap3
! | bug 1820227 | uwsgi (FTBFS: #1820095)
! | bug 1820229 | wcwidth
*M | bug 1820232 | zeromq3 (FTBFS #1820282, demotion since 1597439?)
STC | bug 1820233 | zope.component (version update)
STC | bug 1820234 | zope.configuration (version update)
STC | bug 1820236 | zope.event (version update)
STC | bug 1820237 | zope.hookable (version update)
STC | bug 1820238 | zope.i18nmessageid (version update)
STC | bug 1820239 | zope.schema (version update)
List Debian bugs we depend on being resolved as expected before
the dependency tree can completely be MIRed:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924629
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924961
This might sometimes be slightly out of date, to cross check and for history on all of them check git at:
https://git.launchpad.net/~ubuntu-server/+git/mailman3-MIR-party/tree/package-list.txt
---
Past Decisions in regard to this:
mailman is python2, mailman3 is python3, but also it has new dependency stack due to adopting django but also splitting or rewriting a lot of its components.
Q: Do we want bin:mailman3 or bin:mailman3-full in main? (the latter pulls
in src:mailman-suite as well). src:mailman-suite has potentially more
things - django, hyperkitty, ruby-sass, uwsgi...
A: We analyzed this and we will need the full set of dependencies, even
meaning MIRs are needed for all of the above listed (and more).
Q: Before proceeding further with assignment/doing technical work in
driving above MIRs, a product level yes/no answers should probably be
answered for above two questions.
A: Discussed in several sprints now, as uncomfortable as it is we will go
through the mass-MIR processing |
|
| 2019-03-20 12:29:41 |
Christian Ehrhardt |
description |
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for https://lists.canonical.com/mailman3/postorius/lists/
This source builds only docs and mailman3 itself (which provides mailman3-core).
[Rationale]
This is part of the MIR activity for all dependencies of mailman3
The "main" MIR of it is at bug 1775427:
Mailman (2) has only python2 support, but we strive for python3,
therefore Mailman3 which has python3 support should be promoted to main.
This is an evolution of the mailman2 core delivery engine of the system, but I can't guess how much it deviated so we need to recheck security (IMHO)
[Security]
No known CVEs found.
A few old issues can be found against mailman2 and one (but long fixed) for mailman 3
=> https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=mailman
[Quality assurance]
The mailman3 stacks as of now (Disco) installs fine and provides a base
config. But due to the nature of the package that needs further modification
to be of real use.
The package does in error cases ask a debconf-high question, but it is not going to be installed by default - so that is no MIR problem.
There are a few (2) Ubuntu bugs outstanding, but none of them is critical and stopping this MIR request.
There are a few (2) Debian bugs outstanding all seems to "just work" still, but when we main this in 19.10 we should at least evaluate and maybe adress this one:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921445
There are regular upstream releases and Debian packages them and fixes regularly.
No exotic HW involved.
The package ships a test suite, but it is not run at build time for upstream bug #400.
It tests things in a dep8 test thou to provide coverage.
d/watch is set up and ok.
No Lintian warning except fairly recent newer Standards version.
The package does not rely on demoted or obsolete packages.
[UI standards]
Comes with 7 translations in .po files
No End-user applications that needs a standard conformant desktop file.
[Dependencies]
Some dependencies are not in main, but we drive MIR for all related packages
that are not in main at the same time.
Please check the list of bugs from the main Mailman3 MIR in bug 1775427 to get an overview.
[Standards compliance]
The package meets the FHS and Debian Policy standards.
The packaging itself is very straight forward and uses dh_* as much as possible - the d/rules fits on one screen.
[Maintenance]
The Server team will subscribe for the package for maintenance
[Background]
The package description explains the general purpose and context of the package well.
---
References to all the related MIR bug - one per affected package.
Status (simplified version of https://wiki.ubuntu.com/MIRTeam#Process_states)
(nothing) means we have not even prepared the MIR yet
- MIR not needed (e.g. dependency will be dropped)
* all of the template fields for the MIR are complete
! waiting for MIR review
? cpaelzer needs experienced MIR team members to continue
S needs security review to be accepted
+ MIR accepted
x MIR nacked
Extra Flags which team members or on review feedback can be added:
T extra work for the team that should be done before 20.04 (state todo after package)
M extra work for the team before getting MIR to be acceptable (read as asap)
C needed if only promoting mailman3 (core)
H needed if only promoting mailman3 (core) plus Hyperkitty
J no more needed for mailman3-web if we can cut node-less out
FLAGS | MIR-Bug | Package (Notes)
TC
MH
----------------------------------------
! | bug 1820179 | coreapi
! | bug 1820180 | coreschema
! | bug 1820181 | django-allauth
! | bug 1820182 | django-filter
! | bug 1820183 | django-guardian
! | bug 1820185 | django-haystack
! | bug 1820186 | django-mailman3
- | | django-paintstore ((no dep hyperkitty >=1.2.2-1)
! | bug 1820188 | django-picklefield
! | bug 1820189 | django-q
! | bug 1820190 | djangorestframework
S C | bug 1820191 | flufl.bounce
+ C | bug 1820192 | flufl.i18n
+ C | bug 1820193 | flufl.lock
! | bug 1820195 | glewlwyd
! | bug 1820196 | hyperkitty
! | bug 1820197 | itypes
- | n/a | jqueryui (no dep hyperkitty >=1.2.2-1)
+ C | bug 1820199 | lazr.config
+TC | bug 1820200 | lazr.delegates (opt: update version before 20.04)
-MJ | bug 1820201 | less.js (Dep will be cut out in Debian bug 924961)
- | n/a | libjs-jquery-colorpicker (no hyperkitty >=1.2.2-1)
! | bug 1820202 | libmatheval
! | bug 1820203 | libpgm
! C | bug 1775427 | mailman3
! | bug 1820204 | mailmanclient
! H | bug 1820205 | mailman-hyperkitty
! | bug 1820206 | mailman-suite
-MJ | bug 1820207 | node-source-map (wait for node-less dep to be cut)
-MJ | bug 1820208 | nodejs (wait for node-less dep to be cut)
! | bug 1820209 | norm
-M | n/a | nose (important: drop dep from lazr.delegates)
! | bug 1820210 | postorius
! | bug 1820211 | python3-openid
! C | bug 1820212 | python-aiosmtpd
! | bug 1820213 | python-arrow
! | bug 1820214 | python-blessed
! | bug 1820215 | python-django-extensions
! | bug 1820216 | python-django-gravatar2
!TC | bug 1820217 | python-falcon (opt: update version before 20.04)
+ | bug 686045 | python-lockfile
!TC | bug 1820220 | python-public (opt: update version before 20.04)
! | bug 1820221 | python-requests-oauthlib
!T | bug 1820223 | python-uritemplate (feed delta back, be a sync)
! | bug 1820224 | python-whoosh
! | bug 1820225 | robot-detection
-M | n/a | ruby-sass (deprecated, use sassc - Debian 924629)
-M | TBD | sassc (Dep will be cut by Debian bug 924961)
-M | TBD | libsass (Dep will be cut by Debian bug 924961)
! | bug 1820226 | twitter-bootstrap3
! | bug 1820227 | uwsgi (FTBFS: #1820095)
! | bug 1820229 | wcwidth
*M | bug 1820232 | zeromq3 (FTBFS #1820282, demotion since 1597439?)
STC | bug 1820233 | zope.component (version update)
STC | bug 1820234 | zope.configuration (version update)
STC | bug 1820236 | zope.event (version update)
STC | bug 1820237 | zope.hookable (version update)
STC | bug 1820238 | zope.i18nmessageid (version update)
STC | bug 1820239 | zope.schema (version update)
List Debian bugs we depend on being resolved as expected before
the dependency tree can completely be MIRed:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924629
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924961
This might sometimes be slightly out of date, to cross check and for history on all of them check git at:
https://git.launchpad.net/~ubuntu-server/+git/mailman3-MIR-party/tree/package-list.txt
---
Past Decisions in regard to this:
mailman is python2, mailman3 is python3, but also it has new dependency stack due to adopting django but also splitting or rewriting a lot of its components.
Q: Do we want bin:mailman3 or bin:mailman3-full in main? (the latter pulls
in src:mailman-suite as well). src:mailman-suite has potentially more
things - django, hyperkitty, ruby-sass, uwsgi...
A: We analyzed this and we will need the full set of dependencies, even
meaning MIRs are needed for all of the above listed (and more).
Q: Before proceeding further with assignment/doing technical work in
driving above MIRs, a product level yes/no answers should probably be
answered for above two questions.
A: Discussed in several sprints now, as uncomfortable as it is we will go
through the mass-MIR processing |
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for https://lists.canonical.com/mailman3/postorius/lists/
This source builds only docs and mailman3 itself (which provides mailman3-core).
[Rationale]
This is part of the MIR activity for all dependencies of mailman3
The "main" MIR of it is at bug 1775427:
Mailman (2) has only python2 support, but we strive for python3,
therefore Mailman3 which has python3 support should be promoted to main.
This is an evolution of the mailman2 core delivery engine of the system, but I can't guess how much it deviated so we need to recheck security (IMHO)
[Security]
No known CVEs found.
A few old issues can be found against mailman2 and one (but long fixed) for mailman 3
=> https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=mailman
[Quality assurance]
The mailman3 stacks as of now (Disco) installs fine and provides a base
config. But due to the nature of the package that needs further modification
to be of real use.
The package does in error cases ask a debconf-high question, but it is not going to be installed by default - so that is no MIR problem.
There are a few (2) Ubuntu bugs outstanding, but none of them is critical and stopping this MIR request.
There are a few (2) Debian bugs outstanding all seems to "just work" still, but when we main this in 19.10 we should at least evaluate and maybe adress this one:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921445
There are regular upstream releases and Debian packages them and fixes regularly.
No exotic HW involved.
The package ships a test suite, but it is not run at build time for upstream bug #400.
It tests things in a dep8 test thou to provide coverage.
d/watch is set up and ok.
No Lintian warning except fairly recent newer Standards version.
The package does not rely on demoted or obsolete packages.
[UI standards]
Comes with 7 translations in .po files
No End-user applications that needs a standard conformant desktop file.
[Dependencies]
Some dependencies are not in main, but we drive MIR for all related packages
that are not in main at the same time.
Please check the list of bugs from the main Mailman3 MIR in bug 1775427 to get an overview.
[Standards compliance]
The package meets the FHS and Debian Policy standards.
The packaging itself is very straight forward and uses dh_* as much as possible - the d/rules fits on one screen.
[Maintenance]
The Server team will subscribe for the package for maintenance
[Background]
The package description explains the general purpose and context of the package well.
---
References to all the related MIR bug - one per affected package.
Status (simplified version of https://wiki.ubuntu.com/MIRTeam#Process_states)
(nothing) means we have not even prepared the MIR yet
- MIR not needed (e.g. dependency will be dropped)
* all of the template fields for the MIR are complete
! waiting for MIR review
? cpaelzer needs experienced MIR team members to continue
S needs security review to be accepted
+ MIR accepted
x MIR nacked
Extra Flags which team members or on review feedback can be added:
T extra work for the team that should be done before 20.04 (state todo after package)
M extra work for the team before getting MIR to be acceptable (read as asap)
C needed if only promoting mailman3 (core)
H needed if only promoting mailman3 (core) plus Hyperkitty
J no more needed for mailman3-web if we can cut node-less out
FLAGS | MIR-Bug | Package (Notes)
TC
MH
----------------------------------------
! | bug 1820179 | coreapi
! | bug 1820180 | coreschema
S | bug 1820181 | django-allauth
+ | bug 1820182 | django-filter
S | bug 1820183 | django-guardian
+ | bug 1820185 | django-haystack
S | bug 1820186 | django-mailman3
- | | django-paintstore ((no dep hyperkitty >=1.2.2-1)
+ | bug 1820188 | django-picklefield
+ | bug 1820189 | django-q
S | bug 1820190 | djangorestframework
S C | bug 1820191 | flufl.bounce
+ C | bug 1820192 | flufl.i18n
+ C | bug 1820193 | flufl.lock
! | bug 1820195 | glewlwyd
! | bug 1820196 | hyperkitty
! | bug 1820197 | itypes
- | n/a | jqueryui (no dep hyperkitty >=1.2.2-1)
+ C | bug 1820199 | lazr.config
+TC | bug 1820200 | lazr.delegates (opt: update; suggest dropping nose)
-MJ | bug 1820201 | less.js (Dep will be cut out in Debian bug 924961)
- | n/a | libjs-jquery-colorpicker (no hyperkitty >=1.2.2-1)
! | bug 1820202 | libmatheval
! | bug 1820203 | libpgm
! C | bug 1775427 | mailman3
! | bug 1820204 | mailmanclient
! H | bug 1820205 | mailman-hyperkitty
! | bug 1820206 | mailman-suite
-MJ | bug 1820207 | node-source-map (wait for node-less dep to be cut)
-MJ | bug 1820208 | nodejs (wait for node-less dep to be cut)
! | bug 1820209 | norm
+ | bug 1820982 | nose
! | bug 1820210 | postorius
! | bug 1820211 | python3-openid
! C | bug 1820212 | python-aiosmtpd
! | bug 1820213 | python-arrow
! | bug 1820214 | python-blessed
! | bug 1820215 | python-django-extensions
! | bug 1820216 | python-django-gravatar2
!TC | bug 1820217 | python-falcon (opt: update version before 20.04)
+ | bug 686045 | python-lockfile
!TC | bug 1820220 | python-public (opt: update version before 20.04)
! | bug 1820221 | python-requests-oauthlib
!T | bug 1820223 | python-uritemplate (feed delta back, be a sync)
! | bug 1820224 | python-whoosh
! | bug 1820225 | robot-detection
-M | n/a | ruby-sass (deprecated, use sassc - Debian 924629)
-M | TBD | sassc (Dep will be cut by Debian bug 924961)
-M | TBD | libsass (Dep will be cut by Debian bug 924961)
? | bug 1820226 | twitter-bootstrap3
? | bug 1820227 | uwsgi (FTBFS: #1820095)
! | bug 1820229 | wcwidth
*M | bug 1820232 | zeromq3 (FTBFS #1820282, demotion since 1597439?)
STC | bug 1820233 | zope.component (version update)
STC | bug 1820234 | zope.configuration (version update)
STC | bug 1820236 | zope.event (version update)
STC | bug 1820237 | zope.hookable (version update)
STC | bug 1820238 | zope.i18nmessageid (version update)
STC | bug 1820239 | zope.schema (version update)
List Debian bugs we depend on being resolved as expected before
the dependency tree can completely be MIRed:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924629
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924961
This might sometimes be slightly out of date, to cross check and for history on all of them check git at:
https://git.launchpad.net/~ubuntu-server/+git/mailman3-MIR-party/tree/package-list.txt
---
Past Decisions in regard to this:
mailman is python2, mailman3 is python3, but also it has new dependency stack due to adopting django but also splitting or rewriting a lot of its components.
Q: Do we want bin:mailman3 or bin:mailman3-full in main? (the latter pulls
in src:mailman-suite as well). src:mailman-suite has potentially more
things - django, hyperkitty, ruby-sass, uwsgi...
A: We analyzed this and we will need the full set of dependencies, even
meaning MIRs are needed for all of the above listed (and more).
Q: Before proceeding further with assignment/doing technical work in
driving above MIRs, a product level yes/no answers should probably be
answered for above two questions.
A: Discussed in several sprints now, as uncomfortable as it is we will go
through the mass-MIR processing |
|
| 2019-03-20 13:32:34 |
Christian Ehrhardt |
description |
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for https://lists.canonical.com/mailman3/postorius/lists/
This source builds only docs and mailman3 itself (which provides mailman3-core).
[Rationale]
This is part of the MIR activity for all dependencies of mailman3
The "main" MIR of it is at bug 1775427:
Mailman (2) has only python2 support, but we strive for python3,
therefore Mailman3 which has python3 support should be promoted to main.
This is an evolution of the mailman2 core delivery engine of the system, but I can't guess how much it deviated so we need to recheck security (IMHO)
[Security]
No known CVEs found.
A few old issues can be found against mailman2 and one (but long fixed) for mailman 3
=> https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=mailman
[Quality assurance]
The mailman3 stacks as of now (Disco) installs fine and provides a base
config. But due to the nature of the package that needs further modification
to be of real use.
The package does in error cases ask a debconf-high question, but it is not going to be installed by default - so that is no MIR problem.
There are a few (2) Ubuntu bugs outstanding, but none of them is critical and stopping this MIR request.
There are a few (2) Debian bugs outstanding all seems to "just work" still, but when we main this in 19.10 we should at least evaluate and maybe adress this one:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921445
There are regular upstream releases and Debian packages them and fixes regularly.
No exotic HW involved.
The package ships a test suite, but it is not run at build time for upstream bug #400.
It tests things in a dep8 test thou to provide coverage.
d/watch is set up and ok.
No Lintian warning except fairly recent newer Standards version.
The package does not rely on demoted or obsolete packages.
[UI standards]
Comes with 7 translations in .po files
No End-user applications that needs a standard conformant desktop file.
[Dependencies]
Some dependencies are not in main, but we drive MIR for all related packages
that are not in main at the same time.
Please check the list of bugs from the main Mailman3 MIR in bug 1775427 to get an overview.
[Standards compliance]
The package meets the FHS and Debian Policy standards.
The packaging itself is very straight forward and uses dh_* as much as possible - the d/rules fits on one screen.
[Maintenance]
The Server team will subscribe for the package for maintenance
[Background]
The package description explains the general purpose and context of the package well.
---
References to all the related MIR bug - one per affected package.
Status (simplified version of https://wiki.ubuntu.com/MIRTeam#Process_states)
(nothing) means we have not even prepared the MIR yet
- MIR not needed (e.g. dependency will be dropped)
* all of the template fields for the MIR are complete
! waiting for MIR review
? cpaelzer needs experienced MIR team members to continue
S needs security review to be accepted
+ MIR accepted
x MIR nacked
Extra Flags which team members or on review feedback can be added:
T extra work for the team that should be done before 20.04 (state todo after package)
M extra work for the team before getting MIR to be acceptable (read as asap)
C needed if only promoting mailman3 (core)
H needed if only promoting mailman3 (core) plus Hyperkitty
J no more needed for mailman3-web if we can cut node-less out
FLAGS | MIR-Bug | Package (Notes)
TC
MH
----------------------------------------
! | bug 1820179 | coreapi
! | bug 1820180 | coreschema
S | bug 1820181 | django-allauth
+ | bug 1820182 | django-filter
S | bug 1820183 | django-guardian
+ | bug 1820185 | django-haystack
S | bug 1820186 | django-mailman3
- | | django-paintstore ((no dep hyperkitty >=1.2.2-1)
+ | bug 1820188 | django-picklefield
+ | bug 1820189 | django-q
S | bug 1820190 | djangorestframework
S C | bug 1820191 | flufl.bounce
+ C | bug 1820192 | flufl.i18n
+ C | bug 1820193 | flufl.lock
! | bug 1820195 | glewlwyd
! | bug 1820196 | hyperkitty
! | bug 1820197 | itypes
- | n/a | jqueryui (no dep hyperkitty >=1.2.2-1)
+ C | bug 1820199 | lazr.config
+TC | bug 1820200 | lazr.delegates (opt: update; suggest dropping nose)
-MJ | bug 1820201 | less.js (Dep will be cut out in Debian bug 924961)
- | n/a | libjs-jquery-colorpicker (no hyperkitty >=1.2.2-1)
! | bug 1820202 | libmatheval
! | bug 1820203 | libpgm
! C | bug 1775427 | mailman3
! | bug 1820204 | mailmanclient
! H | bug 1820205 | mailman-hyperkitty
! | bug 1820206 | mailman-suite
-MJ | bug 1820207 | node-source-map (wait for node-less dep to be cut)
-MJ | bug 1820208 | nodejs (wait for node-less dep to be cut)
! | bug 1820209 | norm
+ | bug 1820982 | nose
! | bug 1820210 | postorius
! | bug 1820211 | python3-openid
! C | bug 1820212 | python-aiosmtpd
! | bug 1820213 | python-arrow
! | bug 1820214 | python-blessed
! | bug 1820215 | python-django-extensions
! | bug 1820216 | python-django-gravatar2
!TC | bug 1820217 | python-falcon (opt: update version before 20.04)
+ | bug 686045 | python-lockfile
!TC | bug 1820220 | python-public (opt: update version before 20.04)
! | bug 1820221 | python-requests-oauthlib
!T | bug 1820223 | python-uritemplate (feed delta back, be a sync)
! | bug 1820224 | python-whoosh
! | bug 1820225 | robot-detection
-M | n/a | ruby-sass (deprecated, use sassc - Debian 924629)
-M | TBD | sassc (Dep will be cut by Debian bug 924961)
-M | TBD | libsass (Dep will be cut by Debian bug 924961)
? | bug 1820226 | twitter-bootstrap3
? | bug 1820227 | uwsgi (FTBFS: #1820095)
! | bug 1820229 | wcwidth
*M | bug 1820232 | zeromq3 (FTBFS #1820282, demotion since 1597439?)
STC | bug 1820233 | zope.component (version update)
STC | bug 1820234 | zope.configuration (version update)
STC | bug 1820236 | zope.event (version update)
STC | bug 1820237 | zope.hookable (version update)
STC | bug 1820238 | zope.i18nmessageid (version update)
STC | bug 1820239 | zope.schema (version update)
List Debian bugs we depend on being resolved as expected before
the dependency tree can completely be MIRed:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924629
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924961
This might sometimes be slightly out of date, to cross check and for history on all of them check git at:
https://git.launchpad.net/~ubuntu-server/+git/mailman3-MIR-party/tree/package-list.txt
---
Past Decisions in regard to this:
mailman is python2, mailman3 is python3, but also it has new dependency stack due to adopting django but also splitting or rewriting a lot of its components.
Q: Do we want bin:mailman3 or bin:mailman3-full in main? (the latter pulls
in src:mailman-suite as well). src:mailman-suite has potentially more
things - django, hyperkitty, ruby-sass, uwsgi...
A: We analyzed this and we will need the full set of dependencies, even
meaning MIRs are needed for all of the above listed (and more).
Q: Before proceeding further with assignment/doing technical work in
driving above MIRs, a product level yes/no answers should probably be
answered for above two questions.
A: Discussed in several sprints now, as uncomfortable as it is we will go
through the mass-MIR processing |
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for https://lists.canonical.com/mailman3/postorius/lists/
This source builds only docs and mailman3 itself (which provides mailman3-core).
[Rationale]
This is part of the MIR activity for all dependencies of mailman3
The "main" MIR of it is at bug 1775427:
Mailman (2) has only python2 support, but we strive for python3,
therefore Mailman3 which has python3 support should be promoted to main.
This is an evolution of the mailman2 core delivery engine of the system, but I can't guess how much it deviated so we need to recheck security (IMHO)
[Security]
No known CVEs found.
A few old issues can be found against mailman2 and one (but long fixed) for mailman 3
=> https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=mailman
[Quality assurance]
The mailman3 stacks as of now (Disco) installs fine and provides a base
config. But due to the nature of the package that needs further modification
to be of real use.
The package does in error cases ask a debconf-high question, but it is not going to be installed by default - so that is no MIR problem.
There are a few (2) Ubuntu bugs outstanding, but none of them is critical and stopping this MIR request.
There are a few (2) Debian bugs outstanding all seems to "just work" still, but when we main this in 19.10 we should at least evaluate and maybe adress this one:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921445
There are regular upstream releases and Debian packages them and fixes regularly.
No exotic HW involved.
The package ships a test suite, but it is not run at build time for upstream bug #400.
It tests things in a dep8 test thou to provide coverage.
d/watch is set up and ok.
No Lintian warning except fairly recent newer Standards version.
The package does not rely on demoted or obsolete packages.
[UI standards]
Comes with 7 translations in .po files
No End-user applications that needs a standard conformant desktop file.
[Dependencies]
Some dependencies are not in main, but we drive MIR for all related packages
that are not in main at the same time.
Please check the list of bugs from the main Mailman3 MIR in bug 1775427 to get an overview.
[Standards compliance]
The package meets the FHS and Debian Policy standards.
The packaging itself is very straight forward and uses dh_* as much as possible - the d/rules fits on one screen.
[Maintenance]
The Server team will subscribe for the package for maintenance
[Background]
The package description explains the general purpose and context of the package well.
---
References to all the related MIR bug - one per affected package.
Status (simplified version of https://wiki.ubuntu.com/MIRTeam#Process_states)
(nothing) means we have not even prepared the MIR yet
- MIR not needed (e.g. dependency will be dropped)
* all of the template fields for the MIR are complete
! waiting for MIR review
? cpaelzer needs experienced MIR team members to continue
S needs security review to be accepted
+ MIR accepted
x MIR nacked
Extra Flags which team members or on review feedback can be added:
T extra work for the team that should be done before 20.04 (state todo after package)
M extra work for the team before getting MIR to be acceptable (read as asap)
C needed if only promoting mailman3 (core)
H needed if only promoting mailman3 (core) plus Hyperkitty
J no more needed for mailman3-web if we can cut node-less out
FLAGS | MIR-Bug | Package (Notes)
TC
MH
----------------------------------------
! | bug 1820179 | coreapi
! | bug 1820180 | coreschema
S | bug 1820181 | django-allauth
+ | bug 1820182 | django-filter
S | bug 1820183 | django-guardian
+ | bug 1820185 | django-haystack
S | bug 1820186 | django-mailman3
- | | django-paintstore ((no dep hyperkitty >=1.2.2-1)
+ | bug 1820188 | django-picklefield
+ | bug 1820189 | django-q
S | bug 1820190 | djangorestframework
S C | bug 1820191 | flufl.bounce
+ C | bug 1820192 | flufl.i18n
+ C | bug 1820193 | flufl.lock
! | bug 1820195 | glewlwyd
! | bug 1820196 | hyperkitty
! | bug 1820197 | itypes
- | n/a | jqueryui (no dep hyperkitty >=1.2.2-1)
+ C | bug 1820199 | lazr.config
+TC | bug 1820200 | lazr.delegates (opt: update; suggest dropping nose)
-MJ | bug 1820201 | less.js (Dep will be cut out in Debian bug 924961)
- | n/a | libjs-jquery-colorpicker (no hyperkitty >=1.2.2-1)
! | bug 1820202 | libmatheval
! | bug 1820203 | libpgm
! C | bug 1775427 | mailman3
! | bug 1820204 | mailmanclient
! H | bug 1820205 | mailman-hyperkitty
! | bug 1820206 | mailman-suite
-MJ | bug 1820207 | node-source-map (wait for node-less dep to be cut)
-MJ | bug 1820208 | nodejs (wait for node-less dep to be cut)
! | bug 1820209 | norm
+ | bug 1820982 | nose
! | bug 1820210 | postorius
! | bug 1820211 | python3-openid
! C | bug 1820212 | python-aiosmtpd
! | bug 1820213 | python-arrow
! | bug 1820214 | python-blessed
! | bug 1820215 | python-django-extensions
! | bug 1820216 | python-django-gravatar2
!TC | bug 1820217 | python-falcon (opt: update version before 20.04)
+ | bug 686045 | python-lockfile
!TC | bug 1820220 | python-public (opt: update version before 20.04)
! | bug 1820221 | python-requests-oauthlib
!T | bug 1820223 | python-uritemplate (feed delta back, be a sync)
! | bug 1820224 | python-whoosh
! | bug 1820225 | robot-detection
-M | n/a | ruby-sass (deprecated, use sassc - Debian 924629)
-M | TBD | sassc (Dep will be cut by Debian bug 924961)
-M | TBD | libsass (Dep will be cut by Debian bug 924961)
? | bug 1820226 | twitter-bootstrap3
? | bug 1820227 | uwsgi (FTBFS: #1820095)
! | bug 1820229 | wcwidth
+ | bug 1597439 | zeromq3
STC | bug 1820233 | zope.component (version update)
STC | bug 1820234 | zope.configuration (version update)
STC | bug 1820236 | zope.event (version update)
STC | bug 1820237 | zope.hookable (version update)
STC | bug 1820238 | zope.i18nmessageid (version update)
STC | bug 1820239 | zope.schema (version update)
List Debian bugs we depend on being resolved as expected before
the dependency tree can completely be MIRed:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924629
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924961
This might sometimes be slightly out of date, to cross check and for history on all of them check git at:
https://git.launchpad.net/~ubuntu-server/+git/mailman3-MIR-party/tree/package-list.txt
---
Past Decisions in regard to this:
mailman is python2, mailman3 is python3, but also it has new dependency stack due to adopting django but also splitting or rewriting a lot of its components.
Q: Do we want bin:mailman3 or bin:mailman3-full in main? (the latter pulls
in src:mailman-suite as well). src:mailman-suite has potentially more
things - django, hyperkitty, ruby-sass, uwsgi...
A: We analyzed this and we will need the full set of dependencies, even
meaning MIRs are needed for all of the above listed (and more).
Q: Before proceeding further with assignment/doing technical work in
driving above MIRs, a product level yes/no answers should probably be
answered for above two questions.
A: Discussed in several sprints now, as uncomfortable as it is we will go
through the mass-MIR processing |
|
| 2019-03-20 14:14:42 |
Christian Ehrhardt |
description |
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for https://lists.canonical.com/mailman3/postorius/lists/
This source builds only docs and mailman3 itself (which provides mailman3-core).
[Rationale]
This is part of the MIR activity for all dependencies of mailman3
The "main" MIR of it is at bug 1775427:
Mailman (2) has only python2 support, but we strive for python3,
therefore Mailman3 which has python3 support should be promoted to main.
This is an evolution of the mailman2 core delivery engine of the system, but I can't guess how much it deviated so we need to recheck security (IMHO)
[Security]
No known CVEs found.
A few old issues can be found against mailman2 and one (but long fixed) for mailman 3
=> https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=mailman
[Quality assurance]
The mailman3 stacks as of now (Disco) installs fine and provides a base
config. But due to the nature of the package that needs further modification
to be of real use.
The package does in error cases ask a debconf-high question, but it is not going to be installed by default - so that is no MIR problem.
There are a few (2) Ubuntu bugs outstanding, but none of them is critical and stopping this MIR request.
There are a few (2) Debian bugs outstanding all seems to "just work" still, but when we main this in 19.10 we should at least evaluate and maybe adress this one:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921445
There are regular upstream releases and Debian packages them and fixes regularly.
No exotic HW involved.
The package ships a test suite, but it is not run at build time for upstream bug #400.
It tests things in a dep8 test thou to provide coverage.
d/watch is set up and ok.
No Lintian warning except fairly recent newer Standards version.
The package does not rely on demoted or obsolete packages.
[UI standards]
Comes with 7 translations in .po files
No End-user applications that needs a standard conformant desktop file.
[Dependencies]
Some dependencies are not in main, but we drive MIR for all related packages
that are not in main at the same time.
Please check the list of bugs from the main Mailman3 MIR in bug 1775427 to get an overview.
[Standards compliance]
The package meets the FHS and Debian Policy standards.
The packaging itself is very straight forward and uses dh_* as much as possible - the d/rules fits on one screen.
[Maintenance]
The Server team will subscribe for the package for maintenance
[Background]
The package description explains the general purpose and context of the package well.
---
References to all the related MIR bug - one per affected package.
Status (simplified version of https://wiki.ubuntu.com/MIRTeam#Process_states)
(nothing) means we have not even prepared the MIR yet
- MIR not needed (e.g. dependency will be dropped)
* all of the template fields for the MIR are complete
! waiting for MIR review
? cpaelzer needs experienced MIR team members to continue
S needs security review to be accepted
+ MIR accepted
x MIR nacked
Extra Flags which team members or on review feedback can be added:
T extra work for the team that should be done before 20.04 (state todo after package)
M extra work for the team before getting MIR to be acceptable (read as asap)
C needed if only promoting mailman3 (core)
H needed if only promoting mailman3 (core) plus Hyperkitty
J no more needed for mailman3-web if we can cut node-less out
FLAGS | MIR-Bug | Package (Notes)
TC
MH
----------------------------------------
! | bug 1820179 | coreapi
! | bug 1820180 | coreschema
S | bug 1820181 | django-allauth
+ | bug 1820182 | django-filter
S | bug 1820183 | django-guardian
+ | bug 1820185 | django-haystack
S | bug 1820186 | django-mailman3
- | | django-paintstore ((no dep hyperkitty >=1.2.2-1)
+ | bug 1820188 | django-picklefield
+ | bug 1820189 | django-q
S | bug 1820190 | djangorestframework
S C | bug 1820191 | flufl.bounce
+ C | bug 1820192 | flufl.i18n
+ C | bug 1820193 | flufl.lock
! | bug 1820195 | glewlwyd
! | bug 1820196 | hyperkitty
! | bug 1820197 | itypes
- | n/a | jqueryui (no dep hyperkitty >=1.2.2-1)
+ C | bug 1820199 | lazr.config
+TC | bug 1820200 | lazr.delegates (opt: update; suggest dropping nose)
-MJ | bug 1820201 | less.js (Dep will be cut out in Debian bug 924961)
- | n/a | libjs-jquery-colorpicker (no hyperkitty >=1.2.2-1)
! | bug 1820202 | libmatheval
! | bug 1820203 | libpgm
! C | bug 1775427 | mailman3
! | bug 1820204 | mailmanclient
! H | bug 1820205 | mailman-hyperkitty
! | bug 1820206 | mailman-suite
-MJ | bug 1820207 | node-source-map (wait for node-less dep to be cut)
-MJ | bug 1820208 | nodejs (wait for node-less dep to be cut)
! | bug 1820209 | norm
+ | bug 1820982 | nose
! | bug 1820210 | postorius
! | bug 1820211 | python3-openid
! C | bug 1820212 | python-aiosmtpd
! | bug 1820213 | python-arrow
! | bug 1820214 | python-blessed
! | bug 1820215 | python-django-extensions
! | bug 1820216 | python-django-gravatar2
!TC | bug 1820217 | python-falcon (opt: update version before 20.04)
+ | bug 686045 | python-lockfile
!TC | bug 1820220 | python-public (opt: update version before 20.04)
! | bug 1820221 | python-requests-oauthlib
!T | bug 1820223 | python-uritemplate (feed delta back, be a sync)
! | bug 1820224 | python-whoosh
! | bug 1820225 | robot-detection
-M | n/a | ruby-sass (deprecated, use sassc - Debian 924629)
-M | TBD | sassc (Dep will be cut by Debian bug 924961)
-M | TBD | libsass (Dep will be cut by Debian bug 924961)
? | bug 1820226 | twitter-bootstrap3
? | bug 1820227 | uwsgi (FTBFS: #1820095)
! | bug 1820229 | wcwidth
+ | bug 1597439 | zeromq3
STC | bug 1820233 | zope.component (version update)
STC | bug 1820234 | zope.configuration (version update)
STC | bug 1820236 | zope.event (version update)
STC | bug 1820237 | zope.hookable (version update)
STC | bug 1820238 | zope.i18nmessageid (version update)
STC | bug 1820239 | zope.schema (version update)
List Debian bugs we depend on being resolved as expected before
the dependency tree can completely be MIRed:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924629
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924961
This might sometimes be slightly out of date, to cross check and for history on all of them check git at:
https://git.launchpad.net/~ubuntu-server/+git/mailman3-MIR-party/tree/package-list.txt
---
Past Decisions in regard to this:
mailman is python2, mailman3 is python3, but also it has new dependency stack due to adopting django but also splitting or rewriting a lot of its components.
Q: Do we want bin:mailman3 or bin:mailman3-full in main? (the latter pulls
in src:mailman-suite as well). src:mailman-suite has potentially more
things - django, hyperkitty, ruby-sass, uwsgi...
A: We analyzed this and we will need the full set of dependencies, even
meaning MIRs are needed for all of the above listed (and more).
Q: Before proceeding further with assignment/doing technical work in
driving above MIRs, a product level yes/no answers should probably be
answered for above two questions.
A: Discussed in several sprints now, as uncomfortable as it is we will go
through the mass-MIR processing |
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for https://lists.canonical.com/mailman3/postorius/lists/
This source builds only docs and mailman3 itself (which provides mailman3-core).
[Rationale]
This is part of the MIR activity for all dependencies of mailman3
The "main" MIR of it is at bug 1775427:
Mailman (2) has only python2 support, but we strive for python3,
therefore Mailman3 which has python3 support should be promoted to main.
This is an evolution of the mailman2 core delivery engine of the system, but I can't guess how much it deviated so we need to recheck security (IMHO)
[Security]
No known CVEs found.
A few old issues can be found against mailman2 and one (but long fixed) for mailman 3
=> https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=mailman
[Quality assurance]
The mailman3 stacks as of now (Disco) installs fine and provides a base
config. But due to the nature of the package that needs further modification
to be of real use.
The package does in error cases ask a debconf-high question, but it is not going to be installed by default - so that is no MIR problem.
There are a few (2) Ubuntu bugs outstanding, but none of them is critical and stopping this MIR request.
There are a few (2) Debian bugs outstanding all seems to "just work" still, but when we main this in 19.10 we should at least evaluate and maybe adress this one:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921445
There are regular upstream releases and Debian packages them and fixes regularly.
No exotic HW involved.
The package ships a test suite, but it is not run at build time for upstream bug #400.
It tests things in a dep8 test thou to provide coverage.
d/watch is set up and ok.
No Lintian warning except fairly recent newer Standards version.
The package does not rely on demoted or obsolete packages.
[UI standards]
Comes with 7 translations in .po files
No End-user applications that needs a standard conformant desktop file.
[Dependencies]
Some dependencies are not in main, but we drive MIR for all related packages
that are not in main at the same time.
Please check the list of bugs from the main Mailman3 MIR in bug 1775427 to get an overview.
[Standards compliance]
The package meets the FHS and Debian Policy standards.
The packaging itself is very straight forward and uses dh_* as much as possible - the d/rules fits on one screen.
[Maintenance]
The Server team will subscribe for the package for maintenance
[Background]
The package description explains the general purpose and context of the package well.
---
References to all the related MIR bug - one per affected package.
Status (simplified version of https://wiki.ubuntu.com/MIRTeam#Process_states)
(nothing) means we have not even prepared the MIR yet
- MIR not needed (e.g. dependency will be dropped)
* all of the template fields for the MIR are complete
! waiting for MIR review
? cpaelzer needs experienced MIR team members to continue
S needs security review to be accepted
+ MIR accepted
x MIR nacked
Extra Flags which team members or on review feedback can be added:
T extra work for the team that should be done before 20.04 (state todo after package)
M extra work for the team before getting MIR to be acceptable (read as asap)
C needed if only promoting mailman3 (core)
H needed if only promoting mailman3 (core) plus Hyperkitty
J no more needed for mailman3-web if we can cut node-less out
FLAGS | MIR-Bug | Package (Notes)
TC
MH
----------------------------------------
S | bug 1820179 | coreapi
+ | bug 1820180 | coreschema
S | bug 1820181 | django-allauth
+ | bug 1820182 | django-filter
S | bug 1820183 | django-guardian
+ | bug 1820185 | django-haystack
S | bug 1820186 | django-mailman3
- | | django-paintstore ((no dep hyperkitty >=1.2.2-1)
+ | bug 1820188 | django-picklefield
+ | bug 1820189 | django-q
S | bug 1820190 | djangorestframework
S C | bug 1820191 | flufl.bounce
+ C | bug 1820192 | flufl.i18n
+ C | bug 1820193 | flufl.lock
! | bug 1820195 | glewlwyd
! | bug 1820196 | hyperkitty
! | bug 1820197 | itypes
- | n/a | jqueryui (no dep hyperkitty >=1.2.2-1)
+ C | bug 1820199 | lazr.config
+TC | bug 1820200 | lazr.delegates (opt: update; suggest dropping nose)
-MJ | bug 1820201 | less.js (Dep will be cut out in Debian bug 924961)
- | n/a | libjs-jquery-colorpicker (no hyperkitty >=1.2.2-1)
! | bug 1820202 | libmatheval
! | bug 1820203 | libpgm
! C | bug 1775427 | mailman3
! | bug 1820204 | mailmanclient
! H | bug 1820205 | mailman-hyperkitty
! | bug 1820206 | mailman-suite
-MJ | bug 1820207 | node-source-map (wait for node-less dep to be cut)
-MJ | bug 1820208 | nodejs (wait for node-less dep to be cut)
! | bug 1820209 | norm
+ | bug 1820982 | nose
! | bug 1820210 | postorius
! | bug 1820211 | python3-openid
! C | bug 1820212 | python-aiosmtpd
! | bug 1820213 | python-arrow
! | bug 1820214 | python-blessed
! | bug 1820215 | python-django-extensions
! | bug 1820216 | python-django-gravatar2
!TC | bug 1820217 | python-falcon (opt: update version before 20.04)
+ | bug 686045 | python-lockfile
!TC | bug 1820220 | python-public (opt: update version before 20.04)
! | bug 1820221 | python-requests-oauthlib
!T | bug 1820223 | python-uritemplate (feed delta back, be a sync)
! | bug 1820224 | python-whoosh
S | bug 1820225 | robot-detection
-M | n/a | ruby-sass (deprecated, use sassc - Debian 924629)
-M | TBD | sassc (Dep will be cut by Debian bug 924961)
-M | TBD | libsass (Dep will be cut by Debian bug 924961)
? | bug 1820226 | twitter-bootstrap3
? | bug 1820227 | uwsgi (FTBFS: #1820095)
+ | bug 1820229 | wcwidth
+ | bug 1597439 | zeromq3
STC | bug 1820233 | zope.component (version update)
STC | bug 1820234 | zope.configuration (version update)
STC | bug 1820236 | zope.event (version update)
STC | bug 1820237 | zope.hookable (version update)
STC | bug 1820238 | zope.i18nmessageid (version update)
STC | bug 1820239 | zope.schema (version update)
List Debian bugs we depend on being resolved as expected before
the dependency tree can completely be MIRed:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924629
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924961
This might sometimes be slightly out of date, to cross check and for history on all of them check git at:
https://git.launchpad.net/~ubuntu-server/+git/mailman3-MIR-party/tree/package-list.txt
---
Past Decisions in regard to this:
mailman is python2, mailman3 is python3, but also it has new dependency stack due to adopting django but also splitting or rewriting a lot of its components.
Q: Do we want bin:mailman3 or bin:mailman3-full in main? (the latter pulls
in src:mailman-suite as well). src:mailman-suite has potentially more
things - django, hyperkitty, ruby-sass, uwsgi...
A: We analyzed this and we will need the full set of dependencies, even
meaning MIRs are needed for all of the above listed (and more).
Q: Before proceeding further with assignment/doing technical work in
driving above MIRs, a product level yes/no answers should probably be
answered for above two questions.
A: Discussed in several sprints now, as uncomfortable as it is we will go
through the mass-MIR processing |
|
| 2019-03-20 15:31:00 |
Christian Ehrhardt |
mailman3 (Ubuntu): assignee |
Christian Ehrhardt (paelzer) |
Ubuntu Security Team (ubuntu-security) |
|
| 2019-03-20 15:31:03 |
Christian Ehrhardt |
bug |
|
|
added subscriber Christian Ehrhardt |
| 2019-03-20 15:33:30 |
Christian Ehrhardt |
description |
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for https://lists.canonical.com/mailman3/postorius/lists/
This source builds only docs and mailman3 itself (which provides mailman3-core).
[Rationale]
This is part of the MIR activity for all dependencies of mailman3
The "main" MIR of it is at bug 1775427:
Mailman (2) has only python2 support, but we strive for python3,
therefore Mailman3 which has python3 support should be promoted to main.
This is an evolution of the mailman2 core delivery engine of the system, but I can't guess how much it deviated so we need to recheck security (IMHO)
[Security]
No known CVEs found.
A few old issues can be found against mailman2 and one (but long fixed) for mailman 3
=> https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=mailman
[Quality assurance]
The mailman3 stacks as of now (Disco) installs fine and provides a base
config. But due to the nature of the package that needs further modification
to be of real use.
The package does in error cases ask a debconf-high question, but it is not going to be installed by default - so that is no MIR problem.
There are a few (2) Ubuntu bugs outstanding, but none of them is critical and stopping this MIR request.
There are a few (2) Debian bugs outstanding all seems to "just work" still, but when we main this in 19.10 we should at least evaluate and maybe adress this one:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921445
There are regular upstream releases and Debian packages them and fixes regularly.
No exotic HW involved.
The package ships a test suite, but it is not run at build time for upstream bug #400.
It tests things in a dep8 test thou to provide coverage.
d/watch is set up and ok.
No Lintian warning except fairly recent newer Standards version.
The package does not rely on demoted or obsolete packages.
[UI standards]
Comes with 7 translations in .po files
No End-user applications that needs a standard conformant desktop file.
[Dependencies]
Some dependencies are not in main, but we drive MIR for all related packages
that are not in main at the same time.
Please check the list of bugs from the main Mailman3 MIR in bug 1775427 to get an overview.
[Standards compliance]
The package meets the FHS and Debian Policy standards.
The packaging itself is very straight forward and uses dh_* as much as possible - the d/rules fits on one screen.
[Maintenance]
The Server team will subscribe for the package for maintenance
[Background]
The package description explains the general purpose and context of the package well.
---
References to all the related MIR bug - one per affected package.
Status (simplified version of https://wiki.ubuntu.com/MIRTeam#Process_states)
(nothing) means we have not even prepared the MIR yet
- MIR not needed (e.g. dependency will be dropped)
* all of the template fields for the MIR are complete
! waiting for MIR review
? cpaelzer needs experienced MIR team members to continue
S needs security review to be accepted
+ MIR accepted
x MIR nacked
Extra Flags which team members or on review feedback can be added:
T extra work for the team that should be done before 20.04 (state todo after package)
M extra work for the team before getting MIR to be acceptable (read as asap)
C needed if only promoting mailman3 (core)
H needed if only promoting mailman3 (core) plus Hyperkitty
J no more needed for mailman3-web if we can cut node-less out
FLAGS | MIR-Bug | Package (Notes)
TC
MH
----------------------------------------
S | bug 1820179 | coreapi
+ | bug 1820180 | coreschema
S | bug 1820181 | django-allauth
+ | bug 1820182 | django-filter
S | bug 1820183 | django-guardian
+ | bug 1820185 | django-haystack
S | bug 1820186 | django-mailman3
- | | django-paintstore ((no dep hyperkitty >=1.2.2-1)
+ | bug 1820188 | django-picklefield
+ | bug 1820189 | django-q
S | bug 1820190 | djangorestframework
S C | bug 1820191 | flufl.bounce
+ C | bug 1820192 | flufl.i18n
+ C | bug 1820193 | flufl.lock
! | bug 1820195 | glewlwyd
! | bug 1820196 | hyperkitty
! | bug 1820197 | itypes
- | n/a | jqueryui (no dep hyperkitty >=1.2.2-1)
+ C | bug 1820199 | lazr.config
+TC | bug 1820200 | lazr.delegates (opt: update; suggest dropping nose)
-MJ | bug 1820201 | less.js (Dep will be cut out in Debian bug 924961)
- | n/a | libjs-jquery-colorpicker (no hyperkitty >=1.2.2-1)
! | bug 1820202 | libmatheval
! | bug 1820203 | libpgm
! C | bug 1775427 | mailman3
! | bug 1820204 | mailmanclient
! H | bug 1820205 | mailman-hyperkitty
! | bug 1820206 | mailman-suite
-MJ | bug 1820207 | node-source-map (wait for node-less dep to be cut)
-MJ | bug 1820208 | nodejs (wait for node-less dep to be cut)
! | bug 1820209 | norm
+ | bug 1820982 | nose
! | bug 1820210 | postorius
! | bug 1820211 | python3-openid
! C | bug 1820212 | python-aiosmtpd
! | bug 1820213 | python-arrow
! | bug 1820214 | python-blessed
! | bug 1820215 | python-django-extensions
! | bug 1820216 | python-django-gravatar2
!TC | bug 1820217 | python-falcon (opt: update version before 20.04)
+ | bug 686045 | python-lockfile
!TC | bug 1820220 | python-public (opt: update version before 20.04)
! | bug 1820221 | python-requests-oauthlib
!T | bug 1820223 | python-uritemplate (feed delta back, be a sync)
! | bug 1820224 | python-whoosh
S | bug 1820225 | robot-detection
-M | n/a | ruby-sass (deprecated, use sassc - Debian 924629)
-M | TBD | sassc (Dep will be cut by Debian bug 924961)
-M | TBD | libsass (Dep will be cut by Debian bug 924961)
? | bug 1820226 | twitter-bootstrap3
? | bug 1820227 | uwsgi (FTBFS: #1820095)
+ | bug 1820229 | wcwidth
+ | bug 1597439 | zeromq3
STC | bug 1820233 | zope.component (version update)
STC | bug 1820234 | zope.configuration (version update)
STC | bug 1820236 | zope.event (version update)
STC | bug 1820237 | zope.hookable (version update)
STC | bug 1820238 | zope.i18nmessageid (version update)
STC | bug 1820239 | zope.schema (version update)
List Debian bugs we depend on being resolved as expected before
the dependency tree can completely be MIRed:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924629
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924961
This might sometimes be slightly out of date, to cross check and for history on all of them check git at:
https://git.launchpad.net/~ubuntu-server/+git/mailman3-MIR-party/tree/package-list.txt
---
Past Decisions in regard to this:
mailman is python2, mailman3 is python3, but also it has new dependency stack due to adopting django but also splitting or rewriting a lot of its components.
Q: Do we want bin:mailman3 or bin:mailman3-full in main? (the latter pulls
in src:mailman-suite as well). src:mailman-suite has potentially more
things - django, hyperkitty, ruby-sass, uwsgi...
A: We analyzed this and we will need the full set of dependencies, even
meaning MIRs are needed for all of the above listed (and more).
Q: Before proceeding further with assignment/doing technical work in
driving above MIRs, a product level yes/no answers should probably be
answered for above two questions.
A: Discussed in several sprints now, as uncomfortable as it is we will go
through the mass-MIR processing |
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for https://lists.canonical.com/mailman3/postorius/lists/
This source builds only docs and mailman3 itself (which provides mailman3-core).
[Rationale]
This is part of the MIR activity for all dependencies of mailman3
The "main" MIR of it is at bug 1775427:
Mailman (2) has only python2 support, but we strive for python3,
therefore Mailman3 which has python3 support should be promoted to main.
This is an evolution of the mailman2 core delivery engine of the system, but I can't guess how much it deviated so we need to recheck security (IMHO)
[Security]
No known CVEs found.
A few old issues can be found against mailman2 and one (but long fixed) for mailman 3
=> https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=mailman
[Quality assurance]
The mailman3 stacks as of now (Disco) installs fine and provides a base
config. But due to the nature of the package that needs further modification
to be of real use.
The package does in error cases ask a debconf-high question, but it is not going to be installed by default - so that is no MIR problem.
There are a few (2) Ubuntu bugs outstanding, but none of them is critical and stopping this MIR request.
There are a few (2) Debian bugs outstanding all seems to "just work" still, but when we main this in 19.10 we should at least evaluate and maybe adress this one:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921445
There are regular upstream releases and Debian packages them and fixes regularly.
No exotic HW involved.
The package ships a test suite, but it is not run at build time for upstream bug #400.
It tests things in a dep8 test thou to provide coverage.
d/watch is set up and ok.
No Lintian warning except fairly recent newer Standards version.
The package does not rely on demoted or obsolete packages.
[UI standards]
Comes with 7 translations in .po files
No End-user applications that needs a standard conformant desktop file.
[Dependencies]
Some dependencies are not in main, but we drive MIR for all related packages
that are not in main at the same time.
Please check the list of bugs from the main Mailman3 MIR in bug 1775427 to get an overview.
[Standards compliance]
The package meets the FHS and Debian Policy standards.
The packaging itself is very straight forward and uses dh_* as much as possible - the d/rules fits on one screen.
[Maintenance]
The Server team will subscribe for the package for maintenance
[Background]
The package description explains the general purpose and context of the package well.
---
References to all the related MIR bug - one per affected package.
Status (simplified version of https://wiki.ubuntu.com/MIRTeam#Process_states)
(nothing) means we have not even prepared the MIR yet
- MIR not needed (e.g. dependency will be dropped)
* all of the template fields for the MIR are complete
! waiting for MIR review
? cpaelzer needs experienced MIR team members to continue
S needs security review to be accepted
+ MIR accepted
x MIR nacked
Extra Flags which team members or on review feedback can be added:
T extra work for the team that should be done before 20.04 (state todo after package)
M extra work for the team before getting MIR to be acceptable (read as asap)
C needed if only promoting mailman3 (core)
H needed if only promoting mailman3 (core) plus Hyperkitty
J no more needed for mailman3-web if we can cut node-less out
FLAGS | MIR-Bug | Package (Notes)
TC
MH
----------------------------------------
S | bug 1820179 | coreapi
+ | bug 1820180 | coreschema
S | bug 1820181 | django-allauth
+ | bug 1820182 | django-filter
S | bug 1820183 | django-guardian
+ | bug 1820185 | django-haystack
S | bug 1820186 | django-mailman3
- | | django-paintstore ((no dep hyperkitty >=1.2.2-1)
+ | bug 1820188 | django-picklefield
+ | bug 1820189 | django-q
S | bug 1820190 | djangorestframework
S C | bug 1820191 | flufl.bounce
+ C | bug 1820192 | flufl.i18n
+ C | bug 1820193 | flufl.lock
! | bug 1820195 | glewlwyd
S | bug 1820196 | hyperkitty
! | bug 1820197 | itypes
- | n/a | jqueryui (no dep hyperkitty >=1.2.2-1)
+ C | bug 1820199 | lazr.config
+TC | bug 1820200 | lazr.delegates (opt: update; suggest dropping nose)
-MJ | bug 1820201 | less.js (Dep will be cut out in Debian bug 924961)
- | n/a | libjs-jquery-colorpicker (no hyperkitty >=1.2.2-1)
! | bug 1820202 | libmatheval
! | bug 1820203 | libpgm
S C | bug 1775427 | mailman3
S | bug 1820204 | mailmanclient
S H | bug 1820205 | mailman-hyperkitty
S | bug 1820206 | mailman-suite
-MJ | bug 1820207 | node-source-map (wait for node-less dep to be cut)
-MJ | bug 1820208 | nodejs (wait for node-less dep to be cut)
! | bug 1820209 | norm
+ | bug 1820982 | nose
S | bug 1820210 | postorius
! | bug 1820211 | python3-openid
! C | bug 1820212 | python-aiosmtpd
! | bug 1820213 | python-arrow
! | bug 1820214 | python-blessed
! | bug 1820215 | python-django-extensions
! | bug 1820216 | python-django-gravatar2
!TC | bug 1820217 | python-falcon (opt: update version before 20.04)
+ | bug 686045 | python-lockfile
!TC | bug 1820220 | python-public (opt: update version before 20.04)
! | bug 1820221 | python-requests-oauthlib
!T | bug 1820223 | python-uritemplate (feed delta back, be a sync)
! | bug 1820224 | python-whoosh
S | bug 1820225 | robot-detection
-M | n/a | ruby-sass (deprecated, use sassc - Debian 924629)
-M | TBD | sassc (Dep will be cut by Debian bug 924961)
-M | TBD | libsass (Dep will be cut by Debian bug 924961)
? | bug 1820226 | twitter-bootstrap3
? | bug 1820227 | uwsgi (FTBFS: #1820095)
+ | bug 1820229 | wcwidth
+ | bug 1597439 | zeromq3
STC | bug 1820233 | zope.component (version update)
STC | bug 1820234 | zope.configuration (version update)
STC | bug 1820236 | zope.event (version update)
STC | bug 1820237 | zope.hookable (version update)
STC | bug 1820238 | zope.i18nmessageid (version update)
STC | bug 1820239 | zope.schema (version update)
List Debian bugs we depend on being resolved as expected before
the dependency tree can completely be MIRed:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924629
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924961
This might sometimes be slightly out of date, to cross check and for history on all of them check git at:
https://git.launchpad.net/~ubuntu-server/+git/mailman3-MIR-party/tree/package-list.txt
---
Past Decisions in regard to this:
mailman is python2, mailman3 is python3, but also it has new dependency stack due to adopting django but also splitting or rewriting a lot of its components.
Q: Do we want bin:mailman3 or bin:mailman3-full in main? (the latter pulls
in src:mailman-suite as well). src:mailman-suite has potentially more
things - django, hyperkitty, ruby-sass, uwsgi...
A: We analyzed this and we will need the full set of dependencies, even
meaning MIRs are needed for all of the above listed (and more).
Q: Before proceeding further with assignment/doing technical work in
driving above MIRs, a product level yes/no answers should probably be
answered for above two questions.
A: Discussed in several sprints now, as uncomfortable as it is we will go
through the mass-MIR processing |
|
| 2019-03-21 14:30:00 |
Christian Ehrhardt |
description |
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for https://lists.canonical.com/mailman3/postorius/lists/
This source builds only docs and mailman3 itself (which provides mailman3-core).
[Rationale]
This is part of the MIR activity for all dependencies of mailman3
The "main" MIR of it is at bug 1775427:
Mailman (2) has only python2 support, but we strive for python3,
therefore Mailman3 which has python3 support should be promoted to main.
This is an evolution of the mailman2 core delivery engine of the system, but I can't guess how much it deviated so we need to recheck security (IMHO)
[Security]
No known CVEs found.
A few old issues can be found against mailman2 and one (but long fixed) for mailman 3
=> https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=mailman
[Quality assurance]
The mailman3 stacks as of now (Disco) installs fine and provides a base
config. But due to the nature of the package that needs further modification
to be of real use.
The package does in error cases ask a debconf-high question, but it is not going to be installed by default - so that is no MIR problem.
There are a few (2) Ubuntu bugs outstanding, but none of them is critical and stopping this MIR request.
There are a few (2) Debian bugs outstanding all seems to "just work" still, but when we main this in 19.10 we should at least evaluate and maybe adress this one:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921445
There are regular upstream releases and Debian packages them and fixes regularly.
No exotic HW involved.
The package ships a test suite, but it is not run at build time for upstream bug #400.
It tests things in a dep8 test thou to provide coverage.
d/watch is set up and ok.
No Lintian warning except fairly recent newer Standards version.
The package does not rely on demoted or obsolete packages.
[UI standards]
Comes with 7 translations in .po files
No End-user applications that needs a standard conformant desktop file.
[Dependencies]
Some dependencies are not in main, but we drive MIR for all related packages
that are not in main at the same time.
Please check the list of bugs from the main Mailman3 MIR in bug 1775427 to get an overview.
[Standards compliance]
The package meets the FHS and Debian Policy standards.
The packaging itself is very straight forward and uses dh_* as much as possible - the d/rules fits on one screen.
[Maintenance]
The Server team will subscribe for the package for maintenance
[Background]
The package description explains the general purpose and context of the package well.
---
References to all the related MIR bug - one per affected package.
Status (simplified version of https://wiki.ubuntu.com/MIRTeam#Process_states)
(nothing) means we have not even prepared the MIR yet
- MIR not needed (e.g. dependency will be dropped)
* all of the template fields for the MIR are complete
! waiting for MIR review
? cpaelzer needs experienced MIR team members to continue
S needs security review to be accepted
+ MIR accepted
x MIR nacked
Extra Flags which team members or on review feedback can be added:
T extra work for the team that should be done before 20.04 (state todo after package)
M extra work for the team before getting MIR to be acceptable (read as asap)
C needed if only promoting mailman3 (core)
H needed if only promoting mailman3 (core) plus Hyperkitty
J no more needed for mailman3-web if we can cut node-less out
FLAGS | MIR-Bug | Package (Notes)
TC
MH
----------------------------------------
S | bug 1820179 | coreapi
+ | bug 1820180 | coreschema
S | bug 1820181 | django-allauth
+ | bug 1820182 | django-filter
S | bug 1820183 | django-guardian
+ | bug 1820185 | django-haystack
S | bug 1820186 | django-mailman3
- | | django-paintstore ((no dep hyperkitty >=1.2.2-1)
+ | bug 1820188 | django-picklefield
+ | bug 1820189 | django-q
S | bug 1820190 | djangorestframework
S C | bug 1820191 | flufl.bounce
+ C | bug 1820192 | flufl.i18n
+ C | bug 1820193 | flufl.lock
! | bug 1820195 | glewlwyd
S | bug 1820196 | hyperkitty
! | bug 1820197 | itypes
- | n/a | jqueryui (no dep hyperkitty >=1.2.2-1)
+ C | bug 1820199 | lazr.config
+TC | bug 1820200 | lazr.delegates (opt: update; suggest dropping nose)
-MJ | bug 1820201 | less.js (Dep will be cut out in Debian bug 924961)
- | n/a | libjs-jquery-colorpicker (no hyperkitty >=1.2.2-1)
! | bug 1820202 | libmatheval
! | bug 1820203 | libpgm
S C | bug 1775427 | mailman3
S | bug 1820204 | mailmanclient
S H | bug 1820205 | mailman-hyperkitty
S | bug 1820206 | mailman-suite
-MJ | bug 1820207 | node-source-map (wait for node-less dep to be cut)
-MJ | bug 1820208 | nodejs (wait for node-less dep to be cut)
! | bug 1820209 | norm
+ | bug 1820982 | nose
S | bug 1820210 | postorius
! | bug 1820211 | python3-openid
! C | bug 1820212 | python-aiosmtpd
! | bug 1820213 | python-arrow
! | bug 1820214 | python-blessed
! | bug 1820215 | python-django-extensions
! | bug 1820216 | python-django-gravatar2
!TC | bug 1820217 | python-falcon (opt: update version before 20.04)
+ | bug 686045 | python-lockfile
!TC | bug 1820220 | python-public (opt: update version before 20.04)
! | bug 1820221 | python-requests-oauthlib
!T | bug 1820223 | python-uritemplate (feed delta back, be a sync)
! | bug 1820224 | python-whoosh
S | bug 1820225 | robot-detection
-M | n/a | ruby-sass (deprecated, use sassc - Debian 924629)
-M | TBD | sassc (Dep will be cut by Debian bug 924961)
-M | TBD | libsass (Dep will be cut by Debian bug 924961)
? | bug 1820226 | twitter-bootstrap3
? | bug 1820227 | uwsgi (FTBFS: #1820095)
+ | bug 1820229 | wcwidth
+ | bug 1597439 | zeromq3
STC | bug 1820233 | zope.component (version update)
STC | bug 1820234 | zope.configuration (version update)
STC | bug 1820236 | zope.event (version update)
STC | bug 1820237 | zope.hookable (version update)
STC | bug 1820238 | zope.i18nmessageid (version update)
STC | bug 1820239 | zope.schema (version update)
List Debian bugs we depend on being resolved as expected before
the dependency tree can completely be MIRed:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924629
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924961
This might sometimes be slightly out of date, to cross check and for history on all of them check git at:
https://git.launchpad.net/~ubuntu-server/+git/mailman3-MIR-party/tree/package-list.txt
---
Past Decisions in regard to this:
mailman is python2, mailman3 is python3, but also it has new dependency stack due to adopting django but also splitting or rewriting a lot of its components.
Q: Do we want bin:mailman3 or bin:mailman3-full in main? (the latter pulls
in src:mailman-suite as well). src:mailman-suite has potentially more
things - django, hyperkitty, ruby-sass, uwsgi...
A: We analyzed this and we will need the full set of dependencies, even
meaning MIRs are needed for all of the above listed (and more).
Q: Before proceeding further with assignment/doing technical work in
driving above MIRs, a product level yes/no answers should probably be
answered for above two questions.
A: Discussed in several sprints now, as uncomfortable as it is we will go
through the mass-MIR processing |
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for https://lists.canonical.com/mailman3/postorius/lists/
This source builds only docs and mailman3 itself (which provides mailman3-core).
[Rationale]
This is part of the MIR activity for all dependencies of mailman3
The "main" MIR of it is at bug 1775427:
Mailman (2) has only python2 support, but we strive for python3,
therefore Mailman3 which has python3 support should be promoted to main.
This is an evolution of the mailman2 core delivery engine of the system, but I can't guess how much it deviated so we need to recheck security (IMHO)
[Security]
No known CVEs found.
A few old issues can be found against mailman2 and one (but long fixed) for mailman 3
=> https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=mailman
[Quality assurance]
The mailman3 stacks as of now (Disco) installs fine and provides a base
config. But due to the nature of the package that needs further modification
to be of real use.
The package does in error cases ask a debconf-high question, but it is not going to be installed by default - so that is no MIR problem.
There are a few (2) Ubuntu bugs outstanding, but none of them is critical and stopping this MIR request.
There are a few (2) Debian bugs outstanding all seems to "just work" still, but when we main this in 19.10 we should at least evaluate and maybe adress this one:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921445
There are regular upstream releases and Debian packages them and fixes regularly.
No exotic HW involved.
The package ships a test suite, but it is not run at build time for upstream bug #400.
It tests things in a dep8 test thou to provide coverage.
d/watch is set up and ok.
No Lintian warning except fairly recent newer Standards version.
The package does not rely on demoted or obsolete packages.
[UI standards]
Comes with 7 translations in .po files
No End-user applications that needs a standard conformant desktop file.
[Dependencies]
Some dependencies are not in main, but we drive MIR for all related packages
that are not in main at the same time.
Please check the list of bugs from the main Mailman3 MIR in bug 1775427 to get an overview.
[Standards compliance]
The package meets the FHS and Debian Policy standards.
The packaging itself is very straight forward and uses dh_* as much as possible - the d/rules fits on one screen.
[Maintenance]
The Server team will subscribe for the package for maintenance
[Background]
The package description explains the general purpose and context of the package well.
---
References to all the related MIR bug - one per affected package.
Status (simplified version of https://wiki.ubuntu.com/MIRTeam#Process_states)
(nothing) means we have not even prepared the MIR yet
- MIR not needed (e.g. dependency will be dropped)
* all of the template fields for the MIR are complete
! waiting for MIR review
? cpaelzer needs experienced MIR team members to continue
S needs security review to be accepted
+ MIR accepted
x MIR nacked
Extra Flags which team members or on review feedback can be added:
T extra work for the team that should be done before 20.04 (state todo after package)
M extra work for the team before getting MIR to be acceptable (read as asap)
C needed if only promoting mailman3 (core)
H needed if only promoting mailman3 (core) plus Hyperkitty
J no more needed for mailman3-web if we can cut node-less out
FLAGS | MIR-Bug | Package (Notes)
TC
MH
----------------------------------------
S | bug 1820179 | coreapi
+ | bug 1820180 | coreschema
S | bug 1820181 | django-allauth
+ | bug 1820182 | django-filter
S | bug 1820183 | django-guardian
+ | bug 1820185 | django-haystack
S | bug 1820186 | django-mailman3
- | | django-paintstore ((no dep hyperkitty >=1.2.2-1)
+ | bug 1820188 | django-picklefield
+ | bug 1820189 | django-q
S | bug 1820190 | djangorestframework
S C | bug 1820191 | flufl.bounce
+ C | bug 1820192 | flufl.i18n
+ C | bug 1820193 | flufl.lock
? | bug 1820195 | glewlwyd (likely need to break dep to this)
S | bug 1820196 | hyperkitty
+ | bug 1820197 | itypes
- | n/a | jqueryui (no dep hyperkitty >=1.2.2-1)
+ C | bug 1820199 | lazr.config
+TC | bug 1820200 | lazr.delegates (opt: update; suggest dropping nose)
-MJ | bug 1820201 | less.js (Dep will be cut out in Debian bug 924961)
- | n/a | libjs-jquery-colorpicker (no hyperkitty >=1.2.2-1)
S | bug 1820202 | libmatheval
S | bug 1820203 | libpgm
S C | bug 1775427 | mailman3
S | bug 1820204 | mailmanclient
S H | bug 1820205 | mailman-hyperkitty
S | bug 1820206 | mailman-suite
-MJ | bug 1820207 | node-source-map (wait for node-less dep to be cut)
-MJ | bug 1820208 | nodejs (wait for node-less dep to be cut)
?+S | bug 1820209 | norm (check if embedded protolib is an issue)
+ | bug 1820982 | nose
S | bug 1820210 | postorius
! | bug 1820211 | python3-openid
! C | bug 1820212 | python-aiosmtpd
+T | bug 1820213 | python-arrow (non fatal build error on dateutil, tests)
+ | bug 1820214 | python-blessed
! | bug 1820215 | python-django-extensions
! | bug 1820216 | python-django-gravatar2
!TC | bug 1820217 | python-falcon (opt: update version before 20.04)
+ | bug 686045 | python-lockfile
+TC | bug 1820220 | python-public (opt: update version before 20.04)
! | bug 1820221 | python-requests-oauthlib
+T | bug 1820223 | python-uritemplate (be a sync, better new upstream)
! | bug 1820224 | python-whoosh
S | bug 1820225 | robot-detection
-M | n/a | ruby-sass (deprecated, use sassc - Debian 924629)
-M | TBD | sassc (Dep will be cut by Debian bug 924961)
-M | TBD | libsass (Dep will be cut by Debian bug 924961)
? | bug 1820226 | twitter-bootstrap3
? | bug 1820227 | uwsgi (FTBFS: #1820095)
+ | bug 1820229 | wcwidth
+ | bug 1597439 | zeromq3
STC | bug 1820233 | zope.component (version update)
STC | bug 1820234 | zope.configuration (version update)
STC | bug 1820236 | zope.event (version update)
STC | bug 1820237 | zope.hookable (version update)
STC | bug 1820238 | zope.i18nmessageid (version update)
STC | bug 1820239 | zope.schema (version update)
List Debian bugs we depend on being resolved as expected before
the dependency tree can completely be MIRed:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924629
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924961
This might sometimes be slightly out of date, to cross check and for history on all of them check git at:
https://git.launchpad.net/~ubuntu-server/+git/mailman3-MIR-party/tree/package-list.txt
---
Past Decisions in regard to this:
mailman is python2, mailman3 is python3, but also it has new dependency stack due to adopting django but also splitting or rewriting a lot of its components.
Q: Do we want bin:mailman3 or bin:mailman3-full in main? (the latter pulls
in src:mailman-suite as well). src:mailman-suite has potentially more
things - django, hyperkitty, ruby-sass, uwsgi...
A: We analyzed this and we will need the full set of dependencies, even
meaning MIRs are needed for all of the above listed (and more).
Q: Before proceeding further with assignment/doing technical work in
driving above MIRs, a product level yes/no answers should probably be
answered for above two questions.
A: Discussed in several sprints now, as uncomfortable as it is we will go
through the mass-MIR processing |
|
| 2019-03-22 08:24:25 |
Christian Ehrhardt |
description |
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for https://lists.canonical.com/mailman3/postorius/lists/
This source builds only docs and mailman3 itself (which provides mailman3-core).
[Rationale]
This is part of the MIR activity for all dependencies of mailman3
The "main" MIR of it is at bug 1775427:
Mailman (2) has only python2 support, but we strive for python3,
therefore Mailman3 which has python3 support should be promoted to main.
This is an evolution of the mailman2 core delivery engine of the system, but I can't guess how much it deviated so we need to recheck security (IMHO)
[Security]
No known CVEs found.
A few old issues can be found against mailman2 and one (but long fixed) for mailman 3
=> https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=mailman
[Quality assurance]
The mailman3 stacks as of now (Disco) installs fine and provides a base
config. But due to the nature of the package that needs further modification
to be of real use.
The package does in error cases ask a debconf-high question, but it is not going to be installed by default - so that is no MIR problem.
There are a few (2) Ubuntu bugs outstanding, but none of them is critical and stopping this MIR request.
There are a few (2) Debian bugs outstanding all seems to "just work" still, but when we main this in 19.10 we should at least evaluate and maybe adress this one:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921445
There are regular upstream releases and Debian packages them and fixes regularly.
No exotic HW involved.
The package ships a test suite, but it is not run at build time for upstream bug #400.
It tests things in a dep8 test thou to provide coverage.
d/watch is set up and ok.
No Lintian warning except fairly recent newer Standards version.
The package does not rely on demoted or obsolete packages.
[UI standards]
Comes with 7 translations in .po files
No End-user applications that needs a standard conformant desktop file.
[Dependencies]
Some dependencies are not in main, but we drive MIR for all related packages
that are not in main at the same time.
Please check the list of bugs from the main Mailman3 MIR in bug 1775427 to get an overview.
[Standards compliance]
The package meets the FHS and Debian Policy standards.
The packaging itself is very straight forward and uses dh_* as much as possible - the d/rules fits on one screen.
[Maintenance]
The Server team will subscribe for the package for maintenance
[Background]
The package description explains the general purpose and context of the package well.
---
References to all the related MIR bug - one per affected package.
Status (simplified version of https://wiki.ubuntu.com/MIRTeam#Process_states)
(nothing) means we have not even prepared the MIR yet
- MIR not needed (e.g. dependency will be dropped)
* all of the template fields for the MIR are complete
! waiting for MIR review
? cpaelzer needs experienced MIR team members to continue
S needs security review to be accepted
+ MIR accepted
x MIR nacked
Extra Flags which team members or on review feedback can be added:
T extra work for the team that should be done before 20.04 (state todo after package)
M extra work for the team before getting MIR to be acceptable (read as asap)
C needed if only promoting mailman3 (core)
H needed if only promoting mailman3 (core) plus Hyperkitty
J no more needed for mailman3-web if we can cut node-less out
FLAGS | MIR-Bug | Package (Notes)
TC
MH
----------------------------------------
S | bug 1820179 | coreapi
+ | bug 1820180 | coreschema
S | bug 1820181 | django-allauth
+ | bug 1820182 | django-filter
S | bug 1820183 | django-guardian
+ | bug 1820185 | django-haystack
S | bug 1820186 | django-mailman3
- | | django-paintstore ((no dep hyperkitty >=1.2.2-1)
+ | bug 1820188 | django-picklefield
+ | bug 1820189 | django-q
S | bug 1820190 | djangorestframework
S C | bug 1820191 | flufl.bounce
+ C | bug 1820192 | flufl.i18n
+ C | bug 1820193 | flufl.lock
? | bug 1820195 | glewlwyd (likely need to break dep to this)
S | bug 1820196 | hyperkitty
+ | bug 1820197 | itypes
- | n/a | jqueryui (no dep hyperkitty >=1.2.2-1)
+ C | bug 1820199 | lazr.config
+TC | bug 1820200 | lazr.delegates (opt: update; suggest dropping nose)
-MJ | bug 1820201 | less.js (Dep will be cut out in Debian bug 924961)
- | n/a | libjs-jquery-colorpicker (no hyperkitty >=1.2.2-1)
S | bug 1820202 | libmatheval
S | bug 1820203 | libpgm
S C | bug 1775427 | mailman3
S | bug 1820204 | mailmanclient
S H | bug 1820205 | mailman-hyperkitty
S | bug 1820206 | mailman-suite
-MJ | bug 1820207 | node-source-map (wait for node-less dep to be cut)
-MJ | bug 1820208 | nodejs (wait for node-less dep to be cut)
?+S | bug 1820209 | norm (check if embedded protolib is an issue)
+ | bug 1820982 | nose
S | bug 1820210 | postorius
! | bug 1820211 | python3-openid
! C | bug 1820212 | python-aiosmtpd
+T | bug 1820213 | python-arrow (non fatal build error on dateutil, tests)
+ | bug 1820214 | python-blessed
! | bug 1820215 | python-django-extensions
! | bug 1820216 | python-django-gravatar2
!TC | bug 1820217 | python-falcon (opt: update version before 20.04)
+ | bug 686045 | python-lockfile
+TC | bug 1820220 | python-public (opt: update version before 20.04)
! | bug 1820221 | python-requests-oauthlib
+T | bug 1820223 | python-uritemplate (be a sync, better new upstream)
! | bug 1820224 | python-whoosh
S | bug 1820225 | robot-detection
-M | n/a | ruby-sass (deprecated, use sassc - Debian 924629)
-M | TBD | sassc (Dep will be cut by Debian bug 924961)
-M | TBD | libsass (Dep will be cut by Debian bug 924961)
? | bug 1820226 | twitter-bootstrap3
? | bug 1820227 | uwsgi (FTBFS: #1820095)
+ | bug 1820229 | wcwidth
+ | bug 1597439 | zeromq3
STC | bug 1820233 | zope.component (version update)
STC | bug 1820234 | zope.configuration (version update)
STC | bug 1820236 | zope.event (version update)
STC | bug 1820237 | zope.hookable (version update)
STC | bug 1820238 | zope.i18nmessageid (version update)
STC | bug 1820239 | zope.schema (version update)
List Debian bugs we depend on being resolved as expected before
the dependency tree can completely be MIRed:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924629
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924961
This might sometimes be slightly out of date, to cross check and for history on all of them check git at:
https://git.launchpad.net/~ubuntu-server/+git/mailman3-MIR-party/tree/package-list.txt
---
Past Decisions in regard to this:
mailman is python2, mailman3 is python3, but also it has new dependency stack due to adopting django but also splitting or rewriting a lot of its components.
Q: Do we want bin:mailman3 or bin:mailman3-full in main? (the latter pulls
in src:mailman-suite as well). src:mailman-suite has potentially more
things - django, hyperkitty, ruby-sass, uwsgi...
A: We analyzed this and we will need the full set of dependencies, even
meaning MIRs are needed for all of the above listed (and more).
Q: Before proceeding further with assignment/doing technical work in
driving above MIRs, a product level yes/no answers should probably be
answered for above two questions.
A: Discussed in several sprints now, as uncomfortable as it is we will go
through the mass-MIR processing |
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for https://lists.canonical.com/mailman3/postorius/lists/
This source builds only docs and mailman3 itself (which provides mailman3-core).
[Rationale]
This is part of the MIR activity for all dependencies of mailman3
The "main" MIR of it is at bug 1775427:
Mailman (2) has only python2 support, but we strive for python3,
therefore Mailman3 which has python3 support should be promoted to main.
This is an evolution of the mailman2 core delivery engine of the system, but I can't guess how much it deviated so we need to recheck security (IMHO)
[Security]
No known CVEs found.
A few old issues can be found against mailman2 and one (but long fixed) for mailman 3
=> https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=mailman
[Quality assurance]
The mailman3 stacks as of now (Disco) installs fine and provides a base
config. But due to the nature of the package that needs further modification
to be of real use.
The package does in error cases ask a debconf-high question, but it is not going to be installed by default - so that is no MIR problem.
There are a few (2) Ubuntu bugs outstanding, but none of them is critical and stopping this MIR request.
There are a few (2) Debian bugs outstanding all seems to "just work" still, but when we main this in 19.10 we should at least evaluate and maybe adress this one:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921445
There are regular upstream releases and Debian packages them and fixes regularly.
No exotic HW involved.
The package ships a test suite, but it is not run at build time for upstream bug #400.
It tests things in a dep8 test thou to provide coverage.
d/watch is set up and ok.
No Lintian warning except fairly recent newer Standards version.
The package does not rely on demoted or obsolete packages.
[UI standards]
Comes with 7 translations in .po files
No End-user applications that needs a standard conformant desktop file.
[Dependencies]
Some dependencies are not in main, but we drive MIR for all related packages
that are not in main at the same time.
Please check the list of bugs from the main Mailman3 MIR in bug 1775427 to get an overview.
[Standards compliance]
The package meets the FHS and Debian Policy standards.
The packaging itself is very straight forward and uses dh_* as much as possible - the d/rules fits on one screen.
[Maintenance]
The Server team will subscribe for the package for maintenance
[Background]
The package description explains the general purpose and context of the package well.
---
References to all the related MIR bug - one per affected package.
Status (simplified version of https://wiki.ubuntu.com/MIRTeam#Process_states)
(nothing) means we have not even prepared the MIR yet
- MIR not needed (e.g. dependency will be dropped)
* all of the template fields for the MIR are complete
! waiting for MIR review
? cpaelzer needs experienced MIR team members to continue
S needs security review to be accepted
+ MIR accepted
x MIR nacked
Extra Flags which team members or on review feedback can be added:
T extra work for the team that should be done before 20.04 (state todo after package)
M extra work for the team before getting MIR to be acceptable (read as asap)
C needed if only promoting mailman3 (core)
H needed if only promoting mailman3 (core) plus Hyperkitty
J no more needed for mailman3-web if we can cut node-less out
FLAGS | MIR-Bug | Package (Notes)
TC
MH
----------------------------------------
S | bug 1820179 | coreapi
+ | bug 1820180 | coreschema
S | bug 1820181 | django-allauth
+ | bug 1820182 | django-filter
S | bug 1820183 | django-guardian
+ | bug 1820185 | django-haystack
S | bug 1820186 | django-mailman3
- | | django-paintstore ((no dep hyperkitty >=1.2.2-1)
+ | bug 1820188 | django-picklefield
+ | bug 1820189 | django-q
S | bug 1820190 | djangorestframework
S C | bug 1820191 | flufl.bounce
+ C | bug 1820192 | flufl.i18n
+ C | bug 1820193 | flufl.lock
? | bug 1820195 | glewlwyd (likely need to break dep to this)
S | bug 1820196 | hyperkitty
+ | bug 1820197 | itypes
- | n/a | jqueryui (no dep hyperkitty >=1.2.2-1)
+ C | bug 1820199 | lazr.config
+TC | bug 1820200 | lazr.delegates (opt: update; suggest dropping nose)
-MJ | bug 1820201 | less.js (Dep will be cut out in Debian bug 924961)
- | n/a | libjs-jquery-colorpicker (no hyperkitty >=1.2.2-1)
S | bug 1820202 | libmatheval
S | bug 1820203 | libpgm
S C | bug 1775427 | mailman3
S | bug 1820204 | mailmanclient
S H | bug 1820205 | mailman-hyperkitty
S | bug 1820206 | mailman-suite
-MJ | bug 1820207 | node-source-map (wait for node-less dep to be cut)
-MJ | bug 1820208 | nodejs (wait for node-less dep to be cut)
S+? | bug 1820209 | norm (check if embedded protolib is an issue)
+ | bug 1820982 | nose
S | bug 1820210 | postorius
S | bug 1820211 | python3-openid
S C | bug 1820212 | python-aiosmtpd
+T | bug 1820213 | python-arrow (non fatal build error on dateutil, tests)
+ | bug 1820214 | python-blessed
S+? | bug 1820215 | python-django-extensions (many functions in one package)
S | bug 1820216 | python-django-gravatar2
STC | bug 1820217 | python-falcon (opt: update version before 20.04)
+ | bug 686045 | python-lockfile
+TC | bug 1820220 | python-public (opt: update version before 20.04)
S | bug 1820221 | python-requests-oauthlib
+T | bug 1820223 | python-uritemplate (be a sync, better new upstream)
S | bug 1820224 | python-whoosh
S | bug 1820225 | robot-detection
-M | n/a | ruby-sass (deprecated, use sassc - Debian 924629)
-M | TBD | sassc (Dep will be cut by Debian bug 924961)
-M | TBD | libsass (Dep will be cut by Debian bug 924961)
? | bug 1820226 | twitter-bootstrap3
? | bug 1820227 | uwsgi (FTBFS: #1820095)
+ | bug 1820229 | wcwidth
+ | bug 1597439 | zeromq3
STC | bug 1820233 | zope.component (version update)
STC | bug 1820234 | zope.configuration (version update)
STC | bug 1820236 | zope.event (version update)
STC | bug 1820237 | zope.hookable (version update)
STC | bug 1820238 | zope.i18nmessageid (version update)
STC | bug 1820239 | zope.schema (version update)
List Debian bugs we depend on being resolved as expected before
the dependency tree can completely be MIRed:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924629
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924961
This might sometimes be slightly out of date, to cross check and for history on all of them check git at:
https://git.launchpad.net/~ubuntu-server/+git/mailman3-MIR-party/tree/package-list.txt
---
Past Decisions in regard to this:
mailman is python2, mailman3 is python3, but also it has new dependency stack due to adopting django but also splitting or rewriting a lot of its components.
Q: Do we want bin:mailman3 or bin:mailman3-full in main? (the latter pulls
in src:mailman-suite as well). src:mailman-suite has potentially more
things - django, hyperkitty, ruby-sass, uwsgi...
A: We analyzed this and we will need the full set of dependencies, even
meaning MIRs are needed for all of the above listed (and more).
Q: Before proceeding further with assignment/doing technical work in
driving above MIRs, a product level yes/no answers should probably be
answered for above two questions.
A: Discussed in several sprints now, as uncomfortable as it is we will go
through the mass-MIR processing |
|
| 2019-04-09 13:11:51 |
Mathieu Trudel-Lapierre |
mailman (Ubuntu): status |
New |
Triaged |
|
| 2019-04-09 13:17:36 |
Christian Ehrhardt |
description |
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for https://lists.canonical.com/mailman3/postorius/lists/
This source builds only docs and mailman3 itself (which provides mailman3-core).
[Rationale]
This is part of the MIR activity for all dependencies of mailman3
The "main" MIR of it is at bug 1775427:
Mailman (2) has only python2 support, but we strive for python3,
therefore Mailman3 which has python3 support should be promoted to main.
This is an evolution of the mailman2 core delivery engine of the system, but I can't guess how much it deviated so we need to recheck security (IMHO)
[Security]
No known CVEs found.
A few old issues can be found against mailman2 and one (but long fixed) for mailman 3
=> https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=mailman
[Quality assurance]
The mailman3 stacks as of now (Disco) installs fine and provides a base
config. But due to the nature of the package that needs further modification
to be of real use.
The package does in error cases ask a debconf-high question, but it is not going to be installed by default - so that is no MIR problem.
There are a few (2) Ubuntu bugs outstanding, but none of them is critical and stopping this MIR request.
There are a few (2) Debian bugs outstanding all seems to "just work" still, but when we main this in 19.10 we should at least evaluate and maybe adress this one:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921445
There are regular upstream releases and Debian packages them and fixes regularly.
No exotic HW involved.
The package ships a test suite, but it is not run at build time for upstream bug #400.
It tests things in a dep8 test thou to provide coverage.
d/watch is set up and ok.
No Lintian warning except fairly recent newer Standards version.
The package does not rely on demoted or obsolete packages.
[UI standards]
Comes with 7 translations in .po files
No End-user applications that needs a standard conformant desktop file.
[Dependencies]
Some dependencies are not in main, but we drive MIR for all related packages
that are not in main at the same time.
Please check the list of bugs from the main Mailman3 MIR in bug 1775427 to get an overview.
[Standards compliance]
The package meets the FHS and Debian Policy standards.
The packaging itself is very straight forward and uses dh_* as much as possible - the d/rules fits on one screen.
[Maintenance]
The Server team will subscribe for the package for maintenance
[Background]
The package description explains the general purpose and context of the package well.
---
References to all the related MIR bug - one per affected package.
Status (simplified version of https://wiki.ubuntu.com/MIRTeam#Process_states)
(nothing) means we have not even prepared the MIR yet
- MIR not needed (e.g. dependency will be dropped)
* all of the template fields for the MIR are complete
! waiting for MIR review
? cpaelzer needs experienced MIR team members to continue
S needs security review to be accepted
+ MIR accepted
x MIR nacked
Extra Flags which team members or on review feedback can be added:
T extra work for the team that should be done before 20.04 (state todo after package)
M extra work for the team before getting MIR to be acceptable (read as asap)
C needed if only promoting mailman3 (core)
H needed if only promoting mailman3 (core) plus Hyperkitty
J no more needed for mailman3-web if we can cut node-less out
FLAGS | MIR-Bug | Package (Notes)
TC
MH
----------------------------------------
S | bug 1820179 | coreapi
+ | bug 1820180 | coreschema
S | bug 1820181 | django-allauth
+ | bug 1820182 | django-filter
S | bug 1820183 | django-guardian
+ | bug 1820185 | django-haystack
S | bug 1820186 | django-mailman3
- | | django-paintstore ((no dep hyperkitty >=1.2.2-1)
+ | bug 1820188 | django-picklefield
+ | bug 1820189 | django-q
S | bug 1820190 | djangorestframework
S C | bug 1820191 | flufl.bounce
+ C | bug 1820192 | flufl.i18n
+ C | bug 1820193 | flufl.lock
? | bug 1820195 | glewlwyd (likely need to break dep to this)
S | bug 1820196 | hyperkitty
+ | bug 1820197 | itypes
- | n/a | jqueryui (no dep hyperkitty >=1.2.2-1)
+ C | bug 1820199 | lazr.config
+TC | bug 1820200 | lazr.delegates (opt: update; suggest dropping nose)
-MJ | bug 1820201 | less.js (Dep will be cut out in Debian bug 924961)
- | n/a | libjs-jquery-colorpicker (no hyperkitty >=1.2.2-1)
S | bug 1820202 | libmatheval
S | bug 1820203 | libpgm
S C | bug 1775427 | mailman3
S | bug 1820204 | mailmanclient
S H | bug 1820205 | mailman-hyperkitty
S | bug 1820206 | mailman-suite
-MJ | bug 1820207 | node-source-map (wait for node-less dep to be cut)
-MJ | bug 1820208 | nodejs (wait for node-less dep to be cut)
S+? | bug 1820209 | norm (check if embedded protolib is an issue)
+ | bug 1820982 | nose
S | bug 1820210 | postorius
S | bug 1820211 | python3-openid
S C | bug 1820212 | python-aiosmtpd
+T | bug 1820213 | python-arrow (non fatal build error on dateutil, tests)
+ | bug 1820214 | python-blessed
S+? | bug 1820215 | python-django-extensions (many functions in one package)
S | bug 1820216 | python-django-gravatar2
STC | bug 1820217 | python-falcon (opt: update version before 20.04)
+ | bug 686045 | python-lockfile
+TC | bug 1820220 | python-public (opt: update version before 20.04)
S | bug 1820221 | python-requests-oauthlib
+T | bug 1820223 | python-uritemplate (be a sync, better new upstream)
S | bug 1820224 | python-whoosh
S | bug 1820225 | robot-detection
-M | n/a | ruby-sass (deprecated, use sassc - Debian 924629)
-M | TBD | sassc (Dep will be cut by Debian bug 924961)
-M | TBD | libsass (Dep will be cut by Debian bug 924961)
? | bug 1820226 | twitter-bootstrap3
? | bug 1820227 | uwsgi (FTBFS: #1820095)
+ | bug 1820229 | wcwidth
+ | bug 1597439 | zeromq3
STC | bug 1820233 | zope.component (version update)
STC | bug 1820234 | zope.configuration (version update)
STC | bug 1820236 | zope.event (version update)
STC | bug 1820237 | zope.hookable (version update)
STC | bug 1820238 | zope.i18nmessageid (version update)
STC | bug 1820239 | zope.schema (version update)
List Debian bugs we depend on being resolved as expected before
the dependency tree can completely be MIRed:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924629
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924961
This might sometimes be slightly out of date, to cross check and for history on all of them check git at:
https://git.launchpad.net/~ubuntu-server/+git/mailman3-MIR-party/tree/package-list.txt
---
Past Decisions in regard to this:
mailman is python2, mailman3 is python3, but also it has new dependency stack due to adopting django but also splitting or rewriting a lot of its components.
Q: Do we want bin:mailman3 or bin:mailman3-full in main? (the latter pulls
in src:mailman-suite as well). src:mailman-suite has potentially more
things - django, hyperkitty, ruby-sass, uwsgi...
A: We analyzed this and we will need the full set of dependencies, even
meaning MIRs are needed for all of the above listed (and more).
Q: Before proceeding further with assignment/doing technical work in
driving above MIRs, a product level yes/no answers should probably be
answered for above two questions.
A: Discussed in several sprints now, as uncomfortable as it is we will go
through the mass-MIR processing |
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for https://lists.canonical.com/mailman3/postorius/lists/
This source builds only docs and mailman3 itself (which provides mailman3-core).
[Rationale]
This is part of the MIR activity for all dependencies of mailman3
The "main" MIR of it is at bug 1775427:
Mailman (2) has only python2 support, but we strive for python3,
therefore Mailman3 which has python3 support should be promoted to main.
This is an evolution of the mailman2 core delivery engine of the system, but I can't guess how much it deviated so we need to recheck security (IMHO)
[Security]
No known CVEs found.
A few old issues can be found against mailman2 and one (but long fixed) for mailman 3
=> https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=mailman
[Quality assurance]
The mailman3 stacks as of now (Disco) installs fine and provides a base
config. But due to the nature of the package that needs further modification
to be of real use.
The package does in error cases ask a debconf-high question, but it is not going to be installed by default - so that is no MIR problem.
There are a few (2) Ubuntu bugs outstanding, but none of them is critical and stopping this MIR request.
There are a few (2) Debian bugs outstanding all seems to "just work" still, but when we main this in 19.10 we should at least evaluate and maybe adress this one:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921445
There are regular upstream releases and Debian packages them and fixes regularly.
No exotic HW involved.
The package ships a test suite, but it is not run at build time for upstream bug #400.
It tests things in a dep8 test thou to provide coverage.
d/watch is set up and ok.
No Lintian warning except fairly recent newer Standards version.
The package does not rely on demoted or obsolete packages.
[UI standards]
Comes with 7 translations in .po files
No End-user applications that needs a standard conformant desktop file.
[Dependencies]
Some dependencies are not in main, but we drive MIR for all related packages
that are not in main at the same time.
Please check the list of bugs from the main Mailman3 MIR in bug 1775427 to get an overview.
[Standards compliance]
The package meets the FHS and Debian Policy standards.
The packaging itself is very straight forward and uses dh_* as much as possible - the d/rules fits on one screen.
[Maintenance]
The Server team will subscribe for the package for maintenance
[Background]
The package description explains the general purpose and context of the package well.
---
References to all the related MIR bug - one per affected package.
Status (simplified version of https://wiki.ubuntu.com/MIRTeam#Process_states)
(nothing) means we have not even prepared the MIR yet
- MIR not needed (e.g. dependency will be dropped)
* all of the template fields for the MIR are complete
! waiting for MIR review
? cpaelzer needs experienced MIR team members to continue
S needs security review to be accepted
+ MIR accepted
x MIR nacked
Extra Flags which team members or on review feedback can be added:
T extra work for the team that should be done before 20.04 (state todo after package)
M extra work for the team before getting MIR to be acceptable (read as asap)
C needed if only promoting mailman3 (core)
H needed if only promoting mailman3 (core) plus Hyperkitty
J no more needed for mailman3-web if we can cut node-less out
FLAGS | MIR-Bug | Package (Notes)
TC
MH
----------------------------------------
S | bug 1820179 | coreapi
+ | bug 1820180 | coreschema
S | bug 1820181 | django-allauth
+ | bug 1820182 | django-filter
S | bug 1820183 | django-guardian
+ | bug 1820185 | django-haystack
S | bug 1820186 | django-mailman3
- | | django-paintstore ((no dep hyperkitty >=1.2.2-1)
+ | bug 1820188 | django-picklefield
+ | bug 1820189 | django-q
S | bug 1820190 | djangorestframework
S C | bug 1820191 | flufl.bounce
+ C | bug 1820192 | flufl.i18n
+ C | bug 1820193 | flufl.lock
M | bug 1820195 | glewlwyd (likely need to break dep to this)
S | bug 1820196 | hyperkitty
+ | bug 1820197 | itypes
- | n/a | jqueryui (no dep hyperkitty >=1.2.2-1)
+ C | bug 1820199 | lazr.config
+TC | bug 1820200 | lazr.delegates (opt: update; suggest dropping nose)
-MJ | bug 1820201 | less.js (Dep will be cut out in Debian bug 924961)
- | n/a | libjs-jquery-colorpicker (no hyperkitty >=1.2.2-1)
S | bug 1820202 | libmatheval
S | bug 1820203 | libpgm
S C | bug 1775427 | mailman3
S | bug 1820204 | mailmanclient
S H | bug 1820205 | mailman-hyperkitty
S | bug 1820206 | mailman-suite
-MJ | bug 1820207 | node-source-map (wait for node-less dep to be cut)
-MJ | bug 1820208 | nodejs (wait for node-less dep to be cut)
S+? | bug 1820209 | norm (check if embedded protolib is an issue)
+ | bug 1820982 | nose
S | bug 1820210 | postorius
S | bug 1820211 | python3-openid
S C | bug 1820212 | python-aiosmtpd
+T | bug 1820213 | python-arrow (non fatal build error on dateutil, tests)
+ | bug 1820214 | python-blessed
S+? | bug 1820215 | python-django-extensions (many functions in one package)
S | bug 1820216 | python-django-gravatar2
STC | bug 1820217 | python-falcon (opt: update version before 20.04)
+ | bug 686045 | python-lockfile
+TC | bug 1820220 | python-public (opt: update version before 20.04)
S | bug 1820221 | python-requests-oauthlib
+T | bug 1820223 | python-uritemplate (be a sync, better new upstream)
S | bug 1820224 | python-whoosh
S | bug 1820225 | robot-detection
-M | n/a | ruby-sass (deprecated, use sassc - Debian 924629)
-M | TBD | sassc (Dep will be cut by Debian bug 924961)
-M | TBD | libsass (Dep will be cut by Debian bug 924961)
? | bug 1820226 | twitter-bootstrap3
? | bug 1820227 | uwsgi (FTBFS: #1820095)
+ | bug 1820229 | wcwidth
+ | bug 1597439 | zeromq3
STC | bug 1820233 | zope.component (version update)
STC | bug 1820234 | zope.configuration (version update)
STC | bug 1820236 | zope.event (version update)
STC | bug 1820237 | zope.hookable (version update)
STC | bug 1820238 | zope.i18nmessageid (version update)
STC | bug 1820239 | zope.schema (version update)
List Debian bugs we depend on being resolved as expected before
the dependency tree can completely be MIRed:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924629
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924961
This might sometimes be slightly out of date, to cross check and for history on all of them check git at:
https://git.launchpad.net/~ubuntu-server/+git/mailman3-MIR-party/tree/package-list.txt
---
Past Decisions in regard to this:
mailman is python2, mailman3 is python3, but also it has new dependency stack due to adopting django but also splitting or rewriting a lot of its components.
Q: Do we want bin:mailman3 or bin:mailman3-full in main? (the latter pulls
in src:mailman-suite as well). src:mailman-suite has potentially more
things - django, hyperkitty, ruby-sass, uwsgi...
A: We analyzed this and we will need the full set of dependencies, even
meaning MIRs are needed for all of the above listed (and more).
Q: Before proceeding further with assignment/doing technical work in
driving above MIRs, a product level yes/no answers should probably be
answered for above two questions.
A: Discussed in several sprints now, as uncomfortable as it is we will go
through the mass-MIR processing |
|
| 2019-04-09 13:28:03 |
Christian Ehrhardt |
description |
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for https://lists.canonical.com/mailman3/postorius/lists/
This source builds only docs and mailman3 itself (which provides mailman3-core).
[Rationale]
This is part of the MIR activity for all dependencies of mailman3
The "main" MIR of it is at bug 1775427:
Mailman (2) has only python2 support, but we strive for python3,
therefore Mailman3 which has python3 support should be promoted to main.
This is an evolution of the mailman2 core delivery engine of the system, but I can't guess how much it deviated so we need to recheck security (IMHO)
[Security]
No known CVEs found.
A few old issues can be found against mailman2 and one (but long fixed) for mailman 3
=> https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=mailman
[Quality assurance]
The mailman3 stacks as of now (Disco) installs fine and provides a base
config. But due to the nature of the package that needs further modification
to be of real use.
The package does in error cases ask a debconf-high question, but it is not going to be installed by default - so that is no MIR problem.
There are a few (2) Ubuntu bugs outstanding, but none of them is critical and stopping this MIR request.
There are a few (2) Debian bugs outstanding all seems to "just work" still, but when we main this in 19.10 we should at least evaluate and maybe adress this one:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921445
There are regular upstream releases and Debian packages them and fixes regularly.
No exotic HW involved.
The package ships a test suite, but it is not run at build time for upstream bug #400.
It tests things in a dep8 test thou to provide coverage.
d/watch is set up and ok.
No Lintian warning except fairly recent newer Standards version.
The package does not rely on demoted or obsolete packages.
[UI standards]
Comes with 7 translations in .po files
No End-user applications that needs a standard conformant desktop file.
[Dependencies]
Some dependencies are not in main, but we drive MIR for all related packages
that are not in main at the same time.
Please check the list of bugs from the main Mailman3 MIR in bug 1775427 to get an overview.
[Standards compliance]
The package meets the FHS and Debian Policy standards.
The packaging itself is very straight forward and uses dh_* as much as possible - the d/rules fits on one screen.
[Maintenance]
The Server team will subscribe for the package for maintenance
[Background]
The package description explains the general purpose and context of the package well.
---
References to all the related MIR bug - one per affected package.
Status (simplified version of https://wiki.ubuntu.com/MIRTeam#Process_states)
(nothing) means we have not even prepared the MIR yet
- MIR not needed (e.g. dependency will be dropped)
* all of the template fields for the MIR are complete
! waiting for MIR review
? cpaelzer needs experienced MIR team members to continue
S needs security review to be accepted
+ MIR accepted
x MIR nacked
Extra Flags which team members or on review feedback can be added:
T extra work for the team that should be done before 20.04 (state todo after package)
M extra work for the team before getting MIR to be acceptable (read as asap)
C needed if only promoting mailman3 (core)
H needed if only promoting mailman3 (core) plus Hyperkitty
J no more needed for mailman3-web if we can cut node-less out
FLAGS | MIR-Bug | Package (Notes)
TC
MH
----------------------------------------
S | bug 1820179 | coreapi
+ | bug 1820180 | coreschema
S | bug 1820181 | django-allauth
+ | bug 1820182 | django-filter
S | bug 1820183 | django-guardian
+ | bug 1820185 | django-haystack
S | bug 1820186 | django-mailman3
- | | django-paintstore ((no dep hyperkitty >=1.2.2-1)
+ | bug 1820188 | django-picklefield
+ | bug 1820189 | django-q
S | bug 1820190 | djangorestframework
S C | bug 1820191 | flufl.bounce
+ C | bug 1820192 | flufl.i18n
+ C | bug 1820193 | flufl.lock
M | bug 1820195 | glewlwyd (likely need to break dep to this)
S | bug 1820196 | hyperkitty
+ | bug 1820197 | itypes
- | n/a | jqueryui (no dep hyperkitty >=1.2.2-1)
+ C | bug 1820199 | lazr.config
+TC | bug 1820200 | lazr.delegates (opt: update; suggest dropping nose)
-MJ | bug 1820201 | less.js (Dep will be cut out in Debian bug 924961)
- | n/a | libjs-jquery-colorpicker (no hyperkitty >=1.2.2-1)
S | bug 1820202 | libmatheval
S | bug 1820203 | libpgm
S C | bug 1775427 | mailman3
S | bug 1820204 | mailmanclient
S H | bug 1820205 | mailman-hyperkitty
S | bug 1820206 | mailman-suite
-MJ | bug 1820207 | node-source-map (wait for node-less dep to be cut)
-MJ | bug 1820208 | nodejs (wait for node-less dep to be cut)
S+? | bug 1820209 | norm (check if embedded protolib is an issue)
+ | bug 1820982 | nose
S | bug 1820210 | postorius
S | bug 1820211 | python3-openid
S C | bug 1820212 | python-aiosmtpd
+T | bug 1820213 | python-arrow (non fatal build error on dateutil, tests)
+ | bug 1820214 | python-blessed
S+? | bug 1820215 | python-django-extensions (many functions in one package)
S | bug 1820216 | python-django-gravatar2
STC | bug 1820217 | python-falcon (opt: update version before 20.04)
+ | bug 686045 | python-lockfile
+TC | bug 1820220 | python-public (opt: update version before 20.04)
S | bug 1820221 | python-requests-oauthlib
+T | bug 1820223 | python-uritemplate (be a sync, better new upstream)
S | bug 1820224 | python-whoosh
S | bug 1820225 | robot-detection
-M | n/a | ruby-sass (deprecated, use sassc - Debian 924629)
-M | TBD | sassc (Dep will be cut by Debian bug 924961)
-M | TBD | libsass (Dep will be cut by Debian bug 924961)
? | bug 1820226 | twitter-bootstrap3
? | bug 1820227 | uwsgi (FTBFS: #1820095)
+ | bug 1820229 | wcwidth
+ | bug 1597439 | zeromq3
STC | bug 1820233 | zope.component (version update)
STC | bug 1820234 | zope.configuration (version update)
STC | bug 1820236 | zope.event (version update)
STC | bug 1820237 | zope.hookable (version update)
STC | bug 1820238 | zope.i18nmessageid (version update)
STC | bug 1820239 | zope.schema (version update)
List Debian bugs we depend on being resolved as expected before
the dependency tree can completely be MIRed:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924629
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924961
This might sometimes be slightly out of date, to cross check and for history on all of them check git at:
https://git.launchpad.net/~ubuntu-server/+git/mailman3-MIR-party/tree/package-list.txt
---
Past Decisions in regard to this:
mailman is python2, mailman3 is python3, but also it has new dependency stack due to adopting django but also splitting or rewriting a lot of its components.
Q: Do we want bin:mailman3 or bin:mailman3-full in main? (the latter pulls
in src:mailman-suite as well). src:mailman-suite has potentially more
things - django, hyperkitty, ruby-sass, uwsgi...
A: We analyzed this and we will need the full set of dependencies, even
meaning MIRs are needed for all of the above listed (and more).
Q: Before proceeding further with assignment/doing technical work in
driving above MIRs, a product level yes/no answers should probably be
answered for above two questions.
A: Discussed in several sprints now, as uncomfortable as it is we will go
through the mass-MIR processing |
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for https://lists.canonical.com/mailman3/postorius/lists/
This source builds only docs and mailman3 itself (which provides mailman3-core).
[Rationale]
This is part of the MIR activity for all dependencies of mailman3
The "main" MIR of it is at bug 1775427:
Mailman (2) has only python2 support, but we strive for python3,
therefore Mailman3 which has python3 support should be promoted to main.
This is an evolution of the mailman2 core delivery engine of the system, but I can't guess how much it deviated so we need to recheck security (IMHO)
[Security]
No known CVEs found.
A few old issues can be found against mailman2 and one (but long fixed) for mailman 3
=> https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=mailman
[Quality assurance]
The mailman3 stacks as of now (Disco) installs fine and provides a base
config. But due to the nature of the package that needs further modification
to be of real use.
The package does in error cases ask a debconf-high question, but it is not going to be installed by default - so that is no MIR problem.
There are a few (2) Ubuntu bugs outstanding, but none of them is critical and stopping this MIR request.
There are a few (2) Debian bugs outstanding all seems to "just work" still, but when we main this in 19.10 we should at least evaluate and maybe adress this one:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921445
There are regular upstream releases and Debian packages them and fixes regularly.
No exotic HW involved.
The package ships a test suite, but it is not run at build time for upstream bug #400.
It tests things in a dep8 test thou to provide coverage.
d/watch is set up and ok.
No Lintian warning except fairly recent newer Standards version.
The package does not rely on demoted or obsolete packages.
[UI standards]
Comes with 7 translations in .po files
No End-user applications that needs a standard conformant desktop file.
[Dependencies]
Some dependencies are not in main, but we drive MIR for all related packages
that are not in main at the same time.
Please check the list of bugs from the main Mailman3 MIR in bug 1775427 to get an overview.
[Standards compliance]
The package meets the FHS and Debian Policy standards.
The packaging itself is very straight forward and uses dh_* as much as possible - the d/rules fits on one screen.
[Maintenance]
The Server team will subscribe for the package for maintenance
[Background]
The package description explains the general purpose and context of the package well.
---
References to all the related MIR bug - one per affected package.
Status (simplified version of https://wiki.ubuntu.com/MIRTeam#Process_states)
(nothing) means we have not even prepared the MIR yet
- MIR not needed (e.g. dependency will be dropped)
* all of the template fields for the MIR are complete
! waiting for MIR review
? cpaelzer needs experienced MIR team members to continue
S needs security review to be accepted
+ MIR accepted
x MIR nacked
Extra Flags which team members or on review feedback can be added:
T extra work for the team that should be done before 20.04 (state todo after package)
M extra work for the team before getting MIR to be acceptable (read as asap)
C needed if only promoting mailman3 (core)
H needed if only promoting mailman3 (core) plus Hyperkitty
J no more needed for mailman3-web if we can cut node-less out
FLAGS | MIR-Bug | Package (Notes)
TC
MH
----------------------------------------
S | bug 1820179 | coreapi
+ | bug 1820180 | coreschema
S | bug 1820181 | django-allauth
+ | bug 1820182 | django-filter
S | bug 1820183 | django-guardian
+ | bug 1820185 | django-haystack
S | bug 1820186 | django-mailman3
- | | django-paintstore ((no dep hyperkitty >=1.2.2-1)
+ | bug 1820188 | django-picklefield
+ | bug 1820189 | django-q
S | bug 1820190 | djangorestframework
S C | bug 1820191 | flufl.bounce
+ C | bug 1820192 | flufl.i18n
+ C | bug 1820193 | flufl.lock
M | bug 1820195 | glewlwyd (likely need to break dep to this)
S | bug 1820196 | hyperkitty
+ | bug 1820197 | itypes
- | n/a | jqueryui (no dep hyperkitty >=1.2.2-1)
+ C | bug 1820199 | lazr.config
+TC | bug 1820200 | lazr.delegates (opt: update; suggest dropping nose)
-MJ | bug 1820201 | less.js (Dep will be cut out in Debian bug 924961)
- | n/a | libjs-jquery-colorpicker (no hyperkitty >=1.2.2-1)
S | bug 1820202 | libmatheval
S | bug 1820203 | libpgm
S C | bug 1775427 | mailman3
S | bug 1820204 | mailmanclient
S H | bug 1820205 | mailman-hyperkitty
S | bug 1820206 | mailman-suite
-MJ | bug 1820207 | node-source-map (wait for node-less dep to be cut)
-MJ | bug 1820208 | nodejs (wait for node-less dep to be cut)
S+? | bug 1820209 | norm (check if embedded protolib is an issue)
+ | bug 1820982 | nose
S | bug 1820210 | postorius
S | bug 1820211 | python3-openid
S C | bug 1820212 | python-aiosmtpd
+T | bug 1820213 | python-arrow (non fatal build error on dateutil, tests)
+ | bug 1820214 | python-blessed
S+? | bug 1820215 | python-django-extensions (many functions in one package)
S | bug 1820216 | python-django-gravatar2
STC | bug 1820217 | python-falcon (opt: update version before 20.04)
+ | bug 686045 | python-lockfile
+TC | bug 1820220 | python-public (opt: update version before 20.04)
S | bug 1820221 | python-requests-oauthlib
+T | bug 1820223 | python-uritemplate (be a sync, better new upstream)
S | bug 1820224 | python-whoosh
S | bug 1820225 | robot-detection
-M | n/a | ruby-sass (deprecated, use sassc - Debian 924629)
-M | TBD | sassc (Dep will be cut by Debian bug 924961)
-M | TBD | libsass (Dep will be cut by Debian bug 924961)
? | bug 1820226 | twitter-bootstrap3 (assigned to cyphermox)
? | bug 1820227 | uwsgi (FTBFS: #1820095) (assigned to cyphermox)
+ | bug 1820229 | wcwidth
+ | bug 1597439 | zeromq3
STC | bug 1820233 | zope.component (version update)
STC | bug 1820234 | zope.configuration (version update)
STC | bug 1820236 | zope.event (version update)
STC | bug 1820237 | zope.hookable (version update)
STC | bug 1820238 | zope.i18nmessageid (version update)
STC | bug 1820239 | zope.schema (version update)
List Debian bugs we depend on being resolved as expected before
the dependency tree can completely be MIRed:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924629
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924961
This might sometimes be slightly out of date, to cross check and for history on all of them check git at:
https://git.launchpad.net/~ubuntu-server/+git/mailman3-MIR-party/tree/package-list.txt
---
Past Decisions in regard to this:
mailman is python2, mailman3 is python3, but also it has new dependency stack due to adopting django but also splitting or rewriting a lot of its components.
Q: Do we want bin:mailman3 or bin:mailman3-full in main? (the latter pulls
in src:mailman-suite as well). src:mailman-suite has potentially more
things - django, hyperkitty, ruby-sass, uwsgi...
A: We analyzed this and we will need the full set of dependencies, even
meaning MIRs are needed for all of the above listed (and more).
Q: Before proceeding further with assignment/doing technical work in
driving above MIRs, a product level yes/no answers should probably be
answered for above two questions.
A: Discussed in several sprints now, as uncomfortable as it is we will go
through the mass-MIR processing |
|
| 2019-04-11 09:44:41 |
Christian Ehrhardt |
description |
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for https://lists.canonical.com/mailman3/postorius/lists/
This source builds only docs and mailman3 itself (which provides mailman3-core).
[Rationale]
This is part of the MIR activity for all dependencies of mailman3
The "main" MIR of it is at bug 1775427:
Mailman (2) has only python2 support, but we strive for python3,
therefore Mailman3 which has python3 support should be promoted to main.
This is an evolution of the mailman2 core delivery engine of the system, but I can't guess how much it deviated so we need to recheck security (IMHO)
[Security]
No known CVEs found.
A few old issues can be found against mailman2 and one (but long fixed) for mailman 3
=> https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=mailman
[Quality assurance]
The mailman3 stacks as of now (Disco) installs fine and provides a base
config. But due to the nature of the package that needs further modification
to be of real use.
The package does in error cases ask a debconf-high question, but it is not going to be installed by default - so that is no MIR problem.
There are a few (2) Ubuntu bugs outstanding, but none of them is critical and stopping this MIR request.
There are a few (2) Debian bugs outstanding all seems to "just work" still, but when we main this in 19.10 we should at least evaluate and maybe adress this one:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921445
There are regular upstream releases and Debian packages them and fixes regularly.
No exotic HW involved.
The package ships a test suite, but it is not run at build time for upstream bug #400.
It tests things in a dep8 test thou to provide coverage.
d/watch is set up and ok.
No Lintian warning except fairly recent newer Standards version.
The package does not rely on demoted or obsolete packages.
[UI standards]
Comes with 7 translations in .po files
No End-user applications that needs a standard conformant desktop file.
[Dependencies]
Some dependencies are not in main, but we drive MIR for all related packages
that are not in main at the same time.
Please check the list of bugs from the main Mailman3 MIR in bug 1775427 to get an overview.
[Standards compliance]
The package meets the FHS and Debian Policy standards.
The packaging itself is very straight forward and uses dh_* as much as possible - the d/rules fits on one screen.
[Maintenance]
The Server team will subscribe for the package for maintenance
[Background]
The package description explains the general purpose and context of the package well.
---
References to all the related MIR bug - one per affected package.
Status (simplified version of https://wiki.ubuntu.com/MIRTeam#Process_states)
(nothing) means we have not even prepared the MIR yet
- MIR not needed (e.g. dependency will be dropped)
* all of the template fields for the MIR are complete
! waiting for MIR review
? cpaelzer needs experienced MIR team members to continue
S needs security review to be accepted
+ MIR accepted
x MIR nacked
Extra Flags which team members or on review feedback can be added:
T extra work for the team that should be done before 20.04 (state todo after package)
M extra work for the team before getting MIR to be acceptable (read as asap)
C needed if only promoting mailman3 (core)
H needed if only promoting mailman3 (core) plus Hyperkitty
J no more needed for mailman3-web if we can cut node-less out
FLAGS | MIR-Bug | Package (Notes)
TC
MH
----------------------------------------
S | bug 1820179 | coreapi
+ | bug 1820180 | coreschema
S | bug 1820181 | django-allauth
+ | bug 1820182 | django-filter
S | bug 1820183 | django-guardian
+ | bug 1820185 | django-haystack
S | bug 1820186 | django-mailman3
- | | django-paintstore ((no dep hyperkitty >=1.2.2-1)
+ | bug 1820188 | django-picklefield
+ | bug 1820189 | django-q
S | bug 1820190 | djangorestframework
S C | bug 1820191 | flufl.bounce
+ C | bug 1820192 | flufl.i18n
+ C | bug 1820193 | flufl.lock
M | bug 1820195 | glewlwyd (likely need to break dep to this)
S | bug 1820196 | hyperkitty
+ | bug 1820197 | itypes
- | n/a | jqueryui (no dep hyperkitty >=1.2.2-1)
+ C | bug 1820199 | lazr.config
+TC | bug 1820200 | lazr.delegates (opt: update; suggest dropping nose)
-MJ | bug 1820201 | less.js (Dep will be cut out in Debian bug 924961)
- | n/a | libjs-jquery-colorpicker (no hyperkitty >=1.2.2-1)
S | bug 1820202 | libmatheval
S | bug 1820203 | libpgm
S C | bug 1775427 | mailman3
S | bug 1820204 | mailmanclient
S H | bug 1820205 | mailman-hyperkitty
S | bug 1820206 | mailman-suite
-MJ | bug 1820207 | node-source-map (wait for node-less dep to be cut)
-MJ | bug 1820208 | nodejs (wait for node-less dep to be cut)
S+? | bug 1820209 | norm (check if embedded protolib is an issue)
+ | bug 1820982 | nose
S | bug 1820210 | postorius
S | bug 1820211 | python3-openid
S C | bug 1820212 | python-aiosmtpd
+T | bug 1820213 | python-arrow (non fatal build error on dateutil, tests)
+ | bug 1820214 | python-blessed
S+? | bug 1820215 | python-django-extensions (many functions in one package)
S | bug 1820216 | python-django-gravatar2
STC | bug 1820217 | python-falcon (opt: update version before 20.04)
+ | bug 686045 | python-lockfile
+TC | bug 1820220 | python-public (opt: update version before 20.04)
S | bug 1820221 | python-requests-oauthlib
+T | bug 1820223 | python-uritemplate (be a sync, better new upstream)
S | bug 1820224 | python-whoosh
S | bug 1820225 | robot-detection
-M | n/a | ruby-sass (deprecated, use sassc - Debian 924629)
-M | TBD | sassc (Dep will be cut by Debian bug 924961)
-M | TBD | libsass (Dep will be cut by Debian bug 924961)
? | bug 1820226 | twitter-bootstrap3 (assigned to cyphermox)
? | bug 1820227 | uwsgi (FTBFS: #1820095) (assigned to cyphermox)
+ | bug 1820229 | wcwidth
+ | bug 1597439 | zeromq3
STC | bug 1820233 | zope.component (version update)
STC | bug 1820234 | zope.configuration (version update)
STC | bug 1820236 | zope.event (version update)
STC | bug 1820237 | zope.hookable (version update)
STC | bug 1820238 | zope.i18nmessageid (version update)
STC | bug 1820239 | zope.schema (version update)
List Debian bugs we depend on being resolved as expected before
the dependency tree can completely be MIRed:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924629
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924961
This might sometimes be slightly out of date, to cross check and for history on all of them check git at:
https://git.launchpad.net/~ubuntu-server/+git/mailman3-MIR-party/tree/package-list.txt
---
Past Decisions in regard to this:
mailman is python2, mailman3 is python3, but also it has new dependency stack due to adopting django but also splitting or rewriting a lot of its components.
Q: Do we want bin:mailman3 or bin:mailman3-full in main? (the latter pulls
in src:mailman-suite as well). src:mailman-suite has potentially more
things - django, hyperkitty, ruby-sass, uwsgi...
A: We analyzed this and we will need the full set of dependencies, even
meaning MIRs are needed for all of the above listed (and more).
Q: Before proceeding further with assignment/doing technical work in
driving above MIRs, a product level yes/no answers should probably be
answered for above two questions.
A: Discussed in several sprints now, as uncomfortable as it is we will go
through the mass-MIR processing |
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for https://lists.canonical.com/mailman3/postorius/lists/
This source builds only docs and mailman3 itself (which provides mailman3-core).
[Rationale]
This is part of the MIR activity for all dependencies of mailman3
The "main" MIR of it is at bug 1775427:
Mailman (2) has only python2 support, but we strive for python3,
therefore Mailman3 which has python3 support should be promoted to main.
This is an evolution of the mailman2 core delivery engine of the system, but I can't guess how much it deviated so we need to recheck security (IMHO)
[Security]
No known CVEs found.
A few old issues can be found against mailman2 and one (but long fixed) for mailman 3
=> https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=mailman
[Quality assurance]
The mailman3 stacks as of now (Disco) installs fine and provides a base
config. But due to the nature of the package that needs further modification
to be of real use.
The package does in error cases ask a debconf-high question, but it is not going to be installed by default - so that is no MIR problem.
There are a few (2) Ubuntu bugs outstanding, but none of them is critical and stopping this MIR request.
There are a few (2) Debian bugs outstanding all seems to "just work" still, but when we main this in 19.10 we should at least evaluate and maybe adress this one:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921445
There are regular upstream releases and Debian packages them and fixes regularly.
No exotic HW involved.
The package ships a test suite, but it is not run at build time for upstream bug #400.
It tests things in a dep8 test thou to provide coverage.
d/watch is set up and ok.
No Lintian warning except fairly recent newer Standards version.
The package does not rely on demoted or obsolete packages.
[UI standards]
Comes with 7 translations in .po files
No End-user applications that needs a standard conformant desktop file.
[Dependencies]
Some dependencies are not in main, but we drive MIR for all related packages
that are not in main at the same time.
Please check the list of bugs from the main Mailman3 MIR in bug 1775427 to get an overview.
[Standards compliance]
The package meets the FHS and Debian Policy standards.
The packaging itself is very straight forward and uses dh_* as much as possible - the d/rules fits on one screen.
[Maintenance]
The Server team will subscribe for the package for maintenance
[Background]
The package description explains the general purpose and context of the package well.
---
References to all the related MIR bug - one per affected package.
Status (simplified version of https://wiki.ubuntu.com/MIRTeam#Process_states)
(nothing) means we have not even prepared the MIR yet
- MIR not needed (e.g. dependency will be dropped)
* all of the template fields for the MIR are complete
! waiting for MIR review
? cpaelzer needs experienced MIR team members to continue
S needs security review to be accepted
+ MIR accepted
x MIR nacked
Extra Flags which team members or on review feedback can be added:
T extra work for the team that should be done before 20.04 (state todo after package)
M extra work for the team before getting MIR to be acceptable (read as asap)
C needed if only promoting mailman3 (core)
H needed if only promoting mailman3 (core) plus Hyperkitty
J no more needed for mailman3-web if we can cut node-less out
FLAGS | MIR-Bug | Package (Notes)
TC
MH
----------------------------------------
S | bug 1820179 | coreapi
+ | bug 1820180 | coreschema
S | bug 1820181 | django-allauth
+ | bug 1820182 | django-filter
S | bug 1820183 | django-guardian
+ | bug 1820185 | django-haystack
S | bug 1820186 | django-mailman3
- | | django-paintstore ((no dep hyperkitty >=1.2.2-1)
+ | bug 1820188 | django-picklefield
+ | bug 1820189 | django-q
S | bug 1820190 | djangorestframework
S C | bug 1820191 | flufl.bounce
+ C | bug 1820192 | flufl.i18n
+ C | bug 1820193 | flufl.lock
M | bug 1820195 | glewlwyd (likely need to break dep to this)
S | bug 1820196 | hyperkitty
+ | bug 1820197 | itypes
- | n/a | jqueryui (no dep hyperkitty >=1.2.2-1)
+ C | bug 1820199 | lazr.config
+TC | bug 1820200 | lazr.delegates (opt: update; suggest dropping nose)
-MJ | bug 1820201 | less.js (Dep will be cut out in Debian bug 924961)
- | n/a | libjs-jquery-colorpicker (no hyperkitty >=1.2.2-1)
S | bug 1820202 | libmatheval
S | bug 1820203 | libpgm
S C | bug 1775427 | mailman3
S | bug 1820204 | mailmanclient
S H | bug 1820205 | mailman-hyperkitty
S | bug 1820206 | mailman-suite
-MJ | bug 1820207 | node-source-map (wait for node-less dep to be cut)
-MJ | bug 1820208 | nodejs (wait for node-less dep to be cut)
S+? | bug 1820209 | norm (check if embedded protolib is an issue)
+ | bug 1820982 | nose
S | bug 1820210 | postorius
S | bug 1820211 | python3-openid
S C | bug 1820212 | python-aiosmtpd
+T | bug 1820213 | python-arrow (non fatal build error on dateutil, tests)
+ | bug 1820214 | python-blessed
S+? | bug 1820215 | python-django-extensions (many functions in one package)
S | bug 1820216 | python-django-gravatar2
STC | bug 1820217 | python-falcon (opt: update version before 20.04)
+ | bug 686045 | python-lockfile
+TC | bug 1820220 | python-public (opt: update version before 20.04)
S | bug 1820221 | python-requests-oauthlib
+T | bug 1820223 | python-uritemplate (be a sync, better new upstream)
S | bug 1820224 | python-whoosh
S | bug 1820225 | robot-detection
-M | n/a | ruby-sass (deprecated, use sassc - Debian 924629)
-M | TBD | sassc (Dep will be cut by Debian bug 924961)
-M | TBD | libsass (Dep will be cut by Debian bug 924961)
S | bug 1820226 | twitter-bootstrap3 (asked upstream to move to v4)
? | bug 1820227 | uwsgi (FTBFS: #1820095) (assigned to cyphermox)
+ | bug 1820229 | wcwidth
+ | bug 1597439 | zeromq3
STC | bug 1820233 | zope.component (version update)
STC | bug 1820234 | zope.configuration (version update)
STC | bug 1820236 | zope.event (version update)
STC | bug 1820237 | zope.hookable (version update)
STC | bug 1820238 | zope.i18nmessageid (version update)
STC | bug 1820239 | zope.schema (version update)
List Debian bugs we depend on being resolved as expected before
the dependency tree can completely be MIRed:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924629
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924961
This might sometimes be slightly out of date, to cross check and for history on all of them check git at:
https://git.launchpad.net/~ubuntu-server/+git/mailman3-MIR-party/tree/package-list.txt
---
Past Decisions in regard to this:
mailman is python2, mailman3 is python3, but also it has new dependency stack due to adopting django but also splitting or rewriting a lot of its components.
Q: Do we want bin:mailman3 or bin:mailman3-full in main? (the latter pulls
in src:mailman-suite as well). src:mailman-suite has potentially more
things - django, hyperkitty, ruby-sass, uwsgi...
A: We analyzed this and we will need the full set of dependencies, even
meaning MIRs are needed for all of the above listed (and more).
Q: Before proceeding further with assignment/doing technical work in
driving above MIRs, a product level yes/no answers should probably be
answered for above two questions.
A: Discussed in several sprints now, as uncomfortable as it is we will go
through the mass-MIR processing |
|
| 2019-04-23 07:07:10 |
Christian Ehrhardt |
description |
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for https://lists.canonical.com/mailman3/postorius/lists/
This source builds only docs and mailman3 itself (which provides mailman3-core).
[Rationale]
This is part of the MIR activity for all dependencies of mailman3
The "main" MIR of it is at bug 1775427:
Mailman (2) has only python2 support, but we strive for python3,
therefore Mailman3 which has python3 support should be promoted to main.
This is an evolution of the mailman2 core delivery engine of the system, but I can't guess how much it deviated so we need to recheck security (IMHO)
[Security]
No known CVEs found.
A few old issues can be found against mailman2 and one (but long fixed) for mailman 3
=> https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=mailman
[Quality assurance]
The mailman3 stacks as of now (Disco) installs fine and provides a base
config. But due to the nature of the package that needs further modification
to be of real use.
The package does in error cases ask a debconf-high question, but it is not going to be installed by default - so that is no MIR problem.
There are a few (2) Ubuntu bugs outstanding, but none of them is critical and stopping this MIR request.
There are a few (2) Debian bugs outstanding all seems to "just work" still, but when we main this in 19.10 we should at least evaluate and maybe adress this one:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921445
There are regular upstream releases and Debian packages them and fixes regularly.
No exotic HW involved.
The package ships a test suite, but it is not run at build time for upstream bug #400.
It tests things in a dep8 test thou to provide coverage.
d/watch is set up and ok.
No Lintian warning except fairly recent newer Standards version.
The package does not rely on demoted or obsolete packages.
[UI standards]
Comes with 7 translations in .po files
No End-user applications that needs a standard conformant desktop file.
[Dependencies]
Some dependencies are not in main, but we drive MIR for all related packages
that are not in main at the same time.
Please check the list of bugs from the main Mailman3 MIR in bug 1775427 to get an overview.
[Standards compliance]
The package meets the FHS and Debian Policy standards.
The packaging itself is very straight forward and uses dh_* as much as possible - the d/rules fits on one screen.
[Maintenance]
The Server team will subscribe for the package for maintenance
[Background]
The package description explains the general purpose and context of the package well.
---
References to all the related MIR bug - one per affected package.
Status (simplified version of https://wiki.ubuntu.com/MIRTeam#Process_states)
(nothing) means we have not even prepared the MIR yet
- MIR not needed (e.g. dependency will be dropped)
* all of the template fields for the MIR are complete
! waiting for MIR review
? cpaelzer needs experienced MIR team members to continue
S needs security review to be accepted
+ MIR accepted
x MIR nacked
Extra Flags which team members or on review feedback can be added:
T extra work for the team that should be done before 20.04 (state todo after package)
M extra work for the team before getting MIR to be acceptable (read as asap)
C needed if only promoting mailman3 (core)
H needed if only promoting mailman3 (core) plus Hyperkitty
J no more needed for mailman3-web if we can cut node-less out
FLAGS | MIR-Bug | Package (Notes)
TC
MH
----------------------------------------
S | bug 1820179 | coreapi
+ | bug 1820180 | coreschema
S | bug 1820181 | django-allauth
+ | bug 1820182 | django-filter
S | bug 1820183 | django-guardian
+ | bug 1820185 | django-haystack
S | bug 1820186 | django-mailman3
- | | django-paintstore ((no dep hyperkitty >=1.2.2-1)
+ | bug 1820188 | django-picklefield
+ | bug 1820189 | django-q
S | bug 1820190 | djangorestframework
S C | bug 1820191 | flufl.bounce
+ C | bug 1820192 | flufl.i18n
+ C | bug 1820193 | flufl.lock
M | bug 1820195 | glewlwyd (likely need to break dep to this)
S | bug 1820196 | hyperkitty
+ | bug 1820197 | itypes
- | n/a | jqueryui (no dep hyperkitty >=1.2.2-1)
+ C | bug 1820199 | lazr.config
+TC | bug 1820200 | lazr.delegates (opt: update; suggest dropping nose)
-MJ | bug 1820201 | less.js (Dep will be cut out in Debian bug 924961)
- | n/a | libjs-jquery-colorpicker (no hyperkitty >=1.2.2-1)
S | bug 1820202 | libmatheval
S | bug 1820203 | libpgm
S C | bug 1775427 | mailman3
S | bug 1820204 | mailmanclient
S H | bug 1820205 | mailman-hyperkitty
S | bug 1820206 | mailman-suite
-MJ | bug 1820207 | node-source-map (wait for node-less dep to be cut)
-MJ | bug 1820208 | nodejs (wait for node-less dep to be cut)
S+? | bug 1820209 | norm (check if embedded protolib is an issue)
+ | bug 1820982 | nose
S | bug 1820210 | postorius
S | bug 1820211 | python3-openid
S C | bug 1820212 | python-aiosmtpd
+T | bug 1820213 | python-arrow (non fatal build error on dateutil, tests)
+ | bug 1820214 | python-blessed
S+? | bug 1820215 | python-django-extensions (many functions in one package)
S | bug 1820216 | python-django-gravatar2
STC | bug 1820217 | python-falcon (opt: update version before 20.04)
+ | bug 686045 | python-lockfile
+TC | bug 1820220 | python-public (opt: update version before 20.04)
S | bug 1820221 | python-requests-oauthlib
+T | bug 1820223 | python-uritemplate (be a sync, better new upstream)
S | bug 1820224 | python-whoosh
S | bug 1820225 | robot-detection
-M | n/a | ruby-sass (deprecated, use sassc - Debian 924629)
-M | TBD | sassc (Dep will be cut by Debian bug 924961)
-M | TBD | libsass (Dep will be cut by Debian bug 924961)
S | bug 1820226 | twitter-bootstrap3 (asked upstream to move to v4)
? | bug 1820227 | uwsgi (FTBFS: #1820095) (assigned to cyphermox)
+ | bug 1820229 | wcwidth
+ | bug 1597439 | zeromq3
STC | bug 1820233 | zope.component (version update)
STC | bug 1820234 | zope.configuration (version update)
STC | bug 1820236 | zope.event (version update)
STC | bug 1820237 | zope.hookable (version update)
STC | bug 1820238 | zope.i18nmessageid (version update)
STC | bug 1820239 | zope.schema (version update)
List Debian bugs we depend on being resolved as expected before
the dependency tree can completely be MIRed:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924629
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924961
This might sometimes be slightly out of date, to cross check and for history on all of them check git at:
https://git.launchpad.net/~ubuntu-server/+git/mailman3-MIR-party/tree/package-list.txt
---
Past Decisions in regard to this:
mailman is python2, mailman3 is python3, but also it has new dependency stack due to adopting django but also splitting or rewriting a lot of its components.
Q: Do we want bin:mailman3 or bin:mailman3-full in main? (the latter pulls
in src:mailman-suite as well). src:mailman-suite has potentially more
things - django, hyperkitty, ruby-sass, uwsgi...
A: We analyzed this and we will need the full set of dependencies, even
meaning MIRs are needed for all of the above listed (and more).
Q: Before proceeding further with assignment/doing technical work in
driving above MIRs, a product level yes/no answers should probably be
answered for above two questions.
A: Discussed in several sprints now, as uncomfortable as it is we will go
through the mass-MIR processing |
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for https://lists.canonical.com/mailman3/postorius/lists/
This source builds only docs and mailman3 itself (which provides mailman3-core).
[Rationale]
This is part of the MIR activity for all dependencies of mailman3
The "main" MIR of it is at bug 1775427:
Mailman (2) has only python2 support, but we strive for python3,
therefore Mailman3 which has python3 support should be promoted to main.
This is an evolution of the mailman2 core delivery engine of the system, but I can't guess how much it deviated so we need to recheck security (IMHO)
[Security]
No known CVEs found.
A few old issues can be found against mailman2 and one (but long fixed) for mailman 3
=> https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=mailman
[Quality assurance]
The mailman3 stacks as of now (Disco) installs fine and provides a base
config. But due to the nature of the package that needs further modification
to be of real use.
The package does in error cases ask a debconf-high question, but it is not going to be installed by default - so that is no MIR problem.
There are a few (2) Ubuntu bugs outstanding, but none of them is critical and stopping this MIR request.
There are a few (2) Debian bugs outstanding all seems to "just work" still, but when we main this in 19.10 we should at least evaluate and maybe adress this one:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921445
There are regular upstream releases and Debian packages them and fixes regularly.
No exotic HW involved.
The package ships a test suite, but it is not run at build time for upstream bug #400.
It tests things in a dep8 test thou to provide coverage.
d/watch is set up and ok.
No Lintian warning except fairly recent newer Standards version.
The package does not rely on demoted or obsolete packages.
[UI standards]
Comes with 7 translations in .po files
No End-user applications that needs a standard conformant desktop file.
[Dependencies]
Some dependencies are not in main, but we drive MIR for all related packages
that are not in main at the same time.
Please check the list of bugs from the main Mailman3 MIR in bug 1775427 to get an overview.
[Standards compliance]
The package meets the FHS and Debian Policy standards.
The packaging itself is very straight forward and uses dh_* as much as possible - the d/rules fits on one screen.
[Maintenance]
The Server team will subscribe for the package for maintenance
[Background]
The package description explains the general purpose and context of the package well.
---
References to all the related MIR bug - one per affected package.
Status (simplified version of https://wiki.ubuntu.com/MIRTeam#Process_states)
(nothing) means we have not even prepared the MIR yet
- MIR not needed (e.g. dependency will be dropped)
* all of the template fields for the MIR are complete
! waiting for MIR review
? cpaelzer needs experienced MIR team members to continue
S needs security review to be accepted
+ MIR accepted
x MIR nacked
Extra Flags which team members or on review feedback can be added:
T extra work for the team that should be done before 20.04 (state todo after package)
M extra work for the team before getting MIR to be acceptable (read as asap)
C needed if only promoting mailman3 (core)
H needed if only promoting mailman3 (core) plus Hyperkitty
J no more needed for mailman3-web if we can cut node-less out
FLAGS | MIR-Bug | Package (Notes)
TC
MH
----------------------------------------
S | bug 1820179 | coreapi
+ | bug 1820180 | coreschema
S | bug 1820181 | django-allauth
+ | bug 1820182 | django-filter
S | bug 1820183 | django-guardian
+ | bug 1820185 | django-haystack
S | bug 1820186 | django-mailman3
- | | django-paintstore ((no dep hyperkitty >=1.2.2-1)
+ | bug 1820188 | django-picklefield
+ | bug 1820189 | django-q
S | bug 1820190 | djangorestframework
S C | bug 1820191 | flufl.bounce
+ C | bug 1820192 | flufl.i18n
+ C | bug 1820193 | flufl.lock
M | bug 1820195 | glewlwyd (likely need to break dep to this)
S | bug 1820196 | hyperkitty
+ | bug 1820197 | itypes
- | n/a | jqueryui (no dep hyperkitty >=1.2.2-1)
+ C | bug 1820199 | lazr.config
+TC | bug 1820200 | lazr.delegates (opt: update; suggest dropping nose)
-MJ | bug 1820201 | less.js (Dep will be cut out in Debian bug 924961)
- | n/a | libjs-jquery-colorpicker (no hyperkitty >=1.2.2-1)
S | bug 1820202 | libmatheval
S | bug 1820203 | libpgm
S C | bug 1775427 | mailman3
S | bug 1820204 | mailmanclient
S H | bug 1820205 | mailman-hyperkitty
S | bug 1820206 | mailman-suite
-MJ | bug 1820207 | node-source-map (wait for node-less dep to be cut)
-MJ | bug 1820208 | nodejs (wait for node-less dep to be cut)
S+? | bug 1820209 | norm (check if embedded protolib is an issue)
+ | bug 1820982 | nose
S | bug 1820210 | postorius
S | bug 1820211 | python3-openid
S C | bug 1820212 | python-aiosmtpd
+T | bug 1820213 | python-arrow (non fatal build error on dateutil, tests)
+ | bug 1820214 | python-blessed
S+? | bug 1820215 | python-django-extensions (many functions in one package)
S | bug 1820216 | python-django-gravatar2
STC | bug 1820217 | python-falcon (opt: update version before 20.04)
+ | bug 686045 | python-lockfile
+TC | bug 1820220 | python-public (opt: update version before 20.04)
S | bug 1820221 | python-requests-oauthlib
+T | bug 1820223 | python-uritemplate (be a sync, better new upstream)
S | bug 1820224 | python-whoosh
+ | bug 1820225 | robot-detection
-M | n/a | ruby-sass (deprecated, use sassc - Debian 924629)
-M | TBD | sassc (Dep will be cut by Debian bug 924961)
-M | TBD | libsass (Dep will be cut by Debian bug 924961)
S | bug 1820226 | twitter-bootstrap3 (asked upstream to move to v4)
? | bug 1820227 | uwsgi (FTBFS: #1820095) (assigned to cyphermox)
+ | bug 1820229 | wcwidth
+ | bug 1597439 | zeromq3
STC | bug 1820233 | zope.component (version update)
STC | bug 1820234 | zope.configuration (version update)
STC | bug 1820236 | zope.event (version update)
STC | bug 1820237 | zope.hookable (version update)
STC | bug 1820238 | zope.i18nmessageid (version update)
STC | bug 1820239 | zope.schema (version update)
List Debian bugs we depend on being resolved as expected before
the dependency tree can completely be MIRed:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924629
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924961
This might sometimes be slightly out of date, to cross check and for history on all of them check git at:
https://git.launchpad.net/~ubuntu-server/+git/mailman3-MIR-party/tree/package-list.txt
---
Past Decisions in regard to this:
mailman is python2, mailman3 is python3, but also it has new dependency stack due to adopting django but also splitting or rewriting a lot of its components.
Q: Do we want bin:mailman3 or bin:mailman3-full in main? (the latter pulls
in src:mailman-suite as well). src:mailman-suite has potentially more
things - django, hyperkitty, ruby-sass, uwsgi...
A: We analyzed this and we will need the full set of dependencies, even
meaning MIRs are needed for all of the above listed (and more).
Q: Before proceeding further with assignment/doing technical work in
driving above MIRs, a product level yes/no answers should probably be
answered for above two questions.
A: Discussed in several sprints now, as uncomfortable as it is we will go
through the mass-MIR processing |
|
| 2019-05-02 14:56:50 |
Dimitri John Ledkov |
tags |
|
py2-demotion py2-removal |
|
| 2019-05-02 14:56:56 |
Dimitri John Ledkov |
mailman3 (Ubuntu): importance |
Undecided |
Critical |
|
| 2019-05-02 14:57:02 |
Dimitri John Ledkov |
mailman3 (Ubuntu): milestone |
|
ubuntu-19.10 |
|
| 2019-05-08 07:37:07 |
Christian Ehrhardt |
description |
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for https://lists.canonical.com/mailman3/postorius/lists/
This source builds only docs and mailman3 itself (which provides mailman3-core).
[Rationale]
This is part of the MIR activity for all dependencies of mailman3
The "main" MIR of it is at bug 1775427:
Mailman (2) has only python2 support, but we strive for python3,
therefore Mailman3 which has python3 support should be promoted to main.
This is an evolution of the mailman2 core delivery engine of the system, but I can't guess how much it deviated so we need to recheck security (IMHO)
[Security]
No known CVEs found.
A few old issues can be found against mailman2 and one (but long fixed) for mailman 3
=> https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=mailman
[Quality assurance]
The mailman3 stacks as of now (Disco) installs fine and provides a base
config. But due to the nature of the package that needs further modification
to be of real use.
The package does in error cases ask a debconf-high question, but it is not going to be installed by default - so that is no MIR problem.
There are a few (2) Ubuntu bugs outstanding, but none of them is critical and stopping this MIR request.
There are a few (2) Debian bugs outstanding all seems to "just work" still, but when we main this in 19.10 we should at least evaluate and maybe adress this one:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921445
There are regular upstream releases and Debian packages them and fixes regularly.
No exotic HW involved.
The package ships a test suite, but it is not run at build time for upstream bug #400.
It tests things in a dep8 test thou to provide coverage.
d/watch is set up and ok.
No Lintian warning except fairly recent newer Standards version.
The package does not rely on demoted or obsolete packages.
[UI standards]
Comes with 7 translations in .po files
No End-user applications that needs a standard conformant desktop file.
[Dependencies]
Some dependencies are not in main, but we drive MIR for all related packages
that are not in main at the same time.
Please check the list of bugs from the main Mailman3 MIR in bug 1775427 to get an overview.
[Standards compliance]
The package meets the FHS and Debian Policy standards.
The packaging itself is very straight forward and uses dh_* as much as possible - the d/rules fits on one screen.
[Maintenance]
The Server team will subscribe for the package for maintenance
[Background]
The package description explains the general purpose and context of the package well.
---
References to all the related MIR bug - one per affected package.
Status (simplified version of https://wiki.ubuntu.com/MIRTeam#Process_states)
(nothing) means we have not even prepared the MIR yet
- MIR not needed (e.g. dependency will be dropped)
* all of the template fields for the MIR are complete
! waiting for MIR review
? cpaelzer needs experienced MIR team members to continue
S needs security review to be accepted
+ MIR accepted
x MIR nacked
Extra Flags which team members or on review feedback can be added:
T extra work for the team that should be done before 20.04 (state todo after package)
M extra work for the team before getting MIR to be acceptable (read as asap)
C needed if only promoting mailman3 (core)
H needed if only promoting mailman3 (core) plus Hyperkitty
J no more needed for mailman3-web if we can cut node-less out
FLAGS | MIR-Bug | Package (Notes)
TC
MH
----------------------------------------
S | bug 1820179 | coreapi
+ | bug 1820180 | coreschema
S | bug 1820181 | django-allauth
+ | bug 1820182 | django-filter
S | bug 1820183 | django-guardian
+ | bug 1820185 | django-haystack
S | bug 1820186 | django-mailman3
- | | django-paintstore ((no dep hyperkitty >=1.2.2-1)
+ | bug 1820188 | django-picklefield
+ | bug 1820189 | django-q
S | bug 1820190 | djangorestframework
S C | bug 1820191 | flufl.bounce
+ C | bug 1820192 | flufl.i18n
+ C | bug 1820193 | flufl.lock
M | bug 1820195 | glewlwyd (likely need to break dep to this)
S | bug 1820196 | hyperkitty
+ | bug 1820197 | itypes
- | n/a | jqueryui (no dep hyperkitty >=1.2.2-1)
+ C | bug 1820199 | lazr.config
+TC | bug 1820200 | lazr.delegates (opt: update; suggest dropping nose)
-MJ | bug 1820201 | less.js (Dep will be cut out in Debian bug 924961)
- | n/a | libjs-jquery-colorpicker (no hyperkitty >=1.2.2-1)
S | bug 1820202 | libmatheval
S | bug 1820203 | libpgm
S C | bug 1775427 | mailman3
S | bug 1820204 | mailmanclient
S H | bug 1820205 | mailman-hyperkitty
S | bug 1820206 | mailman-suite
-MJ | bug 1820207 | node-source-map (wait for node-less dep to be cut)
-MJ | bug 1820208 | nodejs (wait for node-less dep to be cut)
S+? | bug 1820209 | norm (check if embedded protolib is an issue)
+ | bug 1820982 | nose
S | bug 1820210 | postorius
S | bug 1820211 | python3-openid
S C | bug 1820212 | python-aiosmtpd
+T | bug 1820213 | python-arrow (non fatal build error on dateutil, tests)
+ | bug 1820214 | python-blessed
S+? | bug 1820215 | python-django-extensions (many functions in one package)
S | bug 1820216 | python-django-gravatar2
STC | bug 1820217 | python-falcon (opt: update version before 20.04)
+ | bug 686045 | python-lockfile
+TC | bug 1820220 | python-public (opt: update version before 20.04)
S | bug 1820221 | python-requests-oauthlib
+T | bug 1820223 | python-uritemplate (be a sync, better new upstream)
S | bug 1820224 | python-whoosh
+ | bug 1820225 | robot-detection
-M | n/a | ruby-sass (deprecated, use sassc - Debian 924629)
-M | TBD | sassc (Dep will be cut by Debian bug 924961)
-M | TBD | libsass (Dep will be cut by Debian bug 924961)
S | bug 1820226 | twitter-bootstrap3 (asked upstream to move to v4)
? | bug 1820227 | uwsgi (FTBFS: #1820095) (assigned to cyphermox)
+ | bug 1820229 | wcwidth
+ | bug 1597439 | zeromq3
STC | bug 1820233 | zope.component (version update)
STC | bug 1820234 | zope.configuration (version update)
STC | bug 1820236 | zope.event (version update)
STC | bug 1820237 | zope.hookable (version update)
STC | bug 1820238 | zope.i18nmessageid (version update)
STC | bug 1820239 | zope.schema (version update)
List Debian bugs we depend on being resolved as expected before
the dependency tree can completely be MIRed:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924629
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924961
This might sometimes be slightly out of date, to cross check and for history on all of them check git at:
https://git.launchpad.net/~ubuntu-server/+git/mailman3-MIR-party/tree/package-list.txt
---
Past Decisions in regard to this:
mailman is python2, mailman3 is python3, but also it has new dependency stack due to adopting django but also splitting or rewriting a lot of its components.
Q: Do we want bin:mailman3 or bin:mailman3-full in main? (the latter pulls
in src:mailman-suite as well). src:mailman-suite has potentially more
things - django, hyperkitty, ruby-sass, uwsgi...
A: We analyzed this and we will need the full set of dependencies, even
meaning MIRs are needed for all of the above listed (and more).
Q: Before proceeding further with assignment/doing technical work in
driving above MIRs, a product level yes/no answers should probably be
answered for above two questions.
A: Discussed in several sprints now, as uncomfortable as it is we will go
through the mass-MIR processing |
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for https://lists.canonical.com/mailman3/postorius/lists/
This source builds only docs and mailman3 itself (which provides mailman3-core).
[Rationale]
This is part of the MIR activity for all dependencies of mailman3
The "main" MIR of it is at bug 1775427:
Mailman (2) has only python2 support, but we strive for python3,
therefore Mailman3 which has python3 support should be promoted to main.
This is an evolution of the mailman2 core delivery engine of the system, but I can't guess how much it deviated so we need to recheck security (IMHO)
[Security]
No known CVEs found.
A few old issues can be found against mailman2 and one (but long fixed) for mailman 3
=> https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=mailman
[Quality assurance]
The mailman3 stacks as of now (Disco) installs fine and provides a base
config. But due to the nature of the package that needs further modification
to be of real use.
The package does in error cases ask a debconf-high question, but it is not going to be installed by default - so that is no MIR problem.
There are a few (2) Ubuntu bugs outstanding, but none of them is critical and stopping this MIR request.
There are a few (2) Debian bugs outstanding all seems to "just work" still, but when we main this in 19.10 we should at least evaluate and maybe adress this one:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921445
There are regular upstream releases and Debian packages them and fixes regularly.
No exotic HW involved.
The package ships a test suite, but it is not run at build time for upstream bug #400.
It tests things in a dep8 test thou to provide coverage.
d/watch is set up and ok.
No Lintian warning except fairly recent newer Standards version.
The package does not rely on demoted or obsolete packages.
[UI standards]
Comes with 7 translations in .po files
No End-user applications that needs a standard conformant desktop file.
[Dependencies]
Some dependencies are not in main, but we drive MIR for all related packages
that are not in main at the same time.
Please check the list of bugs from the main Mailman3 MIR in bug 1775427 to get an overview.
[Standards compliance]
The package meets the FHS and Debian Policy standards.
The packaging itself is very straight forward and uses dh_* as much as possible - the d/rules fits on one screen.
[Maintenance]
The Server team will subscribe for the package for maintenance
[Background]
The package description explains the general purpose and context of the package well.
---
References to all the related MIR bug - one per affected package.
Status (simplified version of https://wiki.ubuntu.com/MIRTeam#Process_states)
(nothing) means we have not even prepared the MIR yet
- MIR not needed (e.g. dependency will be dropped)
* all of the template fields for the MIR are complete
! waiting for MIR review
? cpaelzer needs experienced MIR team members to continue
S needs security review to be accepted
+ MIR accepted
x MIR nacked
Extra Flags which team members or on review feedback can be added:
T extra work for the team that should be done before 20.04 (state todo after package)
M extra work for the team before getting MIR to be acceptable (read as asap)
C needed if only promoting mailman3 (core)
H needed if only promoting mailman3 (core) plus Hyperkitty
J no more needed for mailman3-web if we can cut node-less out
FLAGS | MIR-Bug | Package (Notes)
TC
MH
----------------------------------------
+ | bug 1820179 | coreapi
+ | bug 1820180 | coreschema
S | bug 1820181 | django-allauth
+ | bug 1820182 | django-filter
S | bug 1820183 | django-guardian
+ | bug 1820185 | django-haystack
S | bug 1820186 | django-mailman3
- | | django-paintstore ((no dep hyperkitty >=1.2.2-1)
+ | bug 1820188 | django-picklefield
+ | bug 1820189 | django-q
S | bug 1820190 | djangorestframework
S C | bug 1820191 | flufl.bounce
+ C | bug 1820192 | flufl.i18n
+ C | bug 1820193 | flufl.lock
M | bug 1820195 | glewlwyd (need to break dep [font corruption] or break packaging)
S | bug 1820196 | hyperkitty (avoid type error https://bugs.launchpad.net/ubuntu/+source/robot-detection/+bug/1820225/comments/2)
+ | bug 1820197 | itypes
- | n/a | jqueryui (no dep hyperkitty >=1.2.2-1)
+ C | bug 1820199 | lazr.config
+ C | bug 1820200 | lazr.delegates
-MJ | bug 1820201 | less.js (Dep will be cut out in Debian bug 924961)
- | n/a | libjs-jquery-colorpicker (no hyperkitty >=1.2.2-1)
S | bug 1820202 | libmatheval
S | bug 1820203 | libpgm
S C | bug 1775427 | mailman3
S | bug 1820204 | mailmanclient
S H | bug 1820205 | mailman-hyperkitty
+ | bug 1820206 | mailman-suite
-MJ | bug 1820207 | node-source-map (wait for node-less dep to be cut)
-MJ | bug 1820208 | nodejs (wait for node-less dep to be cut)
S+? | bug 1820209 | norm (check if embedded protolib is an issue)
+ | bug 1820982 | nose
S | bug 1820210 | postorius
M | bug 1820211 | python3-openid (change to python-openid)
S C | bug 1820212 | python-aiosmtpd
+T | bug 1820213 | python-arrow (non fatal build error on dateutil, tests)
+ | bug 1820214 | python-blessed
S+? | bug 1820215 | python-django-extensions (many functions in one package)
+ | bug 1820216 | python-django-gravatar2
STC | bug 1820217 | python-falcon (opt: update version before 20.04)
+ | bug 686045 | python-lockfile
+TC | bug 1820220 | python-public (opt: update version before 20.04)
+ | bug 1820221 | python-requests-oauthlib
+T | bug 1820223 | python-uritemplate (be a sync, better new upstream)
S | bug 1820224 | python-whoosh
+ | bug 1820225 | robot-detection
-M | n/a | ruby-sass (deprecated, use sassc - Debian 924629)
-M | TBD | sassc (Dep will be cut by Debian bug 924961)
-M | TBD | libsass (Dep will be cut by Debian bug 924961)
S | bug 1820226 | twitter-bootstrap3 (asked upstream to move to v4)
? | bug 1820227 | uwsgi (FTBFS: #1820095) (assigned to cyphermox)
+ | bug 1820229 | wcwidth
+ | bug 1597439 | zeromq3
STC | bug 1820233 | zope.component (version update)
STC | bug 1820234 | zope.configuration (version update)
STC | bug 1820236 | zope.event (version update)
STC | bug 1820237 | zope.hookable (version update)
STC | bug 1820238 | zope.i18nmessageid (version update)
STC | bug 1820239 | zope.schema (version update)
List Debian bugs we depend on being resolved as expected before
the dependency tree can completely be MIRed:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924629
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924961
This might sometimes be slightly out of date, to cross check and for history on all of them check git at:
https://git.launchpad.net/~ubuntu-server/+git/mailman3-MIR-party/tree/package-list.txt
---
Past Decisions in regard to this:
mailman is python2, mailman3 is python3, but also it has new dependency stack due to adopting django but also splitting or rewriting a lot of its components.
Q: Do we want bin:mailman3 or bin:mailman3-full in main? (the latter pulls
in src:mailman-suite as well). src:mailman-suite has potentially more
things - django, hyperkitty, ruby-sass, uwsgi...
A: We analyzed this and we will need the full set of dependencies, even
meaning MIRs are needed for all of the above listed (and more).
Q: Before proceeding further with assignment/doing technical work in
driving above MIRs, a product level yes/no answers should probably be
answered for above two questions.
A: Discussed in several sprints now, as uncomfortable as it is we will go
through the mass-MIR processing |
|
| 2019-05-13 06:39:38 |
Christian Ehrhardt |
description |
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for https://lists.canonical.com/mailman3/postorius/lists/
This source builds only docs and mailman3 itself (which provides mailman3-core).
[Rationale]
This is part of the MIR activity for all dependencies of mailman3
The "main" MIR of it is at bug 1775427:
Mailman (2) has only python2 support, but we strive for python3,
therefore Mailman3 which has python3 support should be promoted to main.
This is an evolution of the mailman2 core delivery engine of the system, but I can't guess how much it deviated so we need to recheck security (IMHO)
[Security]
No known CVEs found.
A few old issues can be found against mailman2 and one (but long fixed) for mailman 3
=> https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=mailman
[Quality assurance]
The mailman3 stacks as of now (Disco) installs fine and provides a base
config. But due to the nature of the package that needs further modification
to be of real use.
The package does in error cases ask a debconf-high question, but it is not going to be installed by default - so that is no MIR problem.
There are a few (2) Ubuntu bugs outstanding, but none of them is critical and stopping this MIR request.
There are a few (2) Debian bugs outstanding all seems to "just work" still, but when we main this in 19.10 we should at least evaluate and maybe adress this one:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921445
There are regular upstream releases and Debian packages them and fixes regularly.
No exotic HW involved.
The package ships a test suite, but it is not run at build time for upstream bug #400.
It tests things in a dep8 test thou to provide coverage.
d/watch is set up and ok.
No Lintian warning except fairly recent newer Standards version.
The package does not rely on demoted or obsolete packages.
[UI standards]
Comes with 7 translations in .po files
No End-user applications that needs a standard conformant desktop file.
[Dependencies]
Some dependencies are not in main, but we drive MIR for all related packages
that are not in main at the same time.
Please check the list of bugs from the main Mailman3 MIR in bug 1775427 to get an overview.
[Standards compliance]
The package meets the FHS and Debian Policy standards.
The packaging itself is very straight forward and uses dh_* as much as possible - the d/rules fits on one screen.
[Maintenance]
The Server team will subscribe for the package for maintenance
[Background]
The package description explains the general purpose and context of the package well.
---
References to all the related MIR bug - one per affected package.
Status (simplified version of https://wiki.ubuntu.com/MIRTeam#Process_states)
(nothing) means we have not even prepared the MIR yet
- MIR not needed (e.g. dependency will be dropped)
* all of the template fields for the MIR are complete
! waiting for MIR review
? cpaelzer needs experienced MIR team members to continue
S needs security review to be accepted
+ MIR accepted
x MIR nacked
Extra Flags which team members or on review feedback can be added:
T extra work for the team that should be done before 20.04 (state todo after package)
M extra work for the team before getting MIR to be acceptable (read as asap)
C needed if only promoting mailman3 (core)
H needed if only promoting mailman3 (core) plus Hyperkitty
J no more needed for mailman3-web if we can cut node-less out
FLAGS | MIR-Bug | Package (Notes)
TC
MH
----------------------------------------
+ | bug 1820179 | coreapi
+ | bug 1820180 | coreschema
S | bug 1820181 | django-allauth
+ | bug 1820182 | django-filter
S | bug 1820183 | django-guardian
+ | bug 1820185 | django-haystack
S | bug 1820186 | django-mailman3
- | | django-paintstore ((no dep hyperkitty >=1.2.2-1)
+ | bug 1820188 | django-picklefield
+ | bug 1820189 | django-q
S | bug 1820190 | djangorestframework
S C | bug 1820191 | flufl.bounce
+ C | bug 1820192 | flufl.i18n
+ C | bug 1820193 | flufl.lock
M | bug 1820195 | glewlwyd (need to break dep [font corruption] or break packaging)
S | bug 1820196 | hyperkitty (avoid type error https://bugs.launchpad.net/ubuntu/+source/robot-detection/+bug/1820225/comments/2)
+ | bug 1820197 | itypes
- | n/a | jqueryui (no dep hyperkitty >=1.2.2-1)
+ C | bug 1820199 | lazr.config
+ C | bug 1820200 | lazr.delegates
-MJ | bug 1820201 | less.js (Dep will be cut out in Debian bug 924961)
- | n/a | libjs-jquery-colorpicker (no hyperkitty >=1.2.2-1)
S | bug 1820202 | libmatheval
S | bug 1820203 | libpgm
S C | bug 1775427 | mailman3
S | bug 1820204 | mailmanclient
S H | bug 1820205 | mailman-hyperkitty
+ | bug 1820206 | mailman-suite
-MJ | bug 1820207 | node-source-map (wait for node-less dep to be cut)
-MJ | bug 1820208 | nodejs (wait for node-less dep to be cut)
S+? | bug 1820209 | norm (check if embedded protolib is an issue)
+ | bug 1820982 | nose
S | bug 1820210 | postorius
M | bug 1820211 | python3-openid (change to python-openid)
S C | bug 1820212 | python-aiosmtpd
+T | bug 1820213 | python-arrow (non fatal build error on dateutil, tests)
+ | bug 1820214 | python-blessed
S+? | bug 1820215 | python-django-extensions (many functions in one package)
+ | bug 1820216 | python-django-gravatar2
STC | bug 1820217 | python-falcon (opt: update version before 20.04)
+ | bug 686045 | python-lockfile
+TC | bug 1820220 | python-public (opt: update version before 20.04)
+ | bug 1820221 | python-requests-oauthlib
+T | bug 1820223 | python-uritemplate (be a sync, better new upstream)
S | bug 1820224 | python-whoosh
+ | bug 1820225 | robot-detection
-M | n/a | ruby-sass (deprecated, use sassc - Debian 924629)
-M | TBD | sassc (Dep will be cut by Debian bug 924961)
-M | TBD | libsass (Dep will be cut by Debian bug 924961)
S | bug 1820226 | twitter-bootstrap3 (asked upstream to move to v4)
? | bug 1820227 | uwsgi (FTBFS: #1820095) (assigned to cyphermox)
+ | bug 1820229 | wcwidth
+ | bug 1597439 | zeromq3
STC | bug 1820233 | zope.component (version update)
STC | bug 1820234 | zope.configuration (version update)
STC | bug 1820236 | zope.event (version update)
STC | bug 1820237 | zope.hookable (version update)
STC | bug 1820238 | zope.i18nmessageid (version update)
STC | bug 1820239 | zope.schema (version update)
List Debian bugs we depend on being resolved as expected before
the dependency tree can completely be MIRed:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924629
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924961
This might sometimes be slightly out of date, to cross check and for history on all of them check git at:
https://git.launchpad.net/~ubuntu-server/+git/mailman3-MIR-party/tree/package-list.txt
---
Past Decisions in regard to this:
mailman is python2, mailman3 is python3, but also it has new dependency stack due to adopting django but also splitting or rewriting a lot of its components.
Q: Do we want bin:mailman3 or bin:mailman3-full in main? (the latter pulls
in src:mailman-suite as well). src:mailman-suite has potentially more
things - django, hyperkitty, ruby-sass, uwsgi...
A: We analyzed this and we will need the full set of dependencies, even
meaning MIRs are needed for all of the above listed (and more).
Q: Before proceeding further with assignment/doing technical work in
driving above MIRs, a product level yes/no answers should probably be
answered for above two questions.
A: Discussed in several sprints now, as uncomfortable as it is we will go
through the mass-MIR processing |
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for https://lists.canonical.com/mailman3/postorius/lists/
This source builds only docs and mailman3 itself (which provides mailman3-core).
[Rationale]
This is part of the MIR activity for all dependencies of mailman3
The "main" MIR of it is at bug 1775427:
Mailman (2) has only python2 support, but we strive for python3,
therefore Mailman3 which has python3 support should be promoted to main.
This is an evolution of the mailman2 core delivery engine of the system, but I can't guess how much it deviated so we need to recheck security (IMHO)
[Security]
No known CVEs found.
A few old issues can be found against mailman2 and one (but long fixed) for mailman 3
=> https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=mailman
[Quality assurance]
The mailman3 stacks as of now (Disco) installs fine and provides a base
config. But due to the nature of the package that needs further modification
to be of real use.
The package does in error cases ask a debconf-high question, but it is not going to be installed by default - so that is no MIR problem.
There are a few (2) Ubuntu bugs outstanding, but none of them is critical and stopping this MIR request.
There are a few (2) Debian bugs outstanding all seems to "just work" still, but when we main this in 19.10 we should at least evaluate and maybe adress this one:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921445
There are regular upstream releases and Debian packages them and fixes regularly.
No exotic HW involved.
The package ships a test suite, but it is not run at build time for upstream bug #400.
It tests things in a dep8 test thou to provide coverage.
d/watch is set up and ok.
No Lintian warning except fairly recent newer Standards version.
The package does not rely on demoted or obsolete packages.
[UI standards]
Comes with 7 translations in .po files
No End-user applications that needs a standard conformant desktop file.
[Dependencies]
Some dependencies are not in main, but we drive MIR for all related packages
that are not in main at the same time.
Please check the list of bugs from the main Mailman3 MIR in bug 1775427 to get an overview.
[Standards compliance]
The package meets the FHS and Debian Policy standards.
The packaging itself is very straight forward and uses dh_* as much as possible - the d/rules fits on one screen.
[Maintenance]
The Server team will subscribe for the package for maintenance
[Background]
The package description explains the general purpose and context of the package well.
---
References to all the related MIR bug - one per affected package.
Status (simplified version of https://wiki.ubuntu.com/MIRTeam#Process_states)
(nothing) means we have not even prepared the MIR yet
- MIR not needed (e.g. dependency will be dropped)
* all of the template fields for the MIR are complete
! waiting for MIR review
? cpaelzer needs experienced MIR team members to continue
S needs security review to be accepted
+ MIR accepted
x MIR nacked
Extra Flags which team members or on review feedback can be added:
T extra work for the team that should be done before 20.04 (state todo after package)
M extra work for the team before getting MIR to be acceptable (read as asap)
C needed if only promoting mailman3 (core)
H needed if only promoting mailman3 (core) plus Hyperkitty
J no more needed for mailman3-web if we can cut node-less out
FLAGS | MIR-Bug | Package (Notes)
TC
MH
----------------------------------------
+ | bug 1820179 | coreapi
+ | bug 1820180 | coreschema
S | bug 1820181 | django-allauth
+ | bug 1820182 | django-filter
S | bug 1820183 | django-guardian
+ | bug 1820185 | django-haystack
S | bug 1820186 | django-mailman3
- | | django-paintstore ((no dep hyperkitty >=1.2.2-1)
+ | bug 1820188 | django-picklefield
+ | bug 1820189 | django-q
S | bug 1820190 | djangorestframework
S C | bug 1820191 | flufl.bounce
+ C | bug 1820192 | flufl.i18n
+ C | bug 1820193 | flufl.lock
M | bug 1820195 | glewlwyd (need to break dep [font corruption] or break packaging)
S | bug 1820196 | hyperkitty (avoid type error https://bugs.launchpad.net/ubuntu/+source/robot-detection/+bug/1820225/comments/2)
+ | bug 1820197 | itypes
- | n/a | jqueryui (no dep hyperkitty >=1.2.2-1)
+ C | bug 1820199 | lazr.config
+ C | bug 1820200 | lazr.delegates
-MJ | bug 1820201 | less.js (Dep will be cut out in Debian bug 924961)
- | n/a | libjs-jquery-colorpicker (no hyperkitty >=1.2.2-1)
S | bug 1820202 | libmatheval
S | bug 1820203 | libpgm
S C | bug 1775427 | mailman3
S | bug 1820204 | mailmanclient
S H | bug 1820205 | mailman-hyperkitty
+ | bug 1820206 | mailman-suite
-MJ | bug 1820207 | node-source-map (wait for node-less dep to be cut)
-MJ | bug 1820208 | nodejs (wait for node-less dep to be cut)
S+? | bug 1820209 | norm (check if embedded protolib is an issue)
+ | bug 1820982 | nose
S | bug 1820210 | postorius
M | bug 1820211 | python3-openid (change to python-openid)
M C | bug 1820212 | python-aiosmtpd (fix setuid, main loop and user nobody usage)
+T | bug 1820213 | python-arrow (non fatal build error on dateutil, tests)
+ | bug 1820214 | python-blessed
S+? | bug 1820215 | python-django-extensions (many functions in one package)
+ | bug 1820216 | python-django-gravatar2
STC | bug 1820217 | python-falcon (opt: update version before 20.04)
+ | bug 686045 | python-lockfile
+TC | bug 1820220 | python-public (opt: update version before 20.04)
+ | bug 1820221 | python-requests-oauthlib
+T | bug 1820223 | python-uritemplate (be a sync, better new upstream)
S | bug 1820224 | python-whoosh
+ | bug 1820225 | robot-detection
-M | n/a | ruby-sass (deprecated, use sassc - Debian 924629)
-M | TBD | sassc (Dep will be cut by Debian bug 924961)
-M | TBD | libsass (Dep will be cut by Debian bug 924961)
S | bug 1820226 | twitter-bootstrap3 (asked upstream to move to v4)
? | bug 1820227 | uwsgi (FTBFS: #1820095) (assigned to cyphermox)
+ | bug 1820229 | wcwidth
+ | bug 1597439 | zeromq3
STC | bug 1820233 | zope.component (version update)
STC | bug 1820234 | zope.configuration (version update)
STC | bug 1820236 | zope.event (version update)
STC | bug 1820237 | zope.hookable (version update)
STC | bug 1820238 | zope.i18nmessageid (version update)
STC | bug 1820239 | zope.schema (version update)
List Debian bugs we depend on being resolved as expected before
the dependency tree can completely be MIRed:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924629
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924961
This might sometimes be slightly out of date, to cross check and for history on all of them check git at:
https://git.launchpad.net/~ubuntu-server/+git/mailman3-MIR-party/tree/package-list.txt
---
Past Decisions in regard to this:
mailman is python2, mailman3 is python3, but also it has new dependency stack due to adopting django but also splitting or rewriting a lot of its components.
Q: Do we want bin:mailman3 or bin:mailman3-full in main? (the latter pulls
in src:mailman-suite as well). src:mailman-suite has potentially more
things - django, hyperkitty, ruby-sass, uwsgi...
A: We analyzed this and we will need the full set of dependencies, even
meaning MIRs are needed for all of the above listed (and more).
Q: Before proceeding further with assignment/doing technical work in
driving above MIRs, a product level yes/no answers should probably be
answered for above two questions.
A: Discussed in several sprints now, as uncomfortable as it is we will go
through the mass-MIR processing |
|
| 2019-06-27 05:34:04 |
Christian Ehrhardt |
description |
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for https://lists.canonical.com/mailman3/postorius/lists/
This source builds only docs and mailman3 itself (which provides mailman3-core).
[Rationale]
This is part of the MIR activity for all dependencies of mailman3
The "main" MIR of it is at bug 1775427:
Mailman (2) has only python2 support, but we strive for python3,
therefore Mailman3 which has python3 support should be promoted to main.
This is an evolution of the mailman2 core delivery engine of the system, but I can't guess how much it deviated so we need to recheck security (IMHO)
[Security]
No known CVEs found.
A few old issues can be found against mailman2 and one (but long fixed) for mailman 3
=> https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=mailman
[Quality assurance]
The mailman3 stacks as of now (Disco) installs fine and provides a base
config. But due to the nature of the package that needs further modification
to be of real use.
The package does in error cases ask a debconf-high question, but it is not going to be installed by default - so that is no MIR problem.
There are a few (2) Ubuntu bugs outstanding, but none of them is critical and stopping this MIR request.
There are a few (2) Debian bugs outstanding all seems to "just work" still, but when we main this in 19.10 we should at least evaluate and maybe adress this one:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921445
There are regular upstream releases and Debian packages them and fixes regularly.
No exotic HW involved.
The package ships a test suite, but it is not run at build time for upstream bug #400.
It tests things in a dep8 test thou to provide coverage.
d/watch is set up and ok.
No Lintian warning except fairly recent newer Standards version.
The package does not rely on demoted or obsolete packages.
[UI standards]
Comes with 7 translations in .po files
No End-user applications that needs a standard conformant desktop file.
[Dependencies]
Some dependencies are not in main, but we drive MIR for all related packages
that are not in main at the same time.
Please check the list of bugs from the main Mailman3 MIR in bug 1775427 to get an overview.
[Standards compliance]
The package meets the FHS and Debian Policy standards.
The packaging itself is very straight forward and uses dh_* as much as possible - the d/rules fits on one screen.
[Maintenance]
The Server team will subscribe for the package for maintenance
[Background]
The package description explains the general purpose and context of the package well.
---
References to all the related MIR bug - one per affected package.
Status (simplified version of https://wiki.ubuntu.com/MIRTeam#Process_states)
(nothing) means we have not even prepared the MIR yet
- MIR not needed (e.g. dependency will be dropped)
* all of the template fields for the MIR are complete
! waiting for MIR review
? cpaelzer needs experienced MIR team members to continue
S needs security review to be accepted
+ MIR accepted
x MIR nacked
Extra Flags which team members or on review feedback can be added:
T extra work for the team that should be done before 20.04 (state todo after package)
M extra work for the team before getting MIR to be acceptable (read as asap)
C needed if only promoting mailman3 (core)
H needed if only promoting mailman3 (core) plus Hyperkitty
J no more needed for mailman3-web if we can cut node-less out
FLAGS | MIR-Bug | Package (Notes)
TC
MH
----------------------------------------
+ | bug 1820179 | coreapi
+ | bug 1820180 | coreschema
S | bug 1820181 | django-allauth
+ | bug 1820182 | django-filter
S | bug 1820183 | django-guardian
+ | bug 1820185 | django-haystack
S | bug 1820186 | django-mailman3
- | | django-paintstore ((no dep hyperkitty >=1.2.2-1)
+ | bug 1820188 | django-picklefield
+ | bug 1820189 | django-q
S | bug 1820190 | djangorestframework
S C | bug 1820191 | flufl.bounce
+ C | bug 1820192 | flufl.i18n
+ C | bug 1820193 | flufl.lock
M | bug 1820195 | glewlwyd (need to break dep [font corruption] or break packaging)
S | bug 1820196 | hyperkitty (avoid type error https://bugs.launchpad.net/ubuntu/+source/robot-detection/+bug/1820225/comments/2)
+ | bug 1820197 | itypes
- | n/a | jqueryui (no dep hyperkitty >=1.2.2-1)
+ C | bug 1820199 | lazr.config
+ C | bug 1820200 | lazr.delegates
-MJ | bug 1820201 | less.js (Dep will be cut out in Debian bug 924961)
- | n/a | libjs-jquery-colorpicker (no hyperkitty >=1.2.2-1)
S | bug 1820202 | libmatheval
S | bug 1820203 | libpgm
S C | bug 1775427 | mailman3
S | bug 1820204 | mailmanclient
S H | bug 1820205 | mailman-hyperkitty
+ | bug 1820206 | mailman-suite
-MJ | bug 1820207 | node-source-map (wait for node-less dep to be cut)
-MJ | bug 1820208 | nodejs (wait for node-less dep to be cut)
S+? | bug 1820209 | norm (check if embedded protolib is an issue)
+ | bug 1820982 | nose
S | bug 1820210 | postorius
M | bug 1820211 | python3-openid (change to python-openid)
M C | bug 1820212 | python-aiosmtpd (fix setuid, main loop and user nobody usage)
+T | bug 1820213 | python-arrow (non fatal build error on dateutil, tests)
+ | bug 1820214 | python-blessed
S+? | bug 1820215 | python-django-extensions (many functions in one package)
+ | bug 1820216 | python-django-gravatar2
STC | bug 1820217 | python-falcon (opt: update version before 20.04)
+ | bug 686045 | python-lockfile
+TC | bug 1820220 | python-public (opt: update version before 20.04)
+ | bug 1820221 | python-requests-oauthlib
+T | bug 1820223 | python-uritemplate (be a sync, better new upstream)
S | bug 1820224 | python-whoosh
+ | bug 1820225 | robot-detection
-M | n/a | ruby-sass (deprecated, use sassc - Debian 924629)
-M | TBD | sassc (Dep will be cut by Debian bug 924961)
-M | TBD | libsass (Dep will be cut by Debian bug 924961)
S | bug 1820226 | twitter-bootstrap3 (asked upstream to move to v4)
? | bug 1820227 | uwsgi (FTBFS: #1820095) (assigned to cyphermox)
+ | bug 1820229 | wcwidth
+ | bug 1597439 | zeromq3
STC | bug 1820233 | zope.component (version update)
STC | bug 1820234 | zope.configuration (version update)
STC | bug 1820236 | zope.event (version update)
STC | bug 1820237 | zope.hookable (version update)
STC | bug 1820238 | zope.i18nmessageid (version update)
STC | bug 1820239 | zope.schema (version update)
List Debian bugs we depend on being resolved as expected before
the dependency tree can completely be MIRed:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924629
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924961
This might sometimes be slightly out of date, to cross check and for history on all of them check git at:
https://git.launchpad.net/~ubuntu-server/+git/mailman3-MIR-party/tree/package-list.txt
---
Past Decisions in regard to this:
mailman is python2, mailman3 is python3, but also it has new dependency stack due to adopting django but also splitting or rewriting a lot of its components.
Q: Do we want bin:mailman3 or bin:mailman3-full in main? (the latter pulls
in src:mailman-suite as well). src:mailman-suite has potentially more
things - django, hyperkitty, ruby-sass, uwsgi...
A: We analyzed this and we will need the full set of dependencies, even
meaning MIRs are needed for all of the above listed (and more).
Q: Before proceeding further with assignment/doing technical work in
driving above MIRs, a product level yes/no answers should probably be
answered for above two questions.
A: Discussed in several sprints now, as uncomfortable as it is we will go
through the mass-MIR processing |
[Availability]
The package is already universe for quite a while and build/works fine so far.
It is for example already used for https://lists.canonical.com/mailman3/postorius/lists/
This source builds only docs and mailman3 itself (which provides mailman3-core).
[Rationale]
This is part of the MIR activity for all dependencies of mailman3
The "main" MIR of it is at bug 1775427:
Mailman (2) has only python2 support, but we strive for python3,
therefore Mailman3 which has python3 support should be promoted to main.
This is an evolution of the mailman2 core delivery engine of the system, but I can't guess how much it deviated so we need to recheck security (IMHO)
[Security]
No known CVEs found.
A few old issues can be found against mailman2 and one (but long fixed) for mailman 3
=> https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=mailman
[Quality assurance]
The mailman3 stacks as of now (Disco) installs fine and provides a base
config. But due to the nature of the package that needs further modification
to be of real use.
The package does in error cases ask a debconf-high question, but it is not going to be installed by default - so that is no MIR problem.
There are a few (2) Ubuntu bugs outstanding, but none of them is critical and stopping this MIR request.
There are a few (2) Debian bugs outstanding all seems to "just work" still, but when we main this in 19.10 we should at least evaluate and maybe adress this one:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921445
There are regular upstream releases and Debian packages them and fixes regularly.
No exotic HW involved.
The package ships a test suite, but it is not run at build time for upstream bug #400.
It tests things in a dep8 test thou to provide coverage.
d/watch is set up and ok.
No Lintian warning except fairly recent newer Standards version.
The package does not rely on demoted or obsolete packages.
[UI standards]
Comes with 7 translations in .po files
No End-user applications that needs a standard conformant desktop file.
[Dependencies]
Some dependencies are not in main, but we drive MIR for all related packages
that are not in main at the same time.
Please check the list of bugs from the main Mailman3 MIR in bug 1775427 to get an overview.
[Standards compliance]
The package meets the FHS and Debian Policy standards.
The packaging itself is very straight forward and uses dh_* as much as possible - the d/rules fits on one screen.
[Maintenance]
The Server team will subscribe for the package for maintenance
[Background]
The package description explains the general purpose and context of the package well.
---
References to all the related MIR bug - one per affected package.
Status (simplified version of https://wiki.ubuntu.com/MIRTeam#Process_states)
(nothing) means we have not even prepared the MIR yet
- MIR not needed (e.g. dependency will be dropped)
* all of the template fields for the MIR are complete
! waiting for MIR review
? cpaelzer needs experienced MIR team members to continue
S needs security review to be accepted
+ MIR accepted
x MIR nacked
Extra Flags which team members or on review feedback can be added:
T extra work for the team that should be done before 20.04 (state todo after package)
M extra work for the team before getting MIR to be acceptable (read as asap)
C needed if only promoting mailman3 (core)
H needed if only promoting mailman3 (core) plus Hyperkitty
J no more needed for mailman3-web if we can cut node-less out
FLAGS | MIR-Bug | Package (Notes)
TC
MH
----------------------------------------
+ | bug 1820179 | coreapi
+ | bug 1820180 | coreschema
S | bug 1820181 | django-allauth
+ | bug 1820182 | django-filter
S | bug 1820183 | django-guardian
+ | bug 1820185 | django-haystack
S | bug 1820186 | django-mailman3
- | | django-paintstore ((no dep hyperkitty >=1.2.2-1)
+ | bug 1820188 | django-picklefield
+ | bug 1820189 | django-q
S | bug 1820190 | djangorestframework
S C | bug 1820191 | flufl.bounce
+ C | bug 1820192 | flufl.i18n
+ C | bug 1820193 | flufl.lock
M | bug 1820195 | glewlwyd (need to break dep [font corruption] or break packaging)
S | bug 1820196 | hyperkitty (avoid type error https://bugs.launchpad.net/ubuntu/+source/robot-detection/+bug/1820225/comments/2)
+ | bug 1820197 | itypes
- | n/a | jqueryui (no dep hyperkitty >=1.2.2-1)
+ C | bug 1820199 | lazr.config
+ C | bug 1820200 | lazr.delegates
-MJ | bug 1820201 | less.js (Dep will be cut out in Debian bug 924961)
- | n/a | libjs-jquery-colorpicker (no hyperkitty >=1.2.2-1)
S | bug 1820202 | libmatheval
S | bug 1820203 | libpgm
S C | bug 1775427 | mailman3
S | bug 1820204 | mailmanclient
S H | bug 1820205 | mailman-hyperkitty
+ | bug 1820206 | mailman-suite
-MJ | bug 1820207 | node-source-map (wait for node-less dep to be cut)
-MJ | bug 1820208 | nodejs (wait for node-less dep to be cut)
S+? | bug 1820209 | norm (check if embedded protolib is an issue)
+ | bug 1820982 | nose
S | bug 1820210 | postorius
M | bug 1820211 | python3-openid (change to python-openid)
M C | bug 1820212 | python-aiosmtpd (fix setuid, main loop and user nobody usage)
+T | bug 1820213 | python-arrow (non fatal build error on dateutil, tests)
+ | bug 1820214 | python-blessed
S+? | bug 1820215 | python-django-extensions (many functions in one package)
+ | bug 1820216 | python-django-gravatar2
STC | bug 1820217 | python-falcon (opt: update version before 20.04)
+ | bug 686045 | python-lockfile
+TC | bug 1820220 | python-public (opt: update version before 20.04)
+ | bug 1820221 | python-requests-oauthlib
+T | bug 1820223 | python-uritemplate (be a sync, better new upstream)
S | bug 1820224 | python-whoosh
+ | bug 1820225 | robot-detection
-M | n/a | ruby-sass (deprecated, use sassc - Debian 924629)
-M | TBD | sassc (Dep will be cut by Debian bug 924961)
-M | TBD | libsass (Dep will be cut by Debian bug 924961)
S | bug 1820226 | twitter-bootstrap3 (need JS expert tom complete SEC-Review)
S | bug 1820227 | uwsgi (FTBFS: #1820095) (SEC ~Nack, needs simpler replacement)
+ | bug 1820229 | wcwidth
+ | bug 1597439 | zeromq3
STC | bug 1820233 | zope.component (version update)
STC | bug 1820234 | zope.configuration (version update)
STC | bug 1820236 | zope.event (version update)
STC | bug 1820237 | zope.hookable (version update)
+TC | bug 1820238 | zope.i18nmessageid (version update)
STC | bug 1820239 | zope.schema (version update)
List Debian bugs we depend on being resolved as expected before
the dependency tree can completely be MIRed:
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924629
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924961
This might sometimes be slightly out of date, to cross check and for history on all of them check git at:
https://git.launchpad.net/~ubuntu-server/+git/mailman3-MIR-party/tree/package-list.txt
---
Past Decisions in regard to this:
mailman is python2, mailman3 is python3, but also it has new dependency stack due to adopting django but also splitting or rewriting a lot of its components.
Q: Do we want bin:mailman3 or bin:mailman3-full in main? (the latter pulls
in src:mailman-suite as well). src:mailman-suite has potentially more
things - django, hyperkitty, ruby-sass, uwsgi...
A: We analyzed this and we will need the full set of dependencies, even
meaning MIRs are needed for all of the above listed (and more).
Q: Before proceeding further with assignment/doing technical work in
driving above MIRs, a product level yes/no answers should probably be
answered for above two questions.
A: Discussed in several sprints now, as uncomfortable as it is we will go
through the mass-MIR processing |
|
| 2019-07-02 19:52:19 |
Joshua Powers |
mailman3 (Ubuntu): assignee |
Ubuntu Security Team (ubuntu-security) |
|
|
| 2019-07-02 19:52:24 |
Joshua Powers |
mailman (Ubuntu): status |
Triaged |
Fix Released |
|
| 2019-07-02 19:52:26 |
Joshua Powers |
mailman3 (Ubuntu): status |
In Progress |
Won't Fix |
|
| 2019-07-03 01:55:23 |
Seth Arnold |
bug |
|
|
added subscriber Seth Arnold |
