[
https://issues.apache.org/jira/browse/ACCUMULO-2394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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)
