fix: change trac.ietf.org links to what they redirect to now (#5651)
This commit is contained in:
Robert Sparks
GitHub
parent
2a27a2bffc
commit
f9322391dd
|
|
@ -189,8 +189,7 @@ def state_age_colored(doc):
|
|||
except IndexError:
|
||||
state_datetime = datetime.datetime(1990, 1, 1, tzinfo=datetime.timezone.utc)
|
||||
days = (timezone.now() - state_datetime).days
|
||||
# loosely based on
|
||||
# https://trac.ietf.org/trac/iesg/wiki/PublishPath
|
||||
# loosely based on the Publish Path page at the iesg wiki
|
||||
if iesg_state == "lc":
|
||||
goal1 = 30
|
||||
goal2 = 30
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@
|
|||
# can be translated to the newly expanded Constraint objects.
|
||||
#
|
||||
# This work was done in the context of the new meeting constraints modelling:
|
||||
# https://trac.ietf.org/trac/ietfdb/wiki/MeetingConstraints
|
||||
# https://github.com/ietf-tools/datatracker/wiki/MeetingConstraints
|
||||
# Note that aside from Constraint objects, as created below, there is also
|
||||
# business logic that applies to all sessions, which is to be implemented
|
||||
# in the automatic schedule builder.
|
||||
|
|
|
|||
|
|
@ -1,6 +1,6 @@
|
|||
# Copyright The IETF Trust 2021, All Rights Reserved
|
||||
# For an overview of this process and context, see:
|
||||
# https://trac.ietf.org/trac/ietfdb/wiki/MeetingConstraints
|
||||
# https://github.com/ietf-tools/datatracker/wiki/MeetingConstraints
|
||||
from __future__ import absolute_import, print_function, unicode_literals
|
||||
|
||||
import calendar
|
||||
|
|
|
|||
|
|
@ -833,7 +833,7 @@ class EditMeetingScheduleTests(IetfSeleniumTestCase):
|
|||
def test_session_constraint_hints(self):
|
||||
"""Selecting a session should mark conflicting sessions
|
||||
|
||||
To test for recurrence of https://trac.ietf.org/trac/ietfdb/ticket/3327 need to have some constraints that
|
||||
To test for recurrence of https://github.com/ietf-tools/datatracker/issues/3327 need to have some constraints that
|
||||
do not conflict. Testing with only violated constraints does not exercise the code adequately.
|
||||
"""
|
||||
meeting = MeetingFactory(type_id='ietf', date=date_today(), populate_schedule=False)
|
||||
|
|
|
|||
|
|
@ -48,7 +48,7 @@ def redirect(request, path="", script=""):
|
|||
pass # it's ok, request didn't have 'command'.
|
||||
except:
|
||||
pass # strange exception like the one described in
|
||||
# https://trac.ietf.org/trac/ietfdb/ticket/179?
|
||||
# https://github.com/ietf-tools/datatracker/issues/179
|
||||
# just ignore the command string.
|
||||
if cmd is not None:
|
||||
remove_args.append('command')
|
||||
|
|
|
|||
|
|
@ -23,7 +23,7 @@ from ietf.utils import log
|
|||
"""
|
||||
This file contains policies regarding reviewer queues.
|
||||
The policies are documented in more detail on:
|
||||
https://trac.ietf.org/trac/ietfdb/wiki/ReviewerQueuePolicy
|
||||
https://github.com/ietf-tools/datatracker/wiki/ReviewerQueuePolicy
|
||||
Terminology used here should match terminology used in that document.
|
||||
"""
|
||||
|
||||
|
|
|
|||
|
|
@ -840,7 +840,7 @@ class AssignmentOrderResolverTests(TestCase):
|
|||
self.assertEqual(len(ranking), 2)
|
||||
self.assertEqual(ranking[0]['email'], reviewer_high.email())
|
||||
self.assertEqual(ranking[1]['email'], reviewer_low.email())
|
||||
# These scores follow the ordering of https://trac.ietf.org/trac/ietfdb/wiki/ReviewerQueuePolicy,
|
||||
# These scores follow the ordering of https://github.com/ietf-tools/datatracker/wiki/ReviewerQueuePolicy,
|
||||
self.assertEqual(ranking[0]['scores'], [ 1, 1, 1, 1, 1, 1, 0, 0, -1])
|
||||
self.assertEqual(ranking[1]['scores'], [-1, -1, -1, -1, -1, -1, -91, -2, 0])
|
||||
self.assertEqual(ranking[0]['label'], 'Test Reviewer-high: unavailable indefinitely (Can do follow-ups); requested to be selected next for assignment; reviewed document before; wishes to review document; #2; 1 no response, 1 partially complete, 1 fully completed')
|
||||
|
|
|
|||
|
|
@ -125,9 +125,9 @@ to answer all of them.
|
|||
[1]: https://www.ietf.org/about/groups/iesg/
|
||||
[2]: https://www.rfc-editor.org/rfc/rfc4858.html
|
||||
[3]: https://www.rfc-editor.org/rfc/rfc7942.html
|
||||
[4]: https://trac.ietf.org/trac/ops/wiki/yang-review-tools
|
||||
[4]: https://wiki.ietf.org/group/ops/yang-review-tools
|
||||
[5]: https://www.rfc-editor.org/rfc/rfc8342.html
|
||||
[6]: https://trac.ietf.org/trac/iesg/wiki/ExpertTopics
|
||||
[6]: https://wiki.ietf.org/group/iesg/ExpertTopics
|
||||
[7]: https://www.rfc-editor.org/info/bcp79
|
||||
[8]: https://www.ietf.org/tools/idnits/
|
||||
[9]: https://www.rfc-editor.org/rfc/rfc3967.html
|
||||
|
|
|
|||
|
|
@ -18,13 +18,13 @@
|
|||
<h2>About Status Updates</h2>
|
||||
<p>
|
||||
Capturing group status updates in the datatracker allows including them in meeting proceedings. This capability was added to address the IESG request at
|
||||
<a href="https://trac.ietf.org/trac/ietfdb/ticket/1773">ticket 1773</a>.
|
||||
<a href="https://github.com/ietf-tools/datatracker/issues/1773">ticket 1773</a>.
|
||||
Not all groups are expected to provide status updates. Those that do have historically sent messages by email or have placed them on a wiki. For example, see
|
||||
<a href="https://mailarchive.ietf.org/arch/msg/saag/fo2b3KA47SM4MuQuYj5VIh-Tjok">
|
||||
the Kitten report sent to SAAG for IETF94
|
||||
</a>
|
||||
or the
|
||||
<a href="https://trac.ietf.org/trac/rtg/wiki/IETF94summary">Routing area high level summaries for IETF94</a>.
|
||||
<a href="https://wiki.ietf.org/group/rtg/IETF94summary">Routing area high level summaries for IETF94</a>.
|
||||
</p>
|
||||
</div>
|
||||
{% endif %}
|
||||
|
|
|
|||
|
|
@ -14,13 +14,13 @@
|
|||
<h2>About Status Updates</h2>
|
||||
<p>
|
||||
Capturing group status updates in the datatracker allows including them in meeting proceedings. This capability was added to address the IESG request at
|
||||
<a href="https://trac.ietf.org/trac/ietfdb/ticket/1773">ticket 1773</a>.
|
||||
<a href="https://github.com/ietf-tools/datatracker/issues/1773">ticket 1773</a>.
|
||||
Not all groups are expected to provide status updates. Those that do have historically sent messages by email or have placed them on a wiki. For example, see
|
||||
<a href="https://mailarchive.ietf.org/arch/msg/saag/fo2b3KA47SM4MuQuYj5VIh-Tjok">
|
||||
the Kitten report sent to SAAG for IETF94
|
||||
</a>
|
||||
or the
|
||||
<a href="https://trac.ietf.org/trac/rtg/wiki/IETF94summary">Routing area high level summaries for IETF94</a>.
|
||||
<a href="https://wiki.ietf.org/group/rtg/IETF94summary">Routing area high level summaries for IETF94</a>.
|
||||
</p>
|
||||
</div>
|
||||
<form enctype="multipart/form-data" method="post">
|
||||
|
|
|
|||
Loading…
Reference in a new issue