You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "Andrew Bayer (JIRA)" <ji...@apache.org> on 2013/05/23 21:27:20 UTC
[jira] [Assigned] (JCLOUDS-66) update project metadata
[ https://issues.apache.org/jira/browse/JCLOUDS-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Bayer reassigned JCLOUDS-66:
-----------------------------------
Assignee: Andrew Bayer
> update project metadata
> -----------------------
>
> Key: JCLOUDS-66
> URL: https://issues.apache.org/jira/browse/JCLOUDS-66
> Project: jclouds
> Issue Type: Task
> Components: jclouds-chef, jclouds-cli, jclouds-core, jclouds-examples, jclouds-karaf, jclouds-labs, jclouds-labs-aws, jclouds-labs-google, jclouds-labs-openstack
> Reporter: Adrian Cole
> Assignee: Andrew Bayer
> Priority: Blocker
> Fix For: 1.7.0, 1.6.1, 1.5.11
>
>
> in http://incubator.apache.org/guides/mentor.html#initial-ip-clearance
> there's a section on updating maven, and we have some missing parts:
> Update mailingLists
> Update organization
> Update url
> Update issueManagement
> Check licenses
> Update scm
> Update groupId
> Update manifestEntries. It is recommended that the standard Apache settings are used
> Update developers to use apache IDs (when known)
> Update distributionManagement
> Consider specifying a relocation
--
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