db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michelle Caisse (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JDO-723) Update release process for 3.1
Date Thu, 04 Jul 2013 18:25:48 GMT

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

Michelle Caisse commented on JDO-723:
-------------------------------------

I committed Michael's patch with some additional changes. I ported Andy's new DataNucleus
version numbers to this branch and added configuration for the deploy plugin to skip the subprojects
whose jar files we don't want to deploy. Also added some configuration that allows user-specific
injection of key id via settings.xml.

Additional issues for discussion:
1. Need to turn of automatic packaging of src?
2. Version numbers for copy-jdori-jars vs. jdo-exectck.
3. Configuration for SCM required for deployment: http://maven.apache.org/pom.html#SCM
...

                
> Update release process for 3.1
> ------------------------------
>
>                 Key: JDO-723
>                 URL: https://issues.apache.org/jira/browse/JDO-723
>             Project: JDO
>          Issue Type: Task
>          Components: site and infrastructure
>    Affects Versions: JDO 3 maintenance release 1 (3.1)
>            Reporter: Michelle Caisse
>             Fix For: JDO 3 maintenance release 1 (3.1)
>
>         Attachments: apache-release.patch
>
>
> The 3.1 release is the first JDO release using maven 2. In addition the Apache infrastructure
for testing and distributing releases has changed. We need to update our infrastructure, process,
and documents to reflect the new situation.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message