ecf68dbb05
- Rename IdSubmissionDetail to Submission - Rename various submission fields to correspond to the conventions in the new schema - Use a name model for the states instead of IdSubmissionStatus - Drop the TempIdAuthor model which is based on splitting up author names - Add a simple textual SubmissionEvent for tracking events in the lifetime of a submission - Delete a bunch of obsolete fields - Make sure all submission have an access key so we can depend on it - Add state for when approval is needed from previous authors A couple of migrations take care of transforming the IdSubmissionDetail and moving data over/cleaning it up. Also revamp the submit view code: - Make form code do validation/cleaning only so there's a clear separation of concerns - Reduce uses of inheritance that made the code hard to follow - forms now don't inherit from each other, views don't call each other but instead reuse common utilities, templates share CSS/utilities instead of relying on inheritance - Move email rendering/sending to separate file - Drop the in-grown terminology use (auto post vs. manual posts) - Make the status page explain who is emailed for what purpose - Add history table with recorded events - Make the status page handle its post actions by itself instead of duplicating most of the setup logic in a number of simple views - Fix a couple of minor bugs and handle some edge cases better - Expand tests with a couple of more cases Possibly the submit tool could still use more help text added to explain the process, ideally what's explained in the tool instructions page should be inlined or self-evident. - Legacy-Id: 6714
113 lines
3.5 KiB
Plaintext
113 lines
3.5 KiB
Plaintext
Informational Author Name
|
||
Internet-Draft Test Center Inc.
|
||
Intended status: Informational %(date)s
|
||
Expires: %(expire)s
|
||
|
||
|
||
Testing tests
|
||
%(name)s
|
||
|
||
|
||
Abstract
|
||
|
||
This document describes how to test tests.
|
||
|
||
Status of this Memo
|
||
|
||
This Internet-Draft is submitted in full conformance with the
|
||
provisions of BCP 78 and BCP 79.
|
||
|
||
Internet-Drafts are working documents of the Internet Engineering
|
||
Task Force (IETF). Note that other groups may also distribute
|
||
working documents as Internet-Drafts. The list of current Internet-
|
||
Drafts is at http://datatracker.ietf.org/drafts/current/.
|
||
|
||
Internet-Drafts are draft documents valid for a maximum of six months
|
||
and may be updated, replaced, or obsoleted by other documents at any
|
||
time. It is inappropriate to use Internet-Drafts as reference
|
||
material or to cite them other than as "work in progress."
|
||
|
||
This Internet-Draft will expire on %(expire)s.
|
||
|
||
Copyright Notice
|
||
|
||
Copyright (c) %(year)s IETF Trust and the persons identified as the
|
||
document authors. All rights reserved.
|
||
|
||
This document is subject to BCP 78 and the IETF Trust's Legal
|
||
Provisions Relating to IETF Documents
|
||
(http://trustee.ietf.org/license-info) in effect on the date of
|
||
publication of this document. Please review these documents
|
||
carefully, as they describe your rights and restrictions with respect
|
||
to this document. Code Components extracted from this document must
|
||
|
||
|
||
Name Expires %(expire)s [Page 1]
|
||
|
||
Internet-Draft Testing tests %(month_year)s
|
||
|
||
include Simplified BSD License text as described in Section 4.e of
|
||
the Trust Legal Provisions and are provided without warranty as
|
||
described in the Simplified BSD License.
|
||
|
||
This document may contain material from IETF Documents or IETF
|
||
Contributions published or made publicly available before November
|
||
10, 2008. The person(s) controlling the copyright in some of this
|
||
material may not have granted the IETF Trust the right to allow
|
||
modifications of such material outside the IETF Standards Process.
|
||
Without obtaining an adequate license from the person(s) controlling
|
||
the copyright in such materials, this document may not be modified
|
||
outside the IETF Standards Process, and derivative works of it may
|
||
not be created outside the IETF Standards Process, except to format
|
||
it for publication as an RFC or to translate it into languages other
|
||
than English.
|
||
|
||
|
||
Table of Contents
|
||
|
||
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
|
||
2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 4
|
||
3. Security Considerations . . . . . . . . . . . . . . . . . . . 4
|
||
|
||
|
||
Name Expires %(expire)s [Page 2]
|
||
|
||
Internet-Draft Testing tests %(month_year)s
|
||
|
||
1. Introduction
|
||
|
||
This document describes a protocol for testing tests.
|
||
|
||
Name Expires %(expire)s [Page 3]
|
||
|
||
Internet-Draft Testing tests %(month_year)s
|
||
|
||
2. Security Considerations
|
||
|
||
There are none.
|
||
|
||
|
||
3. IANA Considerations
|
||
|
||
No new registrations for IANA.
|
||
|
||
|
||
Authors' Addresses
|
||
|
||
Author Name
|
||
Test Center Inc.
|
||
42 Some Road
|
||
Some Where 12345
|
||
US
|
||
|
||
Email: author@example.com
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
Name Expires %(expire)s [Page 4]
|