New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Management Issue ordering on IESG agenda #1374
Comments
@cmorgan@amsl.com uploaded file |
@rjsparks@nostrum.com changed priority from |
@rjsparks@nostrum.com changed keywords from `` to |
@rjsparks@nostrum.com changed priority from |
@suresh.krishnan@ericsson.com changed status from |
@suresh.krishnan@ericsson.com changed owner from `` to |
@suresh.krishnan@ericsson.com changed status from |
@suresh.krishnan@ericsson.com changed owner from |
@jmh@joelhalpern.com changed priority from |
@jmh@joelhalpern.com commented Has come up once in 7.5 years. Can be worked around manually. |
@kaduk@mit.edu changed owner from `` to |
@housley@vigilsec.com changed status from |
@housley@vigilsec.com set resolution to |
@housley@vigilsec.com commented Fixed in 8cfa4c2: Properly sort the management items on the IETG telechat agenda. Fixes #1374. Ready for merge. |
@rjsparks@nostrum.com commented Fixed in ade3e2b: Merged in 8cfa4c2 from housley@vigilsec.com: |
keyword_sprint
owner:kaduk@mit.edu
resolution_fixed
type_defect
| by cmorgan@amsl.comHello, Tools Team!
The long break between formal IESG telechats has led to an unusually large number of Management Issues on this week's agenda. There is a bug in the ordering as to how these display on the agenda [*]. Item 6.10 shows up immediately after item 6.1, and before items 6.2 through 6.9.
[*] https://datatracker.ietf.org/iesg/agenda/
https://datatracker.ietf.org/iesg/agenda/agenda.txt
https://datatracker.ietf.org/iesg/agenda/moderator_package.html
Oddly enough, on https://datatracker.ietf.org/iesg/agenda/agenda_package.txt, the order is wrong under "2. AGENDA" but correct under "3. MANAGEMENT ITEM DETAILS."
We're fixing this manually in our packages this time around, but it would be nice if this could be corrected for the future.
Best regards,
Cindy
Issue migrated from trac:1374 at 2022-03-04 03:41:43 +0000
The text was updated successfully, but these errors were encountered: