I'll do the change tonight. Thanks.

- chip

Sent from my iPhone.

On Oct 9, 2012, at 5:16 PM, Noah Slater <[email protected]> wrote:

> Yep, even references in the docs!
>
> The official version will be "4.0.0-incubating", so we should refer to it
> as that in all places.
>
> On Tue, Oct 9, 2012 at 9:56 PM, Chip Childers 
> <[email protected]>wrote:
>
>> On Tue, Oct 9, 2012 at 4:24 PM, Noah Slater <[email protected]> wrote:
>>> Please make sure your build scripts also generate this internally for the
>>> code, and for the tarball name! ^_^
>>
>> I've included "incubating" in the source tarball creation script.
>>
>> Since we're not doing a binary distribution as a project, is it
>> required that all the pom's and package spec files refer to
>> incubating?  How far do we need to take this?  All references in the
>> docs? (I'm honestly asking...)
>>
>>> On Tue, Oct 9, 2012 at 9:23 PM, Chip Childers <[email protected]
>>> wrote:
>>>
>>>> On Tue, Oct 9, 2012 at 4:19 PM, Noah Slater <[email protected]>
>> wrote:
>>>>> Please change the version to "4.0-incubating".
>>>>
>>>> Done - thx
>>>>
>>>>> On Tue, Oct 9, 2012 at 12:51 AM, <[email protected]> wrote:
>>>>>
>>>>>> Adding a CHANGES file
>>>>>>
>>>>>>
>>>>>> Project:
>>>> http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/repo
>>>>>> Commit:
>> http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/commit/0427097a
>>>>>> Tree:
>> http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/tree/0427097a
>>>>>> Diff:
>> http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/diff/0427097a
>>>>>>
>>>>>> Branch: refs/heads/4.0
>>>>>> Commit: 0427097a048c10b3e39ae1b1ad07806fd85909da
>>>>>> Parents: 29e6dae
>>>>>> Author: Chip Childers <[email protected]>
>>>>>> Authored: Mon Oct 8 14:50:06 2012 -0400
>>>>>> Committer: Chip Childers <[email protected]>
>>>>>> Committed: Mon Oct 8 19:50:59 2012 -0400
>> ----------------------------------------------------------------------
>>>>>> CHANGES |   30 ++++++++++++++++++++++++++++++
>>>>>> 1 files changed, 30 insertions(+), 0 deletions(-)
>> ----------------------------------------------------------------------
>> http://git-wip-us.apache.org/repos/asf/incubator-cloudstack/blob/0427097a/CHANGES
>> ----------------------------------------------------------------------
>>>>>> diff --git a/CHANGES b/CHANGES
>>>>>> new file mode 100644
>>>>>> index 0000000..fa28f22
>>>>>> --- /dev/null
>>>>>> +++ b/CHANGES
>>>>>> @@ -0,0 +1,30 @@
>>>>>> +Apache CloudStack (Incubating) CHANGES
>>>>>> +======================================
>>>>>> +
>>>>>> +Full release notes for each release are located in the project's
>>>>>> documentation website:  http://docs.cloudstack.org/
>>>>>> +
>>>>>> +Version 4.0.0
>>>>>> +-------------
>>>>>> +
>>>>>> +Build Tool Changes:
>>>>>> +
>>>>>> + * The project now uses a combination of maven3 and ant for building
>>>>>> + * License header auditing is now implemented via the Apache RAT
>> Maven
>>>>>> plugin
>>>>>> + * Some integrations have been disabled in the default build, due to
>>>> the
>>>>>> license types of our dependencies (See README.md for details on how
>> to
>>>>>> build with the optional capabilities)
>>>>>> +
>>>>>> +New Features:
>>>>>> +
>>>>>> + * Inter-VLAN Routing (VPC)
>>>>>> + * Site-to-Site VPN
>>>>>> + * Local Storage Support for Data Volumes
>>>>>> + * Virtual Resource Tagging
>>>>>> + * Secure Console Access on XenServer
>>>>>> + * Added the ability to create a VM without immediately starting it
>>>> (via
>>>>>> API)
>>>>>> + * Upload an Existing Volume to a Virtual Machine
>>>>>> + * Dedicated High-Availability Hosts
>>>>>> + * Support for Amazon Web Services API (The Citrix CloudBridge
>> product
>>>> is
>>>>>> now part of Apache CloudStack)
>>>>>> + * AWS API Extensions to include Tagging
>>>>>> + * Cisco Nexus 1000v Virtual Switch for ESX
>>>>>> + * Support for Nicira NVP (L2)
>>>>>> + * Ceph RBD Support for KVM
>>>>>> + * Support for Caringo as Secondary Storage
>>>>>> \ No newline at end of file
>>>>>
>>>>>
>>>>> --
>>>>> NS
>>>
>>>
>>>
>>> --
>>> NS
>
>
>
> --
> NS

Reply via email to