You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Larry West (JIRA)" <ji...@apache.org> on 2017/10/23 22:45:00 UTC

[jira] [Closed] (CODEC-243) Release 1.11 documentation polishing

     [ https://issues.apache.org/jira/browse/CODEC-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Larry West closed CODEC-243.
----------------------------

Looks great.

> Release 1.11 documentation polishing
> ------------------------------------
>
>                 Key: CODEC-243
>                 URL: https://issues.apache.org/jira/browse/CODEC-243
>             Project: Commons Codec
>          Issue Type: Bug
>    Affects Versions: 1.11
>         Environment: n/a
> website documentation only.
>            Reporter: Larry West
>            Priority: Minor
>              Labels: Documentation
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> These are actually trivial, but I called this minor because the effect is to make the release look not-quite-finished.
> 1. The Release Notes (http://www.apache.org/dist/commons/codec/RELEASE-NOTES.txt) proclaim: "The Apache Commons Codec team is pleased to announce the commons-codec-1.11-SNAPSHOT release!"
> The "-SNAPSHOT", of course, should be removed.
> 2. The changes report (https://commons.apache.org/proper/commons-codec/changes-report.html) has this index entry for 1.11:
> ||Version||Date||Description||
> |1.11|2017-MM-DD|Feature and fix release.|
> I wholeheartedly approve of the date format, but feel that more specificity of the date is required. 
> Same applies to the corresponding heading, *Release 1.11 – 2017-MM-DD*.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)