db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig L Russell (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JDO-699) Archive unmaintained modules
Date Fri, 28 Oct 2011 17:31:32 GMT

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

Craig L Russell commented on JDO-699:
-------------------------------------

I agree that keeping unmaintained sub-projects in trunk is not good. Moving them to a new
archive directory makes sense. I wouldn't just delete them since it would then be difficult
to find them.
                
> Archive unmaintained modules
> ----------------------------
>
>                 Key: JDO-699
>                 URL: https://issues.apache.org/jira/browse/JDO-699
>             Project: JDO
>          Issue Type: Improvement
>          Components: api11, api2-legacy, btree, core2, enhancer2, fostore2, model2, query2,
ri11, runtime2, tck11, tck2-legacy, util2
>    Affects Versions: JDO 3 maintenance release 1
>            Reporter: Matthew T. Adams
>            Assignee: Matthew T. Adams
>             Fix For: JDO 3 maintenance release 1
>
>
> There are many modules in the trunk of the JDO source repo that are no longer maintained.
 I propose to create a new directory "archive" as a peer to trunk, branches, releases, and
site, then svn-move them from trunk to archive.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message