On Thu, Jun 06, 2013 at 10:50:03AM +0530, Prasanna Santhanam wrote:
> Hi,
>
> I would like to get everyone's opinions on the timeline and policies
> for bringing in automated tests into the repo. Integration tests are
> written in marvin by various people today within and without Citrix.
> Similar
> -Original Message-
> From: Joe Brockmeier [mailto:j...@zonker.net]
> Sent: Thursday, June 06, 2013 5:14 AM
> To: dev@cloudstack.apache.org
> Subject: Re: [DISCUSS] code-freeze and integration tests
>
> On Thu, Jun 6, 2013, at 12:20 AM, Prasanna Santhanam wrote:
&g
It should not affect tests. We want to move to mostly if not all automated
tests. If we freeze the tests that means no more testing for the release. :P
--Alex
> -Original Message-
> From: Prasanna Santhanam [mailto:t...@apache.org]
> Sent: Wednesday, June 5, 2013 10:20 PM
> To: CloudS
On Thu, Jun 6, 2013, at 12:20 AM, Prasanna Santhanam wrote:
> I would like to get everyone's opinions on the timeline and policies
> for bringing in automated tests into the repo. Integration tests are
> written in marvin by various people today within and without Citrix.
> Similar to docs I'd like
On Thu, Jun 6, 2013 at 1:20 AM, Prasanna Santhanam wrote:
> Hi,
>
> I would like to get everyone's opinions on the timeline and policies
> for bringing in automated tests into the repo. Integration tests are
> written in marvin by various people today within and without Citrix.
> Similar to docs I
+1 Feature freeze and even RC timelines should not be applicable to automation
tests at this time. BVT and other regression tests would continue to be
developed beyond release date as well in reality. So dates should not hold for
Automation.
However having some timeline restriction would hel
