Skip to content

Latest commit

 

History

History
57 lines (30 loc) · 1.7 KB

sep-template.md

File metadata and controls

57 lines (30 loc) · 1.7 KB

title here

author:

date-created: 2020 January 1

date-last-revised: 2020 January 1

date-accepted: 2020 January 1

status: Discussion

Abstract

The abstract should be a short description of what the proposal will achieve.

Detailed description

This section describes the need for the proposal. It should describe the existing problem that it is trying to solve and why this proposal makes the situation better. It should include examples of how the new functionality would be used and perhaps some use cases.

Branches and pull requests

Any pull requests or development branches containing work on this proposal should be linked to from here. (A proposal does not need to be implemented in a single pull request if it makes sense to implement it in discrete phases). If no code is yet implemented, just put "N/A"

Implementation

This section lists the major steps required to implement the proposal. Where possible, it should be noted where one step is dependent on another, and which steps may be optionally omitted. Where it makes sense, each step should include a link related pull requests as the implementation progresses.

Backward compatibility

This section describes the ways in which the APE breaks backward compatibility.

Alternatives

If there were any alternative solutions to solving the same problem, they should be discussed here, along with a justification for the chosen approach.

Decision rationale