It shouldn't, but it will be reviewed during the release process at a
minimum.

-chip

On Tue, Feb 12, 2013 at 10:09:14PM +0000, Sudha Ponnaganti (JIRA) wrote:
> 
>      [ 
> https://issues.apache.org/jira/browse/CLOUDSTACK-1076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>  ]
> 
> Sudha Ponnaganti closed CLOUDSTACK-1076.
> ----------------------------------------
> 
> 
> closing as there is no QA - Does this require any additional Review??
>                 
> > Legal documentation improvements to separate source distributions from 
> > packaged distributions.
> > ----------------------------------------------------------------------------------------------
> >
> >                 Key: CLOUDSTACK-1076
> >                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1076
> >             Project: CloudStack
> >          Issue Type: Improvement
> >      Security Level: Public(Anyone can view this level - this is the 
> > default.) 
> >            Reporter: Chip Childers
> >            Assignee: Chip Childers
> >             Fix For: 4.1.0
> >
> >
> > As discussed on the dev list, I'd like to make the following changes in 
> > master:
> > * Remove all binary dependency license and notice info from the top
> > level LICENSE and NOTICE files in our source tree
> > * Create two copies of the Whisker descriptor.xml file (stored in
> > tools/whisker), one that can be used to regenerate the source distro's
> > LICENSE and NOTICE files, and one that can generate an appropriate
> > LICENSE and NOTICE file for a packaged version of the software.
> > * Generate and commit the package LICENSE and NOTICE file to the
> > tools/whisker folder.
> > * Ask that the folks working on packaging take the (to be committed)
> > tools/whisker/LICENSE and tools/whisker/NOTICE files as the correct
> > legal documents to include with the package installation.
> 
> --
> 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
> 

Reply via email to