Yep, that's what I thought. :-) I already updated the release.

Matt 


On 9/25/13 1:03 PM, "Animesh Chaturvedi" <[email protected]>
wrote:

>Well 1900+ is still true but it covers all the transient issues for
>features developed during 4.2.
>
>> -----Original Message-----
>> From: Mathias Mullins [mailto:[email protected]]
>> Sent: Wednesday, September 25, 2013 7:09 AM
>> To: [email protected]
>> Subject: Re: [ACS42] 4.2 Release Statement
>> 
>> That's fine. I thought 1900 was a bit excessive.
>> 
>> Matt
>> 
>> 
>> 
>> On 9/25/13 1:12 AM, "Animesh Chaturvedi" <[email protected]>
>> wrote:
>> 
>> >Mathias
>> >
>> >Sorry for this late comment but I am thinking instead of calling out
>> >fixing over 1900 issues many of which are the issues that were found
>> >and fixed in 4.2.0., should we instead say 160+ issues from 4.1.0 and
>> >4.1.1 were fixed [1]. The end user does not care about the transient
>> >issues for features developed in 4.2
>> >
>> >
>> >[1] https://issues.apache.org/jira/issues/#?filter=12324870
>> >
>> >Thanks
>> >Animesh
>> >
>> >> -----Original Message-----
>> >> From: Mathias Mullins [mailto:[email protected]]
>> >> Sent: Thursday, September 12, 2013 7:26 AM
>> >> To: [email protected]
>> >> Subject: Re: [ACS42] 4.2 Release Statement
>> >>
>> >> Great fixes Tracy!
>> >>
>> >> Much appreciated,
>> >> Matt
>> >>
>> >>
>> >> On 9/12/13 10:03 AM, "Tracy Phillips" <[email protected]> wrote:
>> >>
>> >> >Matt,
>> >> >
>> >> >I made a few tweaks, if you don't like them, please feel free to
>> >> >revert back to the original.
>> >> >
>> >> >
>> >> >On Wed, Sep 11, 2013 at 9:16 PM, Mathias Mullins
>> >> ><[email protected]
>> >> >> wrote:
>> >> >
>> >> >> Ok here's my first draft. Please edit boldly.
>> >> >>
>> >> >> Understand I intentionally tried to expand this one as I'M hoping
>> >> >>these  announcements will not only say we are putting out the next
>> >> >>release but  help to bring in more people, show them the width and
>> >> >>breath of the  product (like support from major players like Cisco)
>> >> >>and get us some more  press coverage and more adoption.
>> >> >>
>> >> >> I know we usually keep this sweet and simple, but I think we need
>> >> >> to up our message as well and show the maturity in our
>> >> >> announcements as
>> >> well.
>> >> >>
>> >> >>
>> >> >>https://cwiki.apache.org/confluence/display/CLOUDSTACK/4.2+Release+
>> >> >>Ann
>> >> >>oun
>> >> >>ce
>> >> >> ment
>> >> >>
>> >> >> Let me know what you think.
>> >> >> Matt
>> >> >>
>> >> >>
>> >> >>
>> >> >> On 8/30/13 8:00 PM, "Chip Childers" <[email protected]>
>> >> wrote:
>> >> >>
>> >> >> >Absolutely!
>> >> >> >
>> >> >> >However, as for formal, take a look at the 4.0.0 and 4.1.0
>> >> >>announcements.
>> >> >> > They aren't press releases either.  IMO 4.2.0 doesn't warrant
>> >> >> > one of
>> >> >>he
>> >> >> >*limited* press releases that the ASF has available.  That
>> >> >> >doesn't mean that it won't get sent out to [email protected].  But
>> >> >> >that's different from
>> >> >>a
>> >> >> >formal press release.
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> >On Fri, Aug 30, 2013 at 4:50 PM, Mathias Mullins
>> >> >> ><[email protected]
>> >> >> >> wrote:
>> >> >> >
>> >> >> >> Should we be working on putting together the release statement
>> >> >> >> for
>> >> >>4.2?
>> >> >> >> Since this is a Feature release, do we also want it in Press
>> >> >> >>Release format  to go out over announce@apache?
>> >> >> >>
>> >> >> >> Thanks,
>> >> >> >> Matt
>> >> >> >>
>> >> >>
>> >> >>
>> >
>

Reply via email to