I went thru the tickets most of them look like minor or corner cases.
https://issues.apache.org/jira/browse/CLOUDSTACK-6270 - VMWare issue
https://issues.apache.org/jira/browse/CLOUDSTACK-4879 - Doc ticket not required
for RC’s
https://issues.apache.org/jira/browse/CLOUDSTACK-6307 - Vsphere
https
Thanks for taking care of 4.4 Daan.
I triaged for 4.3 and moved some of them to Future and a few to 4.5
I marked 4.4.2 and 4.3.2 as released in Jira.
Here is what I followed
1. all sub-tasks or marker tasks moved to Future
2. moved some of the doc issues to Future and a few to 4.5
3. resolved bu
Don't spend to much time. if there is a 4.3.3 mark the 4.3 ones as
such. I'll look at the 4.4 ones.
On Wed, Feb 18, 2015 at 9:58 AM, Rajani Karuturi wrote:
> No Daan. I haven't triaged yet. I tried to mark them as released in jira
> and it showed me the open issues.
> I will try git grep for any
No Daan. I haven't triaged yet. I tried to mark them as released in jira
and it showed me the open issues.
I will try git grep for any commits in 4.3, 4.4 or 4.5. But, it would be
difficult to co-relate unless the commits have bug ids.
4.3.2 has 158 issues[1] and 4.4.2 has 2 open issues[2]
[1] ht
Rajani, did you triage them? Maybe some of those are fixed in commits
after the release. In that case they can be marked with all of 4.3.3,
4.4.3 and 4.5.0. Otherwise we can still decide to put them on higher
versions or on 'future'
On Wed, Feb 18, 2015 at 7:26 AM, Abhinandan Prateek
wrote:
> Sin
Since we are still voting and fixing 4.5 RC, these should be moved to 4.5.
If these are not fixed now then they can be moved to 4.6 after 4.5 is released.
-abhi
> On 18-Feb-2015, at 12:13 pm, Rajani Karuturi wrote:
>
> Hi all,
> There are some open issues on 4.4.2 on 4.3.2.
> Since they are alre
Hi all,
There are some open issues on 4.4.2 on 4.3.2.
Since they are already released, what should be the target release for
these issues?
Should I move them to 4.6 (since we dont have 4.3.3 or 4.4.3 planned)?
Thanks,
~Rajani
