There are two features that did not make the 4.0 release: autoscaling and
brocade. Significant code changes are expected for both of these features past
the code freeze and we just couldn't risk the disruption to the QA cycle.
Please comment.
--Alex
> -Original Message-
> From: Wido den Hollander [mailto:w...@widodh.nl]
> Sent: Friday, September 21, 2012 10:15 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [ASFCS40] Features that did not make the release...
>
>
>
> On 09/21/2012 06:24 PM,
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/7168/#review11841
---
Does this need to go into 4.0?
- Alex Huang
On Sept. 19, 2012, 3
I want to thank everyone for taking time out of their busy schedule to clear up
the review board. What a great job! We're basically in our last stretch now.
We've reduced from 60+ mostly code related reviews down to about 27 reviews.
The majority of the 27 reviews left are in docs, licensing
Sanjay,
This feature needs to be contained within the XenServer plugin framework. It
should not make changes to the CloudStack core.
--Alex
> -Original Message-
> From: Sanjay Tripathi [mailto:sanjay.tripa...@citrix.com]
> Sent: Monday, September 24, 2012 6:33 AM
> To: cloudstack-dev@i
Hi All,
I've been reminded that I've neglected to update the community on the current
status for CloudStack 4.0. I apologize for that oversight. From now til the
actual release, I will give a daily update on the status. If you feel anything
is missing, please let me know and I'll try to incl
cheme until we have
> something to vote on officially?
>
> - chip
>
> Sent from my iPhone.
>
> On Sep 24, 2012, at 10:27 PM, Alex Huang wrote:
>
> > Hi All,
> >
> > I've been reminded that I've neglected to update the community on the
> c
; Thanks,
> Ram
>
>
> > -Original Message-
> > From: Alex Huang [mailto:alex.hu...@citrix.com]
> > Sent: 25 September 2012 07:57
> > To: cloudstack-dev@incubator.apache.org
> > Cc: cloudstack-us...@incubator.apache.org
> > Subject: [AFSCS40] Rele
When CloudStack stops a VM, it completely takes out the VM meta information
from the XenServer database and then reconstructs it when it starts the VM.
You can't do anything unless you want to change cloudstack code.
--Alex
> -Original Message-
> From: Nguyen Anh Tu [mailto:ng.t...@gmai
; Subject: Re: How does XenCenter show stopped state when stop VM from
> CloudStack
>
> I dit it. A smail trick during stopping time.
>
> 2012/9/26 Nguyen Anh Tu
>
> > Thanks for your information, Alex. Looking for AutoScale feature!
> > However, I will try to do some
heckins are currently going to *autoscale* branch.
> I have to generate 4 more reviews and then it will done.
> After that, my plan is to rebase autoscale branch against master (with proper
> unit testing) and send a request for merge. Is this fine?
>
> Thanks,
> Vijay V.
>
I will be gone in that range of time.
--Alex
All you have to do is look up your name and then look to see if the review has
been changed from yesterday. If you haven't kept track of this daily email,
then you need to look at all the items under your name and work on all of them.
Please scan the list for your name.
- The first column is
nk to user/administrative guides
--Alex
- Alex Huang
On Sept. 26, 2012, 3:46 p.m., Rohit Yadav wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://rev
Instead of sending out emails, I've updated the 4.0 release page [1]. You can
head there to find the current testing.
--Alex
[1]
https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+4.0+Release
es":
> >
> >
> > https://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&re
> > questId=12322493
> >
> > Feel free to put this on the wiki, though you should see it in your UI.
> >
> > If you want changes, or new filters making, give me a shout
Chip,
In one of the emails, I saw that you said the licenses are not completely
resolved. Can you send me a list of things to do? Majority of the Jira bugs
on license seem to be on resolved now. So I don't have a complete picture on
what else may be a risk to completing the 4.0 release.
Tha
> Another alternative for achieving this (without adding the per-hypervisor
> logic to CloudStack itself) might be to build a framework for plugging in
> best-
> of-breed update tools for the various hypervisors (and bare metal servers).
> Example: provide the KVM update feature via a combination
ip Childers [mailto:chip.child...@sungard.com]
> Sent: Monday, October 01, 2012 12:31 PM
> To: Alex Huang
> Cc: cloudstack-dev@incubator.apache.org
> Subject: Re: [AFSCS40] Risks to release...
>
> There was one bug that was reopened on Sunday to add a public domain
> statement for the rsyslo
I've also added this page [1] to keep track of features that will be in 4.1.0.
Please use that to submit your features and specs, etc.
--Alex
[1]
https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Next+Release
> -Original Message-
> From: Chip Childers [mailto:chip.chil
> On Sept. 28, 2012, 9:35 a.m., Rohit Yadav wrote:
> > Ship It!
4.0 Commit id: 381c649
Master commit id: 02ca9c2
- Alex
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/7339/#review12018
-
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/7342/#review12086
---
Ship it!
Ship It!
- Alex Huang
On Oct. 1, 2012, 5:23 p.m
> On Oct. 2, 2012, 12:36 a.m., Alex Huang wrote:
> > Ship It!
4.0: 986ceff
master: 25e8deb
- Alex
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/7342/#re
All you have to do is look up your name and then look to see if the review has
been changed from yesterday. If you haven't kept track of this daily email,
then you need to look at all the items under your name and work on all of them.
Please scan the list for your name.
- The first column is
Is that happening tomorrow?
The key agenda I want to go over is whether we're ready to release to PMC.
--Alex
Hi All,
Our status checking on bugs have been inconsistent. I like to share this
workflow diagram with you about how bug statuses should work.
Here are a few rules about working on Jira.
1. If you're working on a bug, mark it as In Progress
2. If you're not a committer, mark the bug as Ready
Hi Everyone,
I apologize for how late this RFC is sent in the 4.0.0 release. Noah gave an
example during irc today what the process should be. This email should have
been sent quite some time ago. I think the community has already been in
release mode for basically the past month. This is j
Hi Sridhar,
NetworkGuru designs the L2/L3 network for CloudStack. NetworkElement provides
a network service to CloudStack.
It works as follows:
CloudStack talks to NG to get a network that can actually be implemented by the
underlying physical networks and then it informs all of the NEs that
Sudha,
I don't think the minutes being posted one day late is the issue. I think what
Noah means here is that the meeting minutes contains a gtm that is no longer
usable so no one on the list can actually join the gtm.
Correct me if I'm wrong but that gtm is actually used every day by the QA
+1 on one clear destination. If it has to start fresh, then it has to start
fresh. Let's identify the content to move and move them over.
--Alex
> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Thursday, October 04, 2012 1:49 PM
> To: cloudstack-dev
Hi Chip,
Can you put up another source package?
Thanks.
--Alex
Thanks! I believe this is the one we'll be using for voting.
--Alex
> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Thursday, October 04, 2012 8:58 PM
> To: Alex Huang
> Cc: cloudstack-dev@incubator.apache.org
> Subject:
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/7435/#review12188
---
Ship it!
Ship It!
- Alex Huang
On Oct. 4, 2012, 9:58 a.m
> On Oct. 5, 2012, 4:06 a.m., Alex Huang wrote:
> > Ship It!
master: 7a22826
4.0: feb669a
- Alex
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/7435/#re
Hello,
I would like call a vote for the Apache CloudStack 4.0.0 release, first round.
We encourage the whole community to download and test these release
artifacts so that any critical issues can be resolved before the release is
made. Everyone is free to vote on this release.
We are voting on t
it was
for bug 254.
--Alex
> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Friday, October 05, 2012 7:07 AM
> To: cloudstack-dev@incubator.apache.org
> Cc: Alex Huang; Edison Su
> Subject: Re: Pending commits/reviews on 4.0?
>
>
> Alex,
>
> A couple of issues.
>
> First, we shouldn't be voting on the "beta" release artifacts. I need to cut
> a
> proper 4.0.0 build for us to vote on.
>
> Second, there are still several bugs that I consider to be blockers
> outstanding
> right now.
>
> Unfortunately, my vote is -1 for
> Yes, you should call a vote expecting it to pass. Releases can't be vetoed,
> so it
> should be pretty serious objections to stop at that point.
>
> For the mechanism beyond that, it can go either way - communities I've been
> involved in generally reach some consensus by testing RC labeled bun
Chip,
I talked to Edison about this yesterday and he said that you guys talked
yesterday and you needed to download a new devCoud image to perform the test
procedure instead of using the old one? That's what I meant by using the new
devCloud image.
Kelven's tested from his mac and says othe
> -Original Message-
> From: Edison Su [mailto:edison...@citrix.com]
> Sent: Friday, October 05, 2012 10:58 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: [VOTE] how to upgrade CloudStack from 3.0.x to 4.0
>
> Refer to bug CLOUDSTACK-248, the root cause is :
> we change cloud-ag
Chip,
Any luck with testing these two bugs? Thanks.
--Alex
> -Original Message-
> From: Alex Huang [mailto:alex.hu...@citrix.com]
> Sent: Friday, October 05, 2012 9:51 AM
> To: cloudstack-dev@incubator.apache.org
> Cc: Chip Childers (chip.child...@sungard.com)
> Sub
d.com]
> Sent: Friday, October 05, 2012 3:47 PM
> To: Alex Huang
> Cc: cloudstack-dev@incubator.apache.org
> Subject: Re: bugs 259 and 260
>
> Edison mentioned on IRC that he thought he knew the issue. I didn't get the
> details.
>
> I've tried clearing my l
e time to track down committers
for those reviews. We cleaned those up today.
Big thanks to Alena who helped out on most of these.
--Alex
> -Original Message-
> From: Alex Huang
> Sent: Friday, October 05, 2012 7:57 AM
> To: cloudstack-dev@incubator.apache.org
> Cc: Ed
The current status is as follows:
The bug board has been cleared.
The reviews needed in 4 have been committed.
We are going to be testing over the weekend, particularly the update cases.
We're hoping the release candidate will be cut by Sunday night.
Will keep everyone posted.
--Alex
topcloud
> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Saturday, October 06, 2012 4:26 PM
> To:
> Subject: Re: IRC nicks
>
> chipc
>
> On Oct 6, 2012, at 5:35 PM, Noah Slater wrote:
>
> > Hey,
> >
> > Can all committers (including PMC/mentors) o
Rohit,
I checked in a fix for that but already. Probably the same as yours.
--Alex
From: Rohit Yadav [mailto:nore...@reviews.apache.org] On Behalf Of Rohit Yadav
Sent: Saturday, October 06, 2012 11:45 PM
To: David Nalley; Edison Su; Alex Huang
Cc: cloudstack; Rohit Yadav
Subject: Re: Review
t 5, 2012 at 5:47 AM, Wido den Hollander
> wrote:
> > > On 10/05/2012 05:58 AM, Chip Childers wrote:
> > >>
> > >> Absolutely. First thing in the morning.
> > >>
> > >
> > > I just bumped the Debian version to 4.0 beta 6:
>
> From my side, it's resolved and no more work is needed unless QA reopens it.
> There are 7 patches which are in 4.0 and no on master, as they are 4.0
> specific
> and Hugo suggested on IRC that since they all are fixing ant build xml files
> and
> cloud.spec they may not be needed to be pull on
>
> CLOUDSTACK-267: Migration of VM in KVM host is not happening because...
> Edison, you marked this bug as closed and that it was fixed in
> c8afd816965786441e4b6f855b141d7515f15f6a. Was this patch applied to the
> 4.0 branch? If so, should we update the fix version to be 4.0.0?
> If not, shou
Definitely retest with the new build. That's the problem we've been tracking
down the whole weekend.
--Alex
> -Original Message-
> From: sebgoa [mailto:run...@gmail.com]
> Sent: Monday, October 08, 2012 9:37 AM
> To: cloudstack
> Subject: aws testing using 4.0 test procedure
>
> Hi,
>
I've talked with Frank and he will remove the limits change.
--Alex
> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Monday, October 08, 2012 4:43 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [ASF40][QA] AWSAPI packging remarks
>
> O
> -Original Message-
> From: David Nalley [mailto:da...@gnsa.us]
> Sent: Monday, October 08, 2012 6:07 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [ASF40][QA] AWSAPI packging remarks
>
> On Mon, Oct 8, 2012 at 7:43 PM, Chip Childers
> wrote:
> > On Mon, Oct 8, 2012 at 7:
Kelven,
AFAIK, every feature in CloudPlatform has been put into 4.0, except for
auto-scaling. Does this mean 4.0 supports distributed vSwitch?
--Alex
> -Original Message-
> From: Kelven Yang [mailto:kelven.y...@citrix.com]
> Sent: Monday, October 08, 2012 7:36 PM
> To: cloudstack-dev@i
> Two things:
>
> How about Wido's remark about us not packaging for Debian?
That one is a new one. Wido said he will work on it.
However, I think the last few days has shown that awsapi is not ready to be
released for 4.0. It's obviously the last thing being tested and it still has
probl
+1 We decided on a time-based release. Since OVM did not make it in time to
make it a functional product, it should not make it.
I think this vote should have a better description. It is more a vote to say
OVM did not make the 4.0 release. It is not to drop OVM. The source code is
still th
-1
devCloud also functions as an easy way to test out CloudStack. That can only
be done with the all-in-one concept.
I like the idea of having management server on my laptop and use devCloud only
as the hypervisor but both format have to exist.
--Alex
> -Original Message-
> From: E
Pluggable models for core and api have been in since 2.2. Pluggable UI is
being planned.
--Alex
> -Original Message-
> From: Wido den Hollander [mailto:w...@widodh.nl]
> Sent: Friday, October 19, 2012 5:32 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: FS for host updates n
There have been open source usage of CloudStack before CloudStack was
contributed to Apache. While CloudStack was contributed in April of this year,
it's been open source for some time before that. We've seen some variants but
have not kept track of every open source deployment.
However, CPBM
Roland,
Apache 4.0 is actually a rollup of all of the features implemented by Citrix in
the 3.x branches + all changes to make it apache license compatible + new work
that breaks out the plugins + changes to the build system. So the current
Apache 4.0 release will bring actually bring CloudSt
Dave,
Do you have any details on progress on this?
--Alex
> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Tuesday, October 23, 2012 4:23 AM
> To:
> Subject: Re: [ASFCS40] Redirect cloudstack.org and docs.cloudstack.org as
> part of the 4.0 "release"
be wrapped by isDebugEnabled() checks to prevent
unnecessary string concatenation
- Not sure if there's any point in printing a debug log that says serializing
to json. Please justify.
- The log for closing db connection should come before the actual close.
- Alex Huang
On Oct. 24, 2012,
> On Oct. 24, 2012, 6:59 p.m., Alex Huang wrote:
> > The following changes need to be made.
> >
> > - All debug() calls should be wrapped by isDebugEnabled() checks to prevent
> > unnecessary string concatenation
> > - Not sure if there's any p
not tab.
- Alex Huang
On Oct. 25, 2012, 12:02 a.m., Min Chen wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apach
symmetry
with the txn open and then transit to user managed.
- Alex Huang
On Oct. 25, 2012, 12:02 a.m., Min Chen wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apach
Is there any standard practices that we can follow? It sounds like a great
idea but how do you keep information fresh and don't end up with broken links
as things move around (or move completely to another site like CloudStack wiki
has)?
--Alex
> -Original Message-
> From: Chip Childe
+1 on the IF check. The condition should always be checked before performing
the actual alteration.
As for the stored procedure, this is meant for writing unit test to test just
that statement? For testing if one statement is correct, I usually just run it
inside mysql or workbench. I think
> On Oct. 25, 2012, 2:59 a.m., Alex Huang wrote:
> > Nicely written unit test. You should add one to test what happens when the
> > transaction is reused. For every bug we find, we should write a unit test
> > for it. Also document in the unit test what you are
. The whole
point is to avoid expensive gc on String objects so if the string construction
is outside of the check, then it's useless.
license should be added to all the new test files.
Nicely done. I'll commit once the above two are addressed.
- Alex Huang
On Oct. 25, 2012, 6:26
bug.
- Alex Huang
On Oct. 25, 2012, 7:14 p.m., Min Chen wrote:
>
> ---
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apach
Ha ha. That was my first thought as well!
+1 on the monkey.
--Alex
> -Original Message-
> From: Marcus Sorensen [mailto:shadow...@gmail.com]
> Sent: Friday, October 26, 2012 9:12 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [DISCUSS] Adopt the Monkey?
>
> Is it bad that
ep Vittal
> Sent: Friday, October 26, 2012 9:53 AM
> To: CloudStack DeveloperList; Alex Huang
> Subject: Re: Is there anyway to block root admin APIs on WAF?
>
> This sounds like an excellent idea. Could you raise an enhancement request.
> I do remember someone talking about moving al
Dave and Joe,
If I'm in the apache wiki and perform a search via the search box on the top
right corner, it actually searches the entire apache confluence. Is there any
way to limit that search to just cloudstack?
Thanks.
--Alex
v@incubator.apache.org
> Cc: David Nalley; Joe Brockmeier
> Subject: Re: Searching in Apache wiki
>
> You have to use advanced search, and select the CloudStack space.
>
> -chip
>
> On Fri, Oct 26, 2012 at 2:47 PM, Alex Huang wrote:
> > Dave and Joe,
> >
> &
Jessica or Brian,
Can you comment on what Noah is seeing in the two links?
Thanks.
--Alex
> -Original Message-
> From: Noah Slater [mailto:nsla...@apache.org]
> Sent: Saturday, October 27, 2012 10:29 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [VOTE] Apache Cloudstack
Is having steps to download waf enough?
--Alex
> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Monday, October 29, 2012 8:32 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: [ASFCS40] Could we easily remove WAF from 4.0 somehow?
>
> Hi all,
>
> However, I think that this discussion raises the issue of removing waf again.
> Hopefully that work is going well, and we can expect to remove waf from the
> project entirely for the next release. I'm not sure how we will handle a bug
> fix release though... Thoughts?
>
I think if we are at a
Meghna,
Can you give an example of which call you're talking about and point out the
specific line of code you're having problem with?
Thanks.
--Alex
> -Original Message-
> From: Meghna Kale [mailto:meghna.k...@sungard.com]
> Sent: Monday, October 29, 2012 9:51 AM
> To: cloudstack-dev@
age-
> From: Meghna Kale [mailto:meghna.k...@sungard.com]
> Sent: Monday, October 29, 2012 12:23 PM
> To: Chiradeep Vittal
> Cc: cloudstack-dev@incubator.apache.org; Alex Huang
> Subject: RE: need help for test cases of api/commands
>
> I was trying with mocks.
>
&
+1 Sorry for being late because I've been tied up in other stuff and because
the instruction doesn't work on windows (yeah yeah windows wmindows). But I
finally gave it a quick test and it worked.
--Alex
> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Se
Matthew,
Are you looking to write unit tests for which set of APIs? Is it the
management server APIs, plugin APIs, or resource APIs?
Yup. Hugo's path is the correct one.
--Alex
> -Original Message-
> From: Hugo Trippaers [mailto:htrippa...@schubergphilis.com]
> Sent: Tuesday, October
Message-
> From: Noah Slater [mailto:nsla...@apache.org]
> Sent: Monday, October 29, 2012 7:04 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: [VOTE] Apache Cloudstack 4.0.0-incubating Release, third round
>
> Alex, do you know enough to fix those instructions?
>
>
esday, October 30, 2012 6:41 AM
> To: cloudstack-dev@incubator.apache.org; Alex Huang
> Subject: New PPMC Member: Alex Huang
>
> The Podling Project Management Committee (PPMC) for Apache CloudStack
> has asked Alex to become a member of the PPMC and we are pleased to
> announce t
Finally! Hopefully it gets easier from here!
Thanks for the incredible work and time you put into this Chip!
--Alex
> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Friday, November 02, 2012 12:11 PM
> To: cloudstack-dev@incubator.apache.org
> Subj
Marcus,
You can add a plugin for something like that. I'm sure you'll need to make
some adjustments in cloudstack code to handle this (particularly specifying the
storage pool the vm should be on) but we should largely keep the logic outside
of cloudstack code and put it in a template.
- The
- CountOnly should have it's own API. Putting it as a parameter to the call
and have it completely change the semantics of the response doesn't make sense
to me.
- If we return a count with the list, I agree with what George suggested. The
count should actually be in the header. It's more met
Me2
-Original Message-
From: Kelceydamage@bbits [mailto:kel...@bbits.ca]
Sent: Wednesday, November 07, 2012 9:42 AM
To: cloudstack-dev@incubator.apache.org
Cc: CloudStack Developers
Subject: Re: Today's IRC meeting
I was under the assumption the meeting was at 10am PST
Sent from my iPho
We should remember that we didn't have Jira setup until very late into the 4.0
release. There were a lot of things that leaked through because of that.
We should make use of the Jira functionalities.
These steps can be performed by everyone.
- A bug is filed in issues.apache.org/cloudstack. Th
The site looks nice. One comment I have and it's the same I had on
cloudstack-meeting irc.
We should keep a top-level link that points the user to the features and
progress of the next release. We had plenty of questions during 4.0 from users
about the progress of the release and the features
+1 semver
+1 on 4 months as the timing. My opinion is that the more releases we'll do,
the better we'll get at it.
--Alex
-Original Message-
From: Marcus Sorensen [mailto:shadow...@gmail.com]
Sent: Tuesday, November 06, 2012 11:25 PM
To: cloudstack-dev@incubator.apache.org
Subject: R
.
--Alex
> -Original Message-
> From: Alex Huang [mailto:alex.hu...@citrix.com]
> Sent: Wednesday, November 07, 2012 3:25 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: [DISCUSS] Feedback on site redesign
>
> The site looks nice. One comment I have and it&#
I sent out an email a couple of months ago about the need to refactor
CloudStack into small pieces. At the time, the overall sentiment was the
community is heavily invested in releasing 4.0 and this should be brought up
post 4.0. Now that 4.0 has been released, I like to bring this up again.
I have updated the page to include a pdf for those who don't have power point.
--Alex
> -Original Message-
> From: Alex Huang [mailto:alex.hu...@citrix.com]
> Sent: Friday, November 09, 2012 10:12 AM
> To: cloudstack-dev@incubator.apache.org
> Subject: [RFC] Refactori
er structure in it, I sent a patch for
> >> review 7776 on request board, once it is reviewed and committed the
> >> structure will be set and all the units already written are in the new
> >> structure.
> >>
> >> Mani
> >>
> &g
>
> 1 - Do we want tests to run each time mvn install is run?
No. I like to have choices.
>
> 2 - Do we want to get stricter about what exactly is considered to be
> a unit test (vs an automated test that may or may not be based on the
> junit framework)?
I actually consider db tests to be un
I like to revive this topic. I punted this in 4.0 because there's just no
infrastructure in place and there were a lot of users asking for a refresh of
the code line.
I like to propose that starting now all commits must have unit tests and
commits can be rejected on the bases that it doesnot
> >> 2 - Do we want to get stricter about what exactly is considered to be
> >> a unit test (vs an automated test that may or may not be based on the
> >> junit framework)?
> >
> > I actually consider db tests to be unit tests as long as the db is setup and
> cleaned up by the unit test itself.
>
> -Original Message-
> From: Alex Huang [mailto:alex.hu...@citrix.com]
> Sent: Friday, November 09, 2012 12:16 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: [DISCUSS] All checkins must include unit testing
>
> I like to revive this topic. I punted this i
> -Original Message-
> From: Alex Huang [mailto:alex.hu...@citrix.com]
> Sent: Friday, November 09, 2012 12:19 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: RE: Unit tests
>
> > >> 2 - Do we want to get stricter about what exactly is considered t
> -Original Message-
> From: Rohit Yadav
> Sent: Wednesday, November 07, 2012 9:23 PM
> To: cloudstack-dev@incubator.apache.org
> Cc: Alex Huang; chip.child...@sungard.com Childers
> Subject: Re: [DISCUSS] releases going forward
>
>
> On 08-Nov-2012, at
, Nov 9, 2012 at 3:56 PM, Alex Huang wrote:
> >
> >
> >> -Original Message-
> >> From: Rohit Yadav
> >> Sent: Wednesday, November 07, 2012 9:23 PM
> >> To: cloudstack-dev@incubator.apache.org
> >> Cc: Alex Huang; chip.child...@sungard.
1 - 100 of 918 matches
Mail list logo
