On Sat, Aug 1, 2015 at 4:37 AM, Raja Pullela wrote:
> My 2 years with this project, I don't remember there was a time when few
> folks have created a bunch of blockers with a malicious intent of blocking a
> release? We should approach to this as people create defects with a "good"
> intent.
Thanks Somesh, It is a usefull link.
Now if for instance an installation can not be used because no initial
zane can be created, this would be a showstopper. But if a release
does not have certain obscure features (even as regression) we have a
discussion. Not whether we should fix it. I am totall
Github user pdion891 commented on the pull request:
https://github.com/apache/cloudstack/pull/623#issuecomment-126909038
@karuturi , I haven't found a way to specify the release number at the
```docker build```. If there is a way I would use it so Dockerfiles would be
same across bran
Github user asfgit closed the pull request at:
https://github.com/apache/cloudstack/pull/623
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Hi Erik,
Do you think we could repurpose your slave, as docker build slave? do you
mind if we had the host in the Chef-Server, I'll create you an account, I
setup some roles for jenkins slaves, all cookbooks are in:
https://github.com/CloudStack-extras/ci-chefrepo
Docker would need to be updated
I don't mind at all :-)
Erik
Den lørdag 1. august 2015 skrev Pierre-Luc Dion
følgende:
> Hi Erik,
> Do you think we could repurpose your slave, as docker build slave? do you
> mind if we had the host in the Chef-Server, I'll create you an account, I
> setup some roles for jenkins slaves, all c
Thanks for that.
This pleases my inner grammar nazi. :)
Lucian
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
- Original Message -
> From: "Mike Tutkowski"
> To: dev@cloudstack.apache.org
> Sent: Friday, 31 July, 2015 06:26:32
> Subject: Small grammatical point
