[jira] [Commented] (MDOAP-66) Don't assume latest release is "Stable"

["Brian Demers (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MDOAP-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17762506#comment-17762506 ] 

Brian Demers commented on MDOAP-66:
-----------------------------------

proposed fix: https://github.com/apache/maven-doap-plugin/pull/14

> Don't assume latest release is "Stable"
> ---------------------------------------
>
>                 Key: MDOAP-66
>                 URL: https://issues.apache.org/jira/browse/MDOAP-66
>             Project: Maven DOAP Plugin
>          Issue Type: Bug
>            Reporter: Brian Demers
>            Priority: Major
>
> The DOAP plugin assumes that the lastest release in the Maven metadata is "stable".
> https://github.com/apache/maven-doap-plugin/blob/04a8fb9ec390830783169701c1d60e95b7dd5bfc/src/main/java/org/apache/maven/plugin/doap/DoapMojo.java#L1337
> The term "latest" does not imply anything about stability, nor release sequence.  I could release 2.1.1 today, and 1.2.3 tomorrow.  1.2.3 would be marked "latest stable release"
> Or I could release 2.0.0-alpha1, and that would be labeled as "Latest stable release".
> My suggestion would be remove this code branch, and not make any assumptions about the version name



--
This message was sent by Atlassian Jira
(v8.20.10#820010)