Go to file
Olblak 18b42e7ed8
Merge pull request #18 from olblak/IEP-12
[WIP][INFRA-1657] Build & Release Jenkins
2019-06-17 16:20:35 +02:00
iep-001 Add a simple template.adoc based off IEP-001 for copy-pasting 2016-11-16 11:07:23 -08:00
iep-002 Mark IEP-2 as complete 2016-12-12 13:03:40 -08:00
iep-003 Flesh out the remainder of the first draft of IEP-3 2016-11-17 17:00:35 -08:00
iep-004 Merge remote-tracking branch 'upstream/kubernetes-004' into kubernetes-004 2017-03-17 16:36:17 +01:00
iep-005 It doesn't seem like we need to collect events, abandoning proposal 2017-06-16 07:35:36 -07:00
iep-006 Swap jenkins.io with www.jenkins.io 2017-07-06 14:23:19 +02:00
iep-007 IEP-007: Update HTTPS endpoint validation command 2018-01-12 10:04:57 +01:00
iep-008 Improve IEP-008 2018-03-20 15:58:31 +01:00
iep-009 Add an IEP describing the new incrementals Maven repository 2018-03-19 14:53:31 -07:00
iep-012 Fix link typo 2019-02-27 14:40:31 +01:00
.gitignore Add a simple generated file to make sure generated garbage doesn't get committed 2016-11-16 12:37:53 -08:00
LICENSE Initial commit 2016-10-25 17:03:51 -07:00
README.adoc Update the IEP authoring directions 2016-12-12 13:16:44 -08:00
template.adoc Add a simple template.adoc based off IEP-001 for copy-pasting 2016-11-16 11:07:23 -08:00

README.adoc

<html lang="en"> <head> </head>

Infrastructure Enhancement Proposals

This repository is for tracking enhancement proposals to the Jenkins projects infrastructure. The goal of this repository is to collect and codify proposals in a transparent and historically reviewable fashion. It can be thought of similar to efforts such as the IETFs RFC process or the Python projects PEPs.

Creating a proposal

  1. Prepare an AsciiDoc file outlining your proposal, using requirement verbiage following RFC 2119 and the directions from IEP-001.

  2. Copy template.adoc into the new iep-xxx/ folder as README.adoc, numbering the directory sequentially from the previous IEP.

  3. Write proposal

  4. Open a pull request.

</html>