[jira] [Commented] (ACCUMULO-2394) Create release notes
[ https://issues.apache.org/jira/browse/ACCUMULO-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14065987#comment-14065987 ] Mike Drob commented on ACCUMULO-2394: - Is this issue done? Create release notes Key: ACCUMULO-2394 URL: https://issues.apache.org/jira/browse/ACCUMULO-2394 Project: Accumulo Issue Type: Task Components: docs Reporter: Josh Elser The big point that came out of the massive discussion on the CHANGES file is that we should also be generating an easy-to-consume release notes page. Ideally, we want something visually appealing, easy for us to maintain, version controlled and not requiring manual HTML (e.g. Markdown, etc). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (ACCUMULO-2394) Create release notes
[ https://issues.apache.org/jira/browse/ACCUMULO-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13924057#comment-13924057 ] ASF subversion and git services commented on ACCUMULO-2394: --- Commit 1575325 from [~elserj] in branch 'site/trunk' [ https://svn.apache.org/r1575325 ] ACCUMULO-2394 Add section on how to update javadocs Create release notes Key: ACCUMULO-2394 URL: https://issues.apache.org/jira/browse/ACCUMULO-2394 Project: Accumulo Issue Type: Task Components: docs Reporter: Josh Elser The big point that came out of the massive discussion on the CHANGES file is that we should also be generating an easy-to-consume release notes page. Ideally, we want something visually appealing, easy for us to maintain, version controlled and not requiring manual HTML (e.g. Markdown, etc). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (ACCUMULO-2394) Create release notes
[ https://issues.apache.org/jira/browse/ACCUMULO-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13924077#comment-13924077 ] Josh Elser commented on ACCUMULO-2394: -- 1575325 was actually for how-to-make-a-release, not release notes. Oops. Create release notes Key: ACCUMULO-2394 URL: https://issues.apache.org/jira/browse/ACCUMULO-2394 Project: Accumulo Issue Type: Task Components: docs Reporter: Josh Elser The big point that came out of the massive discussion on the CHANGES file is that we should also be generating an easy-to-consume release notes page. Ideally, we want something visually appealing, easy for us to maintain, version controlled and not requiring manual HTML (e.g. Markdown, etc). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (ACCUMULO-2394) Create release notes
[ https://issues.apache.org/jira/browse/ACCUMULO-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13923023#comment-13923023 ] ASF subversion and git services commented on ACCUMULO-2394: --- Commit 1575035 from [~elserj] in branch 'site/trunk' [ https://svn.apache.org/r1575035 ] ACCUMULO-2394 Add some more changes to the release notes for 1.5.1 Create release notes Key: ACCUMULO-2394 URL: https://issues.apache.org/jira/browse/ACCUMULO-2394 Project: Accumulo Issue Type: Task Components: docs Reporter: Josh Elser The big point that came out of the massive discussion on the CHANGES file is that we should also be generating an easy-to-consume release notes page. Ideally, we want something visually appealing, easy for us to maintain, version controlled and not requiring manual HTML (e.g. Markdown, etc). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (ACCUMULO-2394) Create release notes
[ https://issues.apache.org/jira/browse/ACCUMULO-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13923222#comment-13923222 ] ASF subversion and git services commented on ACCUMULO-2394: --- Commit 1575093 from [~elserj] in branch 'site/trunk' [ https://svn.apache.org/r1575093 ] ACCUMULO-2394 Fix bad english on 1.5.1 release notes Create release notes Key: ACCUMULO-2394 URL: https://issues.apache.org/jira/browse/ACCUMULO-2394 Project: Accumulo Issue Type: Task Components: docs Reporter: Josh Elser The big point that came out of the massive discussion on the CHANGES file is that we should also be generating an easy-to-consume release notes page. Ideally, we want something visually appealing, easy for us to maintain, version controlled and not requiring manual HTML (e.g. Markdown, etc). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (ACCUMULO-2394) Create release notes
[ https://issues.apache.org/jira/browse/ACCUMULO-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13923251#comment-13923251 ] ASF subversion and git services commented on ACCUMULO-2394: --- Commit 1575095 from [~elserj] in branch 'site/trunk' [ https://svn.apache.org/r1575095 ] ACCUMULO-2394 Add a paragraph about MTBW fixes Create release notes Key: ACCUMULO-2394 URL: https://issues.apache.org/jira/browse/ACCUMULO-2394 Project: Accumulo Issue Type: Task Components: docs Reporter: Josh Elser The big point that came out of the massive discussion on the CHANGES file is that we should also be generating an easy-to-consume release notes page. Ideally, we want something visually appealing, easy for us to maintain, version controlled and not requiring manual HTML (e.g. Markdown, etc). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (ACCUMULO-2394) Create release notes
[ https://issues.apache.org/jira/browse/ACCUMULO-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13913978#comment-13913978 ] ASF subversion and git services commented on ACCUMULO-2394: --- Commit 1572413 from [~elserj] in branch 'site/trunk' [ https://svn.apache.org/r1572413 ] ACCUMULO-2394 Write down what should be in CHANGES Create release notes Key: ACCUMULO-2394 URL: https://issues.apache.org/jira/browse/ACCUMULO-2394 Project: Accumulo Issue Type: Task Components: docs Reporter: Josh Elser The big point that came out of the massive discussion on the CHANGES file is that we should also be generating an easy-to-consume release notes page. Ideally, we want something visually appealing, easy for us to maintain, version controlled and not requiring manual HTML (e.g. Markdown, etc). -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (ACCUMULO-2394) Create release notes
[ https://issues.apache.org/jira/browse/ACCUMULO-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13914015#comment-13914015 ] Josh Elser commented on ACCUMULO-2394: -- Oops, wrong ticket number Create release notes Key: ACCUMULO-2394 URL: https://issues.apache.org/jira/browse/ACCUMULO-2394 Project: Accumulo Issue Type: Task Components: docs Reporter: Josh Elser The big point that came out of the massive discussion on the CHANGES file is that we should also be generating an easy-to-consume release notes page. Ideally, we want something visually appealing, easy for us to maintain, version controlled and not requiring manual HTML (e.g. Markdown, etc). -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (ACCUMULO-2394) Create release notes
[ https://issues.apache.org/jira/browse/ACCUMULO-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13910258#comment-13910258 ] Mike Drob commented on ACCUMULO-2394: - bq. We could link directly to the release notes content hosted elsewhere (just like CHANGES is now). CHANGES is still hosted on ASF servers. I was under the impression that we need to keep our content local somewhere. Create release notes Key: ACCUMULO-2394 URL: https://issues.apache.org/jira/browse/ACCUMULO-2394 Project: Accumulo Issue Type: Task Components: docs Reporter: Josh Elser The big point that came out of the massive discussion on the CHANGES file is that we should also be generating an easy-to-consume release notes page. Ideally, we want something visually appealing, easy for us to maintain, version controlled and not requiring manual HTML (e.g. Markdown, etc). -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (ACCUMULO-2394) Create release notes
[ https://issues.apache.org/jira/browse/ACCUMULO-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13910384#comment-13910384 ] Josh Elser commented on ACCUMULO-2394: -- I wasn't implying not on ASF resources by elsewhere. I just meant not directly in the CMS. Create release notes Key: ACCUMULO-2394 URL: https://issues.apache.org/jira/browse/ACCUMULO-2394 Project: Accumulo Issue Type: Task Components: docs Reporter: Josh Elser The big point that came out of the massive discussion on the CHANGES file is that we should also be generating an easy-to-consume release notes page. Ideally, we want something visually appealing, easy for us to maintain, version controlled and not requiring manual HTML (e.g. Markdown, etc). -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (ACCUMULO-2394) Create release notes
[ https://issues.apache.org/jira/browse/ACCUMULO-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13909711#comment-13909711 ] Sean Busbey commented on ACCUMULO-2394: --- I like the way this looks, but what's the gain over keeping it in ASF CMS directly as markdown? Wouldn't it meet all of the criteria for this issue? We'd have to export it for a release. I'm not sure that's more work than having to push updates out of the main repo to the website. Create release notes Key: ACCUMULO-2394 URL: https://issues.apache.org/jira/browse/ACCUMULO-2394 Project: Accumulo Issue Type: Task Components: docs Reporter: Josh Elser The big point that came out of the massive discussion on the CHANGES file is that we should also be generating an easy-to-consume release notes page. Ideally, we want something visually appealing, easy for us to maintain, version controlled and not requiring manual HTML (e.g. Markdown, etc). -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (ACCUMULO-2394) Create release notes
[ https://issues.apache.org/jira/browse/ACCUMULO-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13909853#comment-13909853 ] Josh Elser commented on ACCUMULO-2394: -- bq. Wouldn't it meet all of the criteria for this issue? Probably -- the ASF CMS is just much more of a pain to work with IMO. It's also not a part of the source tree which I'm not a fan of either (you should get the release notes in the artifact you download just as you do the CHANGES). Thinking some more, it's not a requirement that the release notes are integrated into the main a.a.o website. We could link directly to the release notes content hosted elsewhere (just like CHANGES is now). Exporting isn't a huge concern to me because that's something that isn't difficult to do. Getting release notes in the release artifacts would arguably require just as much work (if not more since it has to be put in tarball, rpms and debs). Overall, I'm not sold on this approach, but I had to the time so I just did it (it literally didn't take more than about 30mins). Jekyll is so much easier to generally use, provides a lot of nice features in building something like this and is easier to get installed. Integration with everything else is a concern. Create release notes Key: ACCUMULO-2394 URL: https://issues.apache.org/jira/browse/ACCUMULO-2394 Project: Accumulo Issue Type: Task Components: docs Reporter: Josh Elser The big point that came out of the massive discussion on the CHANGES file is that we should also be generating an easy-to-consume release notes page. Ideally, we want something visually appealing, easy for us to maintain, version controlled and not requiring manual HTML (e.g. Markdown, etc). -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Commented] (ACCUMULO-2394) Create release notes
[ https://issues.apache.org/jira/browse/ACCUMULO-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13909643#comment-13909643 ] Josh Elser commented on ACCUMULO-2394: -- I had some down time today, so I started poking around. Made a basic release notes Jekyll site. I like it because all it requires is making a new markdown/html file named mm-dd--version.md (e.g. 2013-05-27-1.5.0.md), and it will automatically update a new website with the content. The index page shows the most recent releases first, and allows you to directly link to a specific version. I made enough style changes to make it not completely ugly, and the content is all lorem ipsums, but it should convey the idea. I like the idea of keeping this in the main source tree (use/write a quick maven-jekyll-plugin or just exec out to the command line), but that would introduce more effort to get it into the ASF CMS. Not entirely sure, but I wanted to at least start it out. Code: https://github.com/joshelser/accumulo-release-notes Staged: http://accumulo-release-notes.penguinsinabox.com/ Create release notes Key: ACCUMULO-2394 URL: https://issues.apache.org/jira/browse/ACCUMULO-2394 Project: Accumulo Issue Type: Task Components: docs Reporter: Josh Elser The big point that came out of the massive discussion on the CHANGES file is that we should also be generating an easy-to-consume release notes page. Ideally, we want something visually appealing, easy for us to maintain, version controlled and not requiring manual HTML (e.g. Markdown, etc). -- This message was sent by Atlassian JIRA (v6.1.5#6160)
