You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@commons.apache.org by "Thomas Vandahl (Jira)" <ji...@apache.org> on 2020/03/17 07:51:00 UTC

[jira] [Commented] (JCS-204) Craft a new 2.3 release

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

Thomas Vandahl commented on JCS-204:
------------------------------------

Unfortunately, the current trunk/master contains lots of breaking changes, so that a new release *must* be 3.x. This will require the package name as well as the Maven coordinates to reflect this. I'll see what I can do.

> Craft a new 2.3 release
> -----------------------
>
>                 Key: JCS-204
>                 URL: https://issues.apache.org/jira/browse/JCS-204
>             Project: Commons JCS
>          Issue Type: Task
>            Reporter: Simon Legner
>            Priority: Major
>              Labels: release
>
> Many improvements have been made since the last 2.2.1 release in 2017: https://github.com/apache/commons-jcs/compare/commons-jcs-2.2.1...master
> [JOSM|https://josm.openstreetmap.de/] always has been using the latest SVN version of JCS without any known problems. We would like to switch to Apache Ivy for dependency management and thus require a published release.
> Can you craft a new 2.3 release of JCS? Are there any blockers?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)