commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oliver Heger (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CONFIGURATION-579) Create a migration guide for version 2.0
Date Sat, 31 May 2014 19:17:02 GMT

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

Oliver Heger commented on CONFIGURATION-579:
--------------------------------------------

Many thanks for this offer!

Writing a migration guide requires knowledge of both the old classes and the new version.
I am currently working on updating the user's guide to describe the new features. During this
exercise I still find inconsistencies and missing features of the 2.0 API, so get distracted
from time to time. But my understanding was that an up-to-date user's guide would be a prerequisite
for the migration guide - or would at least make this task much more easier. OTOH, if you
like to explore the current code base on your own, this would also be an option. In any case,
feedback about the new API would be highly appreciated!

Regarding other open points for the 2.0 release: Are you subscribed to the Commons developers
list? This would be the right place to discuss this.

> Create a migration guide for version 2.0
> ----------------------------------------
>
>                 Key: CONFIGURATION-579
>                 URL: https://issues.apache.org/jira/browse/CONFIGURATION-579
>             Project: Commons Configuration
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions: 1.9
>            Reporter: Oliver Heger
>             Fix For: 2.0
>
>
> Users of version 1.x should be given a migration guide describing the changes in and
migration steps for version 2.0. Some parts of the library have been completely rewritten.
Therefore, guidance is required for users when porting their applications to the new version.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message