[
https://issues.apache.org/jira/browse/CLOUDSTACK-212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13544012#comment-13544012
]
Chip Childers commented on CLOUDSTACK-212:
------------------------------------------
Rohit,
Thinking about the overall scope of what's happening for 4.1, and the relative
priority of this one (plus it's risk), I'd propose that we don't do it for 4.1.
However, your thinking about this happening after the 4.1 code freeze is
excellent. I believe that this should occur as one of the first steps for 4.2.
After we create a release branch for 4.1, master basically frees up for 4.2
activity.
I'm going to shift the fix version to 4.2, but do you want to come up with a
strategy for fixing this and propose on the ML?
> Switch java package structure from com.cloud to org.apache
> ----------------------------------------------------------
>
> Key: CLOUDSTACK-212
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-212
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: pre-4.0.0
> Reporter: Chip Childers
> Priority: Minor
> Fix For: 4.1.0
>
>
> Since the project has moved over to ASF, I'd like to suggest that we move
> from com.cloud to org.apache for the java package structure of our modules.
> If there is agreement, we can take this up after 4.0 is out the door.
--
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
