rel-html: update TODO for the next release objectives

Signed-off-by: Luis R. Rodriguez <mcgrof@do-not-panic.com>

1 files changed, 25 insertions, 2 deletions

diff --git a/README.md b/README.md
index 0fd99d9..967ba12 100644
--- a/README.md
+++ b/README.md
@@ -4,7 +4,10 @@ rel-html is designed to parse naked index html pages
 with tarballs on a software project and automatically
 produce a nice shiny HTML5 release page for you. It takes
 as input a configuration file, rel-html.cfg, in which
-you can specify attributes for the release.
+you can specify attributes for the release. Exact stable
+releases are inferred based on some hints, but we still
+require at least the base releases that are supported to
+be annoated.
 
 # Example release page
 
@@ -22,8 +25,28 @@ you can specify attributes for the release.
 	- If we have many stable releases how should
 	  we annotate this via git ?
 
+   It seems that the way to go is to require a config file
+   for the project with the oldest stable release supported
+   and then annotate eols. We do this right now, so rel-html
+   would just need to be modified to infer newer releases.
+
+ * The Linux kernel now (as of 2013-03-10) has json file for
+   releases:
+
+	https://www.kernel.org/releases.json
+
+  We need to do a few things then:
+
+	- Get other projects to use json for releases
+	- Add json intepreter support to rel-html
+
+  If projects don't use json releases files as the Linux
+  kernel does then the current usage of HTMLParser would
+  allow us to parse / infer releases for us.
+
  * See if we can copy the EOL release into an eol/ directory
    and moving forward instead of parsing the tags use the
    directory name to automatically determine other release
-   attributes.
+   attributes. This is only relevant for the Linux kernel
+   right now.