Well we chose to keep the feature freeze while we had 4.3 still in progress. I
don't think we want to hold off 4.3 because of 4.4. It needs to go out
Animesh
From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
Sent: Wednesday, March 12, 2014 10:25 AM
To: dev@cloudstack.apache.o
: Daan Hoogland [mailto:dhoogl...@schubergphilis.com]
> Sent: Wednesday, March 12, 2014 9:08 AM
> To: dev@cloudstack.apache.org
> Subject: [4.3] CLOUDSTACK cidr list length
>
> Animesh,
>
> This is one of two production issues that we have. I will be sending you the
> oth
6 AM
> To: dev
> Subject: Re: [4.3] CLOUDSTACK cidr list length
>
> H Animesh,
>
> tyhe other one is for 6232 and I cherrypicked it without recompile, hence the
> tabs to spaces commit.
>
> I am still in discussion with Alena about it. She thinks it is incomplete. It
&
Cancelling this VOTE because of issues called out by Daan and Paul and off to
building another RC
From: Animesh Chaturvedi
Sent: Monday, March 10, 2014 8:00 PM
To: dev@cloudstack.apache.org
Subject: [VOTE] Apache CloudStack 4.3.0 (seventh round)
Hi All,
I've created a 4.3.0 release,
> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: Wednesday, March 12, 2014 2:52 PM
> To: dev
> Cc: Hugo Trippaers; Animesh Chaturvedi
> Subject: Re: [VOTE] Apache CloudStack 4.3.0 (seventh round)
>
> If we produce a new f
> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: Wednesday, March 12, 2014 11:45 AM
> To: dev; Animesh Chaturvedi
> Subject: [4.3][CLOUDSTACK-6232]isolated network can no longer reserve ip
> range
>
> Animesh, I really feel
why)
Thanks
Animesh
Yes that is correct. 1.7 was changes in master / 4.4. I will revert the changes
for 4.3 release test procedure
> -Original Message-
> From: Amogh Vasekar [mailto:amogh.vase...@citrix.com]
> Sent: Wednesday, March 12, 2014 1:41 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [WIKI] Relea
The change has been reverted.
> -Original Message-
> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> Sent: Wednesday, March 12, 2014 7:32 PM
> To: dev@cloudstack.apache.org
> Subject: RE: [WIKI] Release test procedure contains wrong version of Java
>
> -Original Message-
> From: Nux! [mailto:n...@li.nux.ro]
> Sent: Thursday, March 13, 2014 12:41 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [VOTE] Apache CloudStack 4.3.0 (eighth round)
>
> On 13.03.2014 18:58, Nux! wrote:
> > On 13.03.2014 00:2
> -Original Message-
> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> Sent: Thursday, March 13, 2014 1:25 PM
> To: dev@cloudstack.apache.org
> Subject: RE: [VOTE] Apache CloudStack 4.3.0 (eighth round)
>
>
>
> > -Original Message
Hugo
Folks in USA will still have their day shining on 3/14. Can you cut it after
the day in USA is over in PST time
Animesh
> -Original Message-
> From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers
> Sent: Tuesday, March 11, 2014 8:28 AM
and put it in 4.3 as many
> of those changes are intended for 4.3.1 and not 4.3.
[Animesh] Yes that is correct. I was pulling in commits that I was asked to
cherry-pick from 4.3-forward and the one that I thought were important. There
were some that I had not picked up and had followed up wit
udstack.git;a=blob_plain;f=scripts/vm/net
> > wo
> >
> rk/security_group.py;h=0ac8b74a872d46b5def69be8df35e4fc49eb52b3;hb=0
> > 898a264a5463b85c4cab3033f9c3161c5ef83f8
>
> But the code is not for 4.3, right?
> I want to figure out, why 4.3 security group is broken.
>
If I build another RC I will pick it up
From: Alena Prokharchyk
Sent: Friday, March 14, 2014 12:43 PM
To: Animesh Chaturvedi
Cc: dev@cloudstack.apache.org
Subject: Re: cherrypick to 4.3
Animesh, one more commit for the same bug needs to be cherry-picked:
94817c1b4b89cfa69f2db50a7060dcb7d7c39dbb
(/, "") ;print $3}'""" % brfw).strip()
>
> In commit: 052bff15c6603877e7a0767993eb4675e9bd9ca8
>
> The code should be
> +refs = execute("""iptables -n -L " + %s + " | awk
> + '/%s(.*)references/ {gsub(/\(/, &quo
> -Original Message-
> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> Sent: Friday, March 14, 2014 2:28 PM
> To: dev@cloudstack.apache.org
> Subject: RE: [VOTE] Apache CloudStack 4.3.0 (eighth round)
>
>
>
> > -Original Me
forward
> branch.
> I do see the rule coming on the kvm host:
>
> -A FORWARD -o cloudbr0 -m physdev --physdev-is-bridged -j BF-cloudbr0 -A
> FORWARD -i cloudbr0 -m physdev --physdev-is-bridged -j BF-cloudbr0 -A
> FORWARD -o cloudbr0 -j DROP -A FORWARD -i cloudbr0 -j DROP
>
&g
th round)
>
> Has anyone else seen below behavior with 4.3.0 RC 8?
>
> - with 32 bit system VM, the secondary storage is reported as 0/0 (this is
> at
> the agent level, not a GUI or manager issue)
>
> - with 64 bit system VM, the secondary storage is reported OK.
&
issues.apache.org/jira/browse/CLOUDSTACK-6156 resolved.
[Animesh] I had responded earlier we do not see the issue with Jenkins build so
if someone needs they can get it from the Jenkins, I don't consider it blocker
and nobody seems to pick it up. We can track it for maintenance release on 4.3
&
d been intending to mail previous committers on the
> subdir.
>
> Prachi/Likitha - any comments on https://reviews.apache.org/r/18392/
> would be appreciated.
[Animesh] Removing rampart dependency will need testing AWSAPI again, I am
inclined to track this for 4.3 maintenance or 4.4
Edison
Thanks for taking care of this issue. Nux can you try with this fix and I will
go off building RC
> -Original Message-
> From: Edison Su [mailto:edison...@citrix.com]
> Sent: Monday, March 17, 2014 2:52 PM
> To: dev@cloudstack.apache.org
> Subject: RE: [VOTE] Apache CloudStack 4.3
Cancelling this VOTE too because of Nux's finding of KVM SecurityGroup is
broken.
Thanks
Animesh
From: Animesh Chaturvedi
Sent: Wednesday, March 12, 2014 5:27 PM
To: dev@cloudstack.apache.org
Subject: [VOTE] Apache CloudStack 4.3.0 (eighth round)
Hi All,
I've created a 4.3.0 rel
> -Original Message-
> From: Nux! [mailto:n...@li.nux.ro]
> Sent: Monday, March 17, 2014 3:57 PM
> To: dev@cloudstack.apache.org
> Subject: RE: [VOTE] Apache CloudStack 4.3.0 (eighth round)
>
> On 17.03.2014 22:39, Animesh Chaturvedi wrote:
> > Edison
> &
> -Original Message-
> From: Nux! [mailto:n...@li.nux.ro]
> Sent: Tuesday, March 18, 2014 7:04 AM
> To: Animesh Chaturvedi
> Cc: dev@cloudstack.apache.org; Edison Su
> Subject: RE: [VOTE] Apache CloudStack 4.3.0 (eighth round)
>
> On 17.03.2014 22:39,
why)
Thanks
Animesh
ay be wrong) The role of the release manager starts only during
> the RC creation phase asking for votes(again I maybe wrong).
[Animesh] Rajani releases are actually planned well ahead. Please check out the
Release page for 4.3
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Cloudstack+
Daan/ Hugo
We need to update the wiki release page for 4.4 and also setup the JIRA
dashboard similar to what I did for 4.2 and 4.3. Let me know if you have
questions on how it was done for 4.3
Thanks
Animesh
> -Original Message-
> From: Sudha Ponnaganti [mailto:sudha.p
>> Thanks in advance.
> >>>
> >>> Cheers,
> >>> Wilder
> >>>
> >>> -Original Message-
> >>> From: ilya musayev [mailto:ilya.mailing.li...@gmail.com]
> >>> Sent: Tuesday, March 18, 2014 9:11 PM
> >>&g
> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: Thursday, March 20, 2014 10:25 AM
> To: dev
> Cc: Amogh Vasekar; Suresh Sadhu
> Subject: Re: [VOTE] Apache CloudStack 4.3.0 (ninth round)
>
> On Thu, Mar 20, 2014 at 6:21 PM, Ani
indeed a diff between 4.2.1 and 4.3RC9
[Animesh] Ofcourse there is that's the change in this commit
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=commit;h=ec4db7bbff60f0be96e39f51c0f17b12e0de440c
>
> On Thu, Mar 20, 2014 at 5:32 PM, Nux! wrote:
> > On 20.03.2014 16:2
last
> > round.
> >
> > > -Original Message-
> > > From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> > > Sent: Tuesday, March 18, 2014 12:06 PM
> > > To: dev@cloudstack.apache.org
> > > Subject: [VOTE] Apache CloudStac
Can you clear up browser cache and try again?
> -Original Message-
> From: Animesh Chaturvedi
> Sent: Thursday, March 20, 2014 4:54 PM
> To: dev@cloudstack.apache.org
> Cc: Jessica Wang
> Subject: RE: [VOTE] Apache CloudStack 4.3.0 (ninth round)
>
> That'
+ 1 (binding) verified the release artifacts and tested with devcloud
> -Original Message-
> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> Sent: Tuesday, March 18, 2014 12:06 PM
> To: dev@cloudstack.apache.org
> Subject: [VOTE] Apache CloudStack 4.3
The vote has *passed* with the following results (binding PMC votes indicated
with a "*" next to their name:
+1 : Animesh*, Edison*, Ilya*, Amogh, Wilder
+0 : Daan *
-1 : Tanner (The issue CLOUDSTACK-6266 could not be reproduced )
I'm going to proceed with moving the r
Sure lets track them for 4.3.1 and 4.4
Thanks
Animesh
On Mar 22, 2014, at 3:56 PM, "ilya musayev"
wrote:
> I did find some issue - but relatively minor and nothing that could not have
> been fixed via UI.
>
> I will open JIRA to address the issues.
>
> In the
Release VOTE passed we are working on formal release announcement and it should
be out soon
Animesh
> -Original Message-
> From: Andrei Mikhailovsky [mailto:and...@arhont.com]
> Sent: Monday, March 24, 2014 7:26 AM
> To: dev@cloudstack.apache.org
> Subject: release esti
ule reminder : 10 days to code freeze
>
> 4.3/4.4?
>
>
>
> -Original Message-
> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> Sent: Tuesday, November 26, 2013 9:20 PM
> To: dev@cloudstack.apache.org
> Subject: [ACS4.3] Schedule reminder
copy.
The latter is between 2 trusted IPs
- Also this should only affect SSVM template from 4.2 onwards as only wheezy is
affected
Thanks
Animesh
> -Original Message-
> From: John Kinsella [mailto:j...@stratosec.co]
> Sent: Wednesday, April 09, 2014 11:07 AM
> To: dev@cloudstac
May be this can be a quick hackathon in collab. Copying Wido and Hugo
> -Original Message-
> From: Abhinandan Prateek [mailto:abhinandan.prat...@citrix.com]
> Sent: Thursday, April 10, 2014 9:18 AM
> To: dev@cloudstack.apache.org
> Subject: Re: 4.3 system vm template job failing in jenkins
Folks
FYI I will be out on PTO for 2 weeks starting 4/17
Thanks
Animesh
ogland [mailto:daan.hoogl...@gmail.com]
> Sent: Monday, May 05, 2014 11:53 AM
> To: Animesh Chaturvedi
> Cc: dev
> Subject: Re: 4.4 release-notes
>
> Animesh,
>
> Can you (give me rights to) add these filters to the release dashboard?
>
> On Fri, May 2, 2014 at 4:43 AM, Pierr
I will put a slot in my calendar for triaging bugs daily from now on.
Animesh
> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: Wednesday, May 07, 2014 1:05 AM
> To: dev
> Subject: [ACS44] critical issue assesment
>
> Friend an
e run into
challenges in implementing those rules like toolset not ready or infra then we
would have to fix those.
Animesh
> -Original Message-
> From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers
> Sent: Wednesday, May 14, 2014 12:32 AM
> To: dev@cloudstac
.
You can also do bulk edit for open tickets and ask for updates, I will also
nudge a few folks here.
thanks
Animesh
> -Original Message-
> From: Sudha Ponnaganti [mailto:sudha.ponnaga...@citrix.com]
> Sent: Monday, May 26, 2014 9:21 AM
> To: dev@cloudstack.apache.org
> Subj
> -Original Message-
> From: sebgoa [mailto:run...@gmail.com]
> Sent: Tuesday, May 20, 2014 11:30 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [PROPOSAL] Using continuous integration to maintain our code
> quality...
>
>
> On May 21, 2014, at 12:40 AM,
going to be difficult to balance our development needs with
> our need to remain vendor neutral / independent.
>
> -chip
[Animesh] Chip Alex has called this out in Q&A section of [1]
[1] https://cwiki.apache.org/confluence/display/CLOUDSTACK/Development+Process
Hugo
Can you share the latest results? How can I get access to the reports?
Animesh
> -Original Message-
> From: Hugo Trippaers [mailto:trip...@gmail.com]
> Sent: Friday, November 29, 2013 7:58 AM
> To: dev@cloudstack.apache.org
> Subject: Fwd: New Defects reported by Co
ate to "In Progress". It is a big
reassurance to RM that the issue is being worked upon and RM can go nudge other
open items.
Thanks
Animesh
Congrats Saksham
> -Original Message-
> From: sebgoa [mailto:run...@gmail.com]
> Sent: Wednesday, May 28, 2014 11:48 PM
> To: dev@cloudstack.apache.org
> Subject: [ANNOUNCE] Saksham Srivastava as committer
>
> The Project Management Committee (PMC) for Apache CloudStack has asked
> Saksha
I will merge 4.3-forward into 4.3 later today.
Animesh
> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: Saturday, May 31, 2014 1:38 PM
> To: dev
> Subject: [DISCUSS] old forward branches
>
> The older forward branches are still he
Rajani
Thanks for bringing this up, I looked at the analysis settings and I think the
pattern to exclude aws code should have a leading /. I have fixed it and lets
check it on the next run. We should see a significant bump up in defect
density. Good job in noticing this.
Thanks
Animesh
While we should wait for the next run for actual results but I am expecting the
defect density as reported by Coverity to drop down from 6.4 to about 3.4 after
excluding AWSAPI generated code.
Animesh
> -Original Message-
> From: Animesh Chaturvedi [mailto:animesh.c
when i need to backport/cherry-pick a patch?
> >
> > Thanks
> > ilya
>
> Ilya, imho those -forward branches should not exist, they create a mess.
> If you have something to patch for the 4.3 series, just patch it in the 4.3
> branch.
> 4.3.0, 4.3.1 etc are tags in t
> > [Animesh] Edison had merged 4.3-forward into 4.3 yesterday and I
> > deleted 4.3-forward branch this morning
> >
>
> So was there a lot of bug fixes that went in 4.3 during the merge ? if yes we
> might want to release a 4.3.1 ?
[Animesh] yes there were around 17
. Additional details on fixes are
available in JIRA. Updated wiki with steps will be published shortly.
[1] https://issues.apache.org/jira/browse/CLOUDSTACK-6499
[2] https://issues.apache.org/jira/browse/CLOUDSTACK-6599
[3] https://issues.apache.org/jira/browse/CLOUDSTACK-6824
Thanks
Animesh
:
> > Right - we need to decide as a community what a forward branch really
> means.
> >
> > On Monday, June 9, 2014, Koushik Das wrote:
> >
>
> So a bit of background reading:
> http://markmail.org/message/aux2yjxpudotu7qu
>
> This is when we started wi
Folks please check on the issues reported.
> -Original Message-
> From: scan-ad...@coverity.com [mailto:scan-ad...@coverity.com]
> Sent: Monday, June 09, 2014 7:37 PM
> Subject: New Defects reported by Coverity Scan for cloudstack
>
>
> Hi,
>
>
> Please find the latest report on new de
thing that I used to do was setup a JIRA query for all the open
Blocker and critical issues that have not been updated in last 7 day and do a
BULK EDIT and ask for status or follow up.
Thanks
Animesh
> -Original Message-
> From: Mike Tutkowski [mailto:mike.tutkow...@solidfi
> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: Thursday, June 12, 2014 12:27 AM
> To: dev
> Subject: Re: [DISCUSS] Release 4.4
>
> Why would we need that in a mail to dev@ Animesh? It is on the release
> dashboard.
[Animes
gt; > +1
> >
> > I feel clue less for doing the release-notes about what new features
> > will be in 4.4, this would be a good time to poke around.
[Animesh] Every release has a filter for new features and improvements. Here is
one for 4.4 that I had setup a while back
> -Original Message-
> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> Sent: Thursday, June 12, 2014 2:04 PM
> To: dev@cloudstack.apache.org
> Subject: RE: [PROPOSAL] irc meeting for release 4.4
>
>
>
> > -Original Message
84 is a bug number to call RC ready unless the issues are not really critical
> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: Monday, June 16, 2014 7:11 AM
> To: dev
> Subject: [ACS44] are we RC-ready?
>
> s far as I can tell the only remaining blocker
One thought is if a feature is not nearing test completion then considering
pushing it out to next release and move the corresponding bugs as well out of
4.4
Thanks
Animesh
> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: Monday, June 16, 2
>
> 1. move forward feature freeze not on the coming but on the next release.
[Animesh] Daan to be clear you are proposing to keep the feature freeze date at
Aug 19th
> 2. set feature proposal dealine for the coming release on 19th of June
>
> flames? other thoughts?
> Da
I saw you mentioning mid august as well so there is some confusion
Animesh
> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: Wednesday, June 25, 2014 1:52 PM
> To: dev
> Subject: Re: [ACS45][ACS50][PROPOSAL] move forward feature freeze
&g
In response to Brocade I see your response
"feature should be done (in it's branch) by 19th july. merging and fixing
issues may take to mid august" that essentially means feature freeze (cutting
the branch) by mid august
Animesh
> -Original Message-----
> Fro
Congrats Santhosh
> -Original Message-
> From: Alex Huang [mailto:alex.hu...@citrix.com]
> Sent: Monday, June 30, 2014 9:25 AM
> To: dev@cloudstack.apache.org
> Subject: [ANNOUNCE] Santhosh Edukulla as a committer...
>
> Hi All,
>
> The Project Management Committee (PMC) for Apache Cloud
Daan
We have been following the convention for Release VOTE threads like [1] as
example.
[1] http://markmail.org/message/ksyv4gftcsjc4pma
Thanks
Animesh
> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: Monday, June 30, 2014 2:23 AM
Daan
Which wiki are you referring to. I am looking at this one
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Release+Procedure which
was setup by Chip and we have followed all along.
Animesh
> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
Ok so we are good. Looking forward to VOTE thread
> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: Tuesday, July 01, 2014 12:56 PM
> To: dev
> Subject: Re: [ACS4.4] RC1
>
> thats the one,
>
> On Tue, Jul 1, 2014 at 8:16 PM,
Hugo
My understanding is only binding votes are counted. Non-binding votes are
informational
> -Original Message-
> From: Trippie [mailto:trip...@gmail.com] On Behalf Of Hugo Trippaers
> Sent: Wednesday, July 02, 2014 11:50 PM
> To: dev@cloudstack.apache.org
> Subject: Re: [VOTE] Apache
Yes that’s what we did for 4.3. Merge 4.4-forward into 4.4
> -Original Message-
> From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
> Sent: Thursday, July 24, 2014 7:48 AM
> To: dev@cloudstack.apache.org
> Subject: Re: [PROPOSAL]remove 4.4-forward
>
> Yep...what Wei said. :)
>
>
That's what we want to have a 4.4-forward for 4.4. future release. It's
superset of current 4.4 branch.
Well, probably result in a force-overwrite. But I guess how we did it in 4.3?
Animesh?
--Sheng
On Mon, Jul 28, 2014 at 2:36 AM, Daan Hoogland
mailto:daan.hoogl...@gmail.com&g
gt; On Tue, Jul 29, 2014 at 5:43 AM, Animesh Chaturvedi
> wrote:
>> Yes that's how I did for 4.2 and 4.3
>>
>> Sent from my iPhone
>>
>> On Jul 28, 2014, at 6:28 PM, "Sheng Yang" wrote:
>>
>> Daan,
>>
>> 4.4-forward sh
+ Abhi
> -Original Message-
> From: Daan Hoogland [mailto:daan.hoogl...@gmail.com]
> Sent: Thursday, July 31, 2014 12:14 PM
> To: dev
> Subject: [ACS44] template upgrade code
>
> Devs,
>
> It seems there is a big problem in the 4.4 release. The templates need a new
> java version but the
he simulator.
> Assuming the tests would run quickly (< 60 minutes on travis hardware),
> we could have tests run on every commit for every branch mirrored on
> github (.I hear some of you say "yeah right."). But imho that would be an
> ideal scenario, as folks own fork could
+0
While this protects master with only commits which are merges from release
branch and keeps it clean but the issues that we have shift to develop branch.
> -Original Message-
> From: Rajani Karuturi [mailto:rajani.karut...@citrix.com]
> Sent: Thursday, July 31, 2014 3:28 AM
> To: de
r 4.5 release branch is cut we should enter
> into
> a stable master mode).
>
> -Release: from the time a release branch is cut, features are only merged by
> RM.
[Animesh] Features have to be merged into develop branch before the feature
freeze date in order to make into release
>
> (Like most of the internet...) I strongly believe using cherry picks as the
> basic
> tool for (release) branch management is one of the worst choices you can
> make.
>
> But. Please. Can. We. Just. Stop. Cherry. Picking!!! :-D [1]
>
[Animesh] Leo I don't mi
8?filter=12328007
>
> It is a disappointing 280+ list of issues with 4.4 but I think a lot of them
> can
> be marked as won't solve, future releases or resolved.
[Animesh] We should not mark them as won't solve since they are still fresh.
You can move them to 4.5. I am doing t
r 4.3.1, I guess this is a special case and not a blocker. The
> issue was reproducible when say an admin removed a template where a user may
> be trying to create a VM and was in a wizard. I'm closing as we're not
> putting this for 4.3.1 release.
>
> Nitin Me
While testing before release is needed but the component update process with
new system template as we have now takes a long time logistically.
Thanks
Animesh
> -Original Message-
> From: Sheng Yang [mailto:sh...@yasker.org]
> Sent: Tuesday, September 30, 2014 6:08 PM
> To
he latest few
> features. I'm not done with it, but hope to have something up by end of the
> weekend.
>
[Animesh] Yes we cannot delay the release branch. David, can you confirm that
the bug fixes that were committed will be there.
> --David
>
> On Thu, Oct 9, 2014
e need to revert a lot, Animesh. I don't think you can say that all
the commits since the 1st amount to bugfixes. At least they are not commented
as such. And if so, they should have gone into 4.4, not master.
On Fri, Oct 10, 2014 at 8:19 PM, Animesh Chaturvedi
mailto:animesh.chaturv.
That’s correct Mike, Daan master is also the release branch for 4.5 and as such
you are seeing issues getting fixed there.
Animesh
From: Mike Tutkowski [mailto:mike.tutkow...@solidfire.com]
Sent: Saturday, October 11, 2014 8:52 PM
To: dev@cloudstack.apache.org
Cc: Animesh Chaturvedi
Subject: Re
veral times, fix bugs in the
> release branch and merge them back in the stable source of the release (be
> it master).
[Animesh] Sebastian you have brought up a good point dependency on QA team
from Citrix is an issue for the project. This was raised in the past as well
and Alex's pro
> -Original Message-
> From: Rohit Yadav [mailto:rohit.ya...@shapeblue.com]
> Sent: Thursday, October 23, 2014 1:22 AM
> To: dev@cloudstack.apache.org
> Subject: Re: [PROPOSAL] Move to github PR only during moratorium on
> commit
>
> Hi,
>
> > On
wrote:
> > Hi,
> >
> >> On 23-Oct-2014, at 11:47 am, Animesh Chaturvedi
> wrote:
> ...
> >> The approach for fixing issues in release branch first and master later is
> not practical as we may miss out commits not made into master and future
> release
t; > Is there a way to 'force' close a review if its already submitted?
>
> Some of us can do it. I went through some of them yesterday and closed a few.
> There are many review requests on it which are too old and lack information.
> I’m not sure what to do with them.
[A
more structured.
Thanks
Animesh
> On Thu, Dec 4, 2014 at 7:24 PM, Chip Childers wrote:
> > Steve,
> >
> > (Speaking with my PMC hat on, but not as someone that has the time to
> > help with this process)
> >
> > I love the idea of moving forward with resolvi
Cool, let's roll it out before the holidays.
Folks I had called out in JIRA for New features and Improvements that were
tagged for 4.5 but still open to update the status and move out the ones that
did not make it to Future. Please take care of your issues
Animesh
> -Original
>
> *Will STEVENS*
> Lead Developer
>
> *CloudOps* *| *Cloud Solutions Experts
> 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6 w cloudops.com *|* tw
> @CloudOps_
>
> On Thu, Dec 4, 2014 at 5:17 PM, Animesh Chaturvedi <
> animesh.chaturv...@citrix.com> wro
> having said so, I propose to set a date for our first (irc/goto) meeting;
> wednesday 10 december 16:00 UTC?
[Animesh] Can we push it out by 1 hour to 17:00 UTC, the current time falls
out on my time for dropping kids to school. If it does not work for others I
can join @14:00 UTC (6
v7hyim55
>
>
>
> On Fri, Dec 5, 2014 at 6:36 PM, Animesh Chaturvedi <
> animesh.chaturv...@citrix.com> wrote:
>
> >
> >
> > > having said so, I propose to set a date for our first (irc/goto)
> > > meeting; wednesday 10 december 16:00 UTC?
>
? wait for wednesday?
> >
> > On Sat, Dec 6, 2014 at 5:46 PM, Chip Childers
> >
> > wrote:
> > > Thanks for listening to my concerns folks... and I'll be rooting
> > > for
> > those
> > > of you that are "doing" to co
le to record the meeting? Maybe we can post it so others can view
> it
> if they are not able to attend (or only become interested after the first
> couple
> meetings and wants to catch up)?
>
> Will
> On Dec 9, 2014 9:52 PM, "Animesh Chaturvedi"
> w
The meeting is on ...
> -Original Message-
> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> Sent: Tuesday, December 09, 2014 8:56 PM
> To: dev@cloudstack.apache.org
> Cc: Steve Wilson
> Subject: RE: CloudStack Quality Process
>
> Yes I am pl
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Quality+and+Process+Improvement+Initiative
> -Original Message-
> From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
> Sent: Wednesday, December 10, 2014 9:05 AM
> To: dev@cloudstack.apache.org
> Cc: Steve
che.org
> Cc: Steve Wilson
> Subject: Re: CloudStack Quality Process
>
> Thanks for sharing the notes. Sorry, I couldn't make it this time. Will
> definitely
> plan to join the next meeting.
>
> ~Rajani
>
> On Thu, Dec 11, 2014 at 1:27 AM, Animesh Chaturvedi <
&g
601 - 700 of 735 matches
Mail list logo
