subject:"More Jira tickets clean up"

Re: More Jira tickets clean up

2017-03-17 Thread Rafael Weingärtner

Thanks, Mike for the feedback.
No problem Daan ;)

Tickets closed; depending on tickets, some I marked as closed, others as
resolved. I also configured the status of some to invalid, others to
incomplete, and others as fixed and so on.



On Wed, Mar 15, 2017 at 6:38 PM, Tutkowski, Mike 
wrote:

> Hi,
>
> This one appears to have been fixed a long time ago. I marked it as Fixed
> and closed the ticket.
>
> https://issues.apache.org/jira/browse/CLOUDSTACK-1524
>
> This one is not a big deal. I marked it as Won’t Fix and closed the ticket.
>
> https://issues.apache.org/jira/browse/CLOUDSTACK-1432
>
> I went through all the listed tickets and did not see any others with me
> listed as either the Assignee or Reporter.
>
> Thanks!
> Mike
>
> On 3/8/17, 12:15 AM, "Daan Hoogland"  wrote:
>
> Good hard work again Rafael,
>
> I’ll try to find time today to browse through them.
>
> On 07/03/17 18:05, "Rafael Weingärtner" 
> wrote:
>
> Hi folks,
> Today I had gone through another batch of old Jira tickets and we
> have a
> bunch that can be closed again. The following are the ones I have
> gone
> through. Before I close any ticket I would like to check them with
> you,
> especially the ones from a category called “Seemed fixed, but I
> would like
> to hear some feedback here”. I will be waiting for your feedback
> before I
> proceed to close any ticket.
>
> - Jira tickets that have PRs and were already merged, or at least
> a commit
> hash code reference
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-9509
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-9634
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-9540
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-9635
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-9598
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-212
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-350
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-535
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-698
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-3054
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-7633
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-7405
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-8976
>
> - Jira ticket linked to a PR that is linked to a series of Jira
> tickets
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-9533 (was
> this solved?)
>
> - Seemed fixed, but I would like to hear some feedback here
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-245
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-272
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-371
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-429
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-438
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-458
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-486
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-506
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-561
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-582
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-626
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-692
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-696
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-994
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-1036
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-1306
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-5650
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-5642
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-4870 (naming
> conventions on Marvin?)
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-4759
> (thoughts here
> Daan?)
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-4523
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-4365
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-4232
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-3896
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-3477
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-3012
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-1524 (Mike
> Tutkowski,
> is this still happenings? Is it possible for you to check?)
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-1432 (Mike,
> any
> thoughts here?)
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-7379
> (title=200MB limit
> setting too low for network.throttling.rate and
> vm.network.throttling.rate;
>

Re: More Jira tickets clean up

2017-03-15 Thread Tutkowski, Mike

Hi,

This one appears to have been fixed a long time ago. I marked it as Fixed and 
closed the ticket.

https://issues.apache.org/jira/browse/CLOUDSTACK-1524

This one is not a big deal. I marked it as Won’t Fix and closed the ticket.

https://issues.apache.org/jira/browse/CLOUDSTACK-1432

I went through all the listed tickets and did not see any others with me listed 
as either the Assignee or Reporter.

Thanks!
Mike

On 3/8/17, 12:15 AM, "Daan Hoogland"  wrote:

Good hard work again Rafael,

I’ll try to find time today to browse through them.

On 07/03/17 18:05, "Rafael Weingärtner"  wrote:

Hi folks,
Today I had gone through another batch of old Jira tickets and we have a
bunch that can be closed again. The following are the ones I have gone
through. Before I close any ticket I would like to check them with you,
especially the ones from a category called “Seemed fixed, but I would 
like
to hear some feedback here”. I will be waiting for your feedback before 
I
proceed to close any ticket.

- Jira tickets that have PRs and were already merged, or at least a 
commit
hash code reference
-- https://issues.apache.org/jira/browse/CLOUDSTACK-9509
-- https://issues.apache.org/jira/browse/CLOUDSTACK-9634
-- https://issues.apache.org/jira/browse/CLOUDSTACK-9540
-- https://issues.apache.org/jira/browse/CLOUDSTACK-9635
-- https://issues.apache.org/jira/browse/CLOUDSTACK-9598
-- https://issues.apache.org/jira/browse/CLOUDSTACK-212
-- https://issues.apache.org/jira/browse/CLOUDSTACK-350
-- https://issues.apache.org/jira/browse/CLOUDSTACK-535
-- https://issues.apache.org/jira/browse/CLOUDSTACK-698
-- https://issues.apache.org/jira/browse/CLOUDSTACK-3054
-- https://issues.apache.org/jira/browse/CLOUDSTACK-7633
-- https://issues.apache.org/jira/browse/CLOUDSTACK-7405
-- https://issues.apache.org/jira/browse/CLOUDSTACK-8976

- Jira ticket linked to a PR that is linked to a series of Jira tickets
-- https://issues.apache.org/jira/browse/CLOUDSTACK-9533 (was this 
solved?)

- Seemed fixed, but I would like to hear some feedback here
-- https://issues.apache.org/jira/browse/CLOUDSTACK-245
-- https://issues.apache.org/jira/browse/CLOUDSTACK-272
-- https://issues.apache.org/jira/browse/CLOUDSTACK-371
-- https://issues.apache.org/jira/browse/CLOUDSTACK-429
-- https://issues.apache.org/jira/browse/CLOUDSTACK-438
-- https://issues.apache.org/jira/browse/CLOUDSTACK-458
-- https://issues.apache.org/jira/browse/CLOUDSTACK-486
-- https://issues.apache.org/jira/browse/CLOUDSTACK-506
-- https://issues.apache.org/jira/browse/CLOUDSTACK-561
-- https://issues.apache.org/jira/browse/CLOUDSTACK-582
-- https://issues.apache.org/jira/browse/CLOUDSTACK-626
-- https://issues.apache.org/jira/browse/CLOUDSTACK-692
-- https://issues.apache.org/jira/browse/CLOUDSTACK-696
-- https://issues.apache.org/jira/browse/CLOUDSTACK-994
-- https://issues.apache.org/jira/browse/CLOUDSTACK-1036
-- https://issues.apache.org/jira/browse/CLOUDSTACK-1306
-- https://issues.apache.org/jira/browse/CLOUDSTACK-5650
-- https://issues.apache.org/jira/browse/CLOUDSTACK-5642
-- https://issues.apache.org/jira/browse/CLOUDSTACK-4870 (naming
conventions on Marvin?)
-- https://issues.apache.org/jira/browse/CLOUDSTACK-4759 (thoughts here
Daan?)
-- https://issues.apache.org/jira/browse/CLOUDSTACK-4523
-- https://issues.apache.org/jira/browse/CLOUDSTACK-4365
-- https://issues.apache.org/jira/browse/CLOUDSTACK-4232
-- https://issues.apache.org/jira/browse/CLOUDSTACK-3896
-- https://issues.apache.org/jira/browse/CLOUDSTACK-3477
-- https://issues.apache.org/jira/browse/CLOUDSTACK-3012
-- https://issues.apache.org/jira/browse/CLOUDSTACK-1524 (Mike 
Tutkowski,
is this still happenings? Is it possible for you to check?)
-- https://issues.apache.org/jira/browse/CLOUDSTACK-1432 (Mike, any
thoughts here?)
-- https://issues.apache.org/jira/browse/CLOUDSTACK-7379 (title=200MB 
limit
setting too low for network.throttling.rate and 
vm.network.throttling.rate;
isn`t it a question for the operator/administrator to configure the 
default
value?)
-- https://issues.apache.org/jira/browse/CLOUDSTACK-7167
-- https://issues.apache.org/jira/browse/CLOUDSTACK-7142 (let's open
tickets for specific issues and not for a broad class; then, the 
management
(for us) becomes easier)
-- https://issues.apache.org/jira/browse/CLOUDSTACK-7067 (questions 
should
be directed to the

Re: More Jira tickets clean up

2017-03-15 Thread Daan Hoogland

sorry Rafael, I haven't taken the time to look at more then a few. Go
ahead, for my part

On Wed, Mar 15, 2017 at 4:24 PM, Rafael Weingärtner
 wrote:
> Folks,
> It has been a week. I am assuming that no one knows about these tickets.
>
> In the last years, our workflow has been improved greatly; most of the PRs
> I see have Jira ticket associated and everything seems to be getting better
> by the time; let’s not loose momentum. However, we still have some (a lot?)
> Jira tickets that seem to be left behind.
>
> In 48 ours I will close all of the tickets mentioned here. If I close
> something that should not have been closed, please pardon me ;).
>
> After this, I will proceed with a new batch of tickets. Hopefully, in some
> iterations of this process, we can get rid of these forgotten tickets.
>
> On Wed, Mar 8, 2017 at 2:15 AM, Daan Hoogland 
> wrote:
>
>> Good hard work again Rafael,
>>
>> I’ll try to find time today to browse through them.
>>
>> On 07/03/17 18:05, "Rafael Weingärtner" 
>> wrote:
>>
>> Hi folks,
>> Today I had gone through another batch of old Jira tickets and we have
>> a
>> bunch that can be closed again. The following are the ones I have gone
>> through. Before I close any ticket I would like to check them with you,
>> especially the ones from a category called “Seemed fixed, but I would
>> like
>> to hear some feedback here”. I will be waiting for your feedback
>> before I
>> proceed to close any ticket.
>>
>> - Jira tickets that have PRs and were already merged, or at least a
>> commit
>> hash code reference
>> -- https://issues.apache.org/jira/browse/CLOUDSTACK-9509
>> -- https://issues.apache.org/jira/browse/CLOUDSTACK-9634
>> -- https://issues.apache.org/jira/browse/CLOUDSTACK-9540
>> -- https://issues.apache.org/jira/browse/CLOUDSTACK-9635
>> -- https://issues.apache.org/jira/browse/CLOUDSTACK-9598
>> -- https://issues.apache.org/jira/browse/CLOUDSTACK-212
>> -- https://issues.apache.org/jira/browse/CLOUDSTACK-350
>> -- https://issues.apache.org/jira/browse/CLOUDSTACK-535
>> -- https://issues.apache.org/jira/browse/CLOUDSTACK-698
>> -- https://issues.apache.org/jira/browse/CLOUDSTACK-3054
>> -- https://issues.apache.org/jira/browse/CLOUDSTACK-7633
>> -- https://issues.apache.org/jira/browse/CLOUDSTACK-7405
>> -- https://issues.apache.org/jira/browse/CLOUDSTACK-8976
>>
>> - Jira ticket linked to a PR that is linked to a series of Jira tickets
>> -- https://issues.apache.org/jira/browse/CLOUDSTACK-9533 (was this
>> solved?)
>>
>> - Seemed fixed, but I would like to hear some feedback here
>> -- https://issues.apache.org/jira/browse/CLOUDSTACK-245
>> -- https://issues.apache.org/jira/browse/CLOUDSTACK-272
>> -- https://issues.apache.org/jira/browse/CLOUDSTACK-371
>> -- https://issues.apache.org/jira/browse/CLOUDSTACK-429
>> -- https://issues.apache.org/jira/browse/CLOUDSTACK-438
>> -- https://issues.apache.org/jira/browse/CLOUDSTACK-458
>> -- https://issues.apache.org/jira/browse/CLOUDSTACK-486
>> -- https://issues.apache.org/jira/browse/CLOUDSTACK-506
>> -- https://issues.apache.org/jira/browse/CLOUDSTACK-561
>> -- https://issues.apache.org/jira/browse/CLOUDSTACK-582
>> -- https://issues.apache.org/jira/browse/CLOUDSTACK-626
>> -- https://issues.apache.org/jira/browse/CLOUDSTACK-692
>> -- https://issues.apache.org/jira/browse/CLOUDSTACK-696
>> -- https://issues.apache.org/jira/browse/CLOUDSTACK-994
>> -- https://issues.apache.org/jira/browse/CLOUDSTACK-1036
>> -- https://issues.apache.org/jira/browse/CLOUDSTACK-1306
>> -- https://issues.apache.org/jira/browse/CLOUDSTACK-5650
>> -- https://issues.apache.org/jira/browse/CLOUDSTACK-5642
>> -- https://issues.apache.org/jira/browse/CLOUDSTACK-4870 (naming
>> conventions on Marvin?)
>> -- https://issues.apache.org/jira/browse/CLOUDSTACK-4759 (thoughts
>> here
>> Daan?)
>> -- https://issues.apache.org/jira/browse/CLOUDSTACK-4523
>> -- https://issues.apache.org/jira/browse/CLOUDSTACK-4365
>> -- https://issues.apache.org/jira/browse/CLOUDSTACK-4232
>> -- https://issues.apache.org/jira/browse/CLOUDSTACK-3896
>> -- https://issues.apache.org/jira/browse/CLOUDSTACK-3477
>> -- https://issues.apache.org/jira/browse/CLOUDSTACK-3012
>> -- https://issues.apache.org/jira/browse/CLOUDSTACK-1524 (Mike
>> Tutkowski,
>> is this still happenings? Is it possible for you to check?)
>> -- https://issues.apache.org/jira/browse/CLOUDSTACK-1432 (Mike, any
>> thoughts here?)
>> -- https://issues.apache.org/jira/browse/CLOUDSTACK-7379 (title=200MB
>> limit
>> setting too low for network.throttling.rate and
>> vm.network.throttling.rate;
>> isn`t it a question for the operator/administrator to configure the
>> default
>> value?)
>>

Re: More Jira tickets clean up

2017-03-15 Thread Rafael Weingärtner

Folks,
It has been a week. I am assuming that no one knows about these tickets.

In the last years, our workflow has been improved greatly; most of the PRs
I see have Jira ticket associated and everything seems to be getting better
by the time; let’s not loose momentum. However, we still have some (a lot?)
Jira tickets that seem to be left behind.

In 48 ours I will close all of the tickets mentioned here. If I close
something that should not have been closed, please pardon me ;).

After this, I will proceed with a new batch of tickets. Hopefully, in some
iterations of this process, we can get rid of these forgotten tickets.

On Wed, Mar 8, 2017 at 2:15 AM, Daan Hoogland 
wrote:

> Good hard work again Rafael,
>
> I’ll try to find time today to browse through them.
>
> On 07/03/17 18:05, "Rafael Weingärtner" 
> wrote:
>
> Hi folks,
> Today I had gone through another batch of old Jira tickets and we have
> a
> bunch that can be closed again. The following are the ones I have gone
> through. Before I close any ticket I would like to check them with you,
> especially the ones from a category called “Seemed fixed, but I would
> like
> to hear some feedback here”. I will be waiting for your feedback
> before I
> proceed to close any ticket.
>
> - Jira tickets that have PRs and were already merged, or at least a
> commit
> hash code reference
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-9509
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-9634
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-9540
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-9635
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-9598
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-212
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-350
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-535
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-698
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-3054
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-7633
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-7405
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-8976
>
> - Jira ticket linked to a PR that is linked to a series of Jira tickets
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-9533 (was this
> solved?)
>
> - Seemed fixed, but I would like to hear some feedback here
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-245
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-272
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-371
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-429
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-438
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-458
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-486
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-506
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-561
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-582
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-626
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-692
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-696
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-994
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-1036
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-1306
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-5650
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-5642
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-4870 (naming
> conventions on Marvin?)
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-4759 (thoughts
> here
> Daan?)
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-4523
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-4365
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-4232
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-3896
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-3477
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-3012
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-1524 (Mike
> Tutkowski,
> is this still happenings? Is it possible for you to check?)
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-1432 (Mike, any
> thoughts here?)
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-7379 (title=200MB
> limit
> setting too low for network.throttling.rate and
> vm.network.throttling.rate;
> isn`t it a question for the operator/administrator to configure the
> default
> value?)
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-7167
> -- https://issues.apache.org/jira/browse/CLOUDSTACK-7142 (let's open
> tickets for specific issues and not for a broad class; then, the
> management
> (for us) becomes easier)
> --

Re: More Jira tickets clean up

2017-03-07 Thread Daan Hoogland

Good hard work again Rafael,

I’ll try to find time today to browse through them.

On 07/03/17 18:05, "Rafael Weingärtner"  wrote:

Hi folks,
Today I had gone through another batch of old Jira tickets and we have a
bunch that can be closed again. The following are the ones I have gone
through. Before I close any ticket I would like to check them with you,
especially the ones from a category called “Seemed fixed, but I would like
to hear some feedback here”. I will be waiting for your feedback before I
proceed to close any ticket.

- Jira tickets that have PRs and were already merged, or at least a commit
hash code reference
-- https://issues.apache.org/jira/browse/CLOUDSTACK-9509
-- https://issues.apache.org/jira/browse/CLOUDSTACK-9634
-- https://issues.apache.org/jira/browse/CLOUDSTACK-9540
-- https://issues.apache.org/jira/browse/CLOUDSTACK-9635
-- https://issues.apache.org/jira/browse/CLOUDSTACK-9598
-- https://issues.apache.org/jira/browse/CLOUDSTACK-212
-- https://issues.apache.org/jira/browse/CLOUDSTACK-350
-- https://issues.apache.org/jira/browse/CLOUDSTACK-535
-- https://issues.apache.org/jira/browse/CLOUDSTACK-698
-- https://issues.apache.org/jira/browse/CLOUDSTACK-3054
-- https://issues.apache.org/jira/browse/CLOUDSTACK-7633
-- https://issues.apache.org/jira/browse/CLOUDSTACK-7405
-- https://issues.apache.org/jira/browse/CLOUDSTACK-8976

- Jira ticket linked to a PR that is linked to a series of Jira tickets
-- https://issues.apache.org/jira/browse/CLOUDSTACK-9533 (was this solved?)

- Seemed fixed, but I would like to hear some feedback here
-- https://issues.apache.org/jira/browse/CLOUDSTACK-245
-- https://issues.apache.org/jira/browse/CLOUDSTACK-272
-- https://issues.apache.org/jira/browse/CLOUDSTACK-371
-- https://issues.apache.org/jira/browse/CLOUDSTACK-429
-- https://issues.apache.org/jira/browse/CLOUDSTACK-438
-- https://issues.apache.org/jira/browse/CLOUDSTACK-458
-- https://issues.apache.org/jira/browse/CLOUDSTACK-486
-- https://issues.apache.org/jira/browse/CLOUDSTACK-506
-- https://issues.apache.org/jira/browse/CLOUDSTACK-561
-- https://issues.apache.org/jira/browse/CLOUDSTACK-582
-- https://issues.apache.org/jira/browse/CLOUDSTACK-626
-- https://issues.apache.org/jira/browse/CLOUDSTACK-692
-- https://issues.apache.org/jira/browse/CLOUDSTACK-696
-- https://issues.apache.org/jira/browse/CLOUDSTACK-994
-- https://issues.apache.org/jira/browse/CLOUDSTACK-1036
-- https://issues.apache.org/jira/browse/CLOUDSTACK-1306
-- https://issues.apache.org/jira/browse/CLOUDSTACK-5650
-- https://issues.apache.org/jira/browse/CLOUDSTACK-5642
-- https://issues.apache.org/jira/browse/CLOUDSTACK-4870 (naming
conventions on Marvin?)
-- https://issues.apache.org/jira/browse/CLOUDSTACK-4759 (thoughts here
Daan?)
-- https://issues.apache.org/jira/browse/CLOUDSTACK-4523
-- https://issues.apache.org/jira/browse/CLOUDSTACK-4365
-- https://issues.apache.org/jira/browse/CLOUDSTACK-4232
-- https://issues.apache.org/jira/browse/CLOUDSTACK-3896
-- https://issues.apache.org/jira/browse/CLOUDSTACK-3477
-- https://issues.apache.org/jira/browse/CLOUDSTACK-3012
-- https://issues.apache.org/jira/browse/CLOUDSTACK-1524 (Mike Tutkowski,
is this still happenings? Is it possible for you to check?)
-- https://issues.apache.org/jira/browse/CLOUDSTACK-1432 (Mike, any
thoughts here?)
-- https://issues.apache.org/jira/browse/CLOUDSTACK-7379 (title=200MB limit
setting too low for network.throttling.rate and vm.network.throttling.rate;
isn`t it a question for the operator/administrator to configure the default
value?)
-- https://issues.apache.org/jira/browse/CLOUDSTACK-7167
-- https://issues.apache.org/jira/browse/CLOUDSTACK-7142 (let's open
tickets for specific issues and not for a broad class; then, the management
(for us) becomes easier)
-- https://issues.apache.org/jira/browse/CLOUDSTACK-7067 (questions should
be directed to the mailing list)
-- https://issues.apache.org/jira/browse/CLOUDSTACK-7056 (questions should
be directed to the mailing list)
-- https://issues.apache.org/jira/browse/CLOUDSTACK-7048
-- https://issues.apache.org/jira/browse/CLOUDSTACK-6849
-- https://issues.apache.org/jira/browse/CLOUDSTACK-6848
-- https://issues.apache.org/jira/browse/CLOUDSTACK-6643
-- https://issues.apache.org/jira/browse/CLOUDSTACK-6642
-- https://issues.apache.org/jira/browse/CLOUDSTACK-6641
-- https://issues.apache.org/jira/browse/CLOUDSTACK-6640
-- https://issues.apache.org/jira/browse/CLOUDSTACK-6639
-- https://issues.apache.org/jira/browse/CLOUDSTACK-6638
-- https://issues.apache.org/jira/browse/CLOUDSTACK-6637
-- https://issues.apache.org/jira/browse/CLOUDSTACK-6567
--

More Jira tickets clean up

2017-03-07 Thread Rafael Weingärtner

Hi folks,
Today I had gone through another batch of old Jira tickets and we have a
bunch that can be closed again. The following are the ones I have gone
through. Before I close any ticket I would like to check them with you,
especially the ones from a category called “Seemed fixed, but I would like
to hear some feedback here”. I will be waiting for your feedback before I
proceed to close any ticket.

- Jira tickets that have PRs and were already merged, or at least a commit
hash code reference
-- https://issues.apache.org/jira/browse/CLOUDSTACK-9509
-- https://issues.apache.org/jira/browse/CLOUDSTACK-9634
-- https://issues.apache.org/jira/browse/CLOUDSTACK-9540
-- https://issues.apache.org/jira/browse/CLOUDSTACK-9635
-- https://issues.apache.org/jira/browse/CLOUDSTACK-9598
-- https://issues.apache.org/jira/browse/CLOUDSTACK-212
-- https://issues.apache.org/jira/browse/CLOUDSTACK-350
-- https://issues.apache.org/jira/browse/CLOUDSTACK-535
-- https://issues.apache.org/jira/browse/CLOUDSTACK-698
-- https://issues.apache.org/jira/browse/CLOUDSTACK-3054
-- https://issues.apache.org/jira/browse/CLOUDSTACK-7633
-- https://issues.apache.org/jira/browse/CLOUDSTACK-7405
-- https://issues.apache.org/jira/browse/CLOUDSTACK-8976

- Jira ticket linked to a PR that is linked to a series of Jira tickets
-- https://issues.apache.org/jira/browse/CLOUDSTACK-9533 (was this solved?)

- Seemed fixed, but I would like to hear some feedback here
-- https://issues.apache.org/jira/browse/CLOUDSTACK-245
-- https://issues.apache.org/jira/browse/CLOUDSTACK-272
-- https://issues.apache.org/jira/browse/CLOUDSTACK-371
-- https://issues.apache.org/jira/browse/CLOUDSTACK-429
-- https://issues.apache.org/jira/browse/CLOUDSTACK-438
-- https://issues.apache.org/jira/browse/CLOUDSTACK-458
-- https://issues.apache.org/jira/browse/CLOUDSTACK-486
-- https://issues.apache.org/jira/browse/CLOUDSTACK-506
-- https://issues.apache.org/jira/browse/CLOUDSTACK-561
-- https://issues.apache.org/jira/browse/CLOUDSTACK-582
-- https://issues.apache.org/jira/browse/CLOUDSTACK-626
-- https://issues.apache.org/jira/browse/CLOUDSTACK-692
-- https://issues.apache.org/jira/browse/CLOUDSTACK-696
-- https://issues.apache.org/jira/browse/CLOUDSTACK-994
-- https://issues.apache.org/jira/browse/CLOUDSTACK-1036
-- https://issues.apache.org/jira/browse/CLOUDSTACK-1306
-- https://issues.apache.org/jira/browse/CLOUDSTACK-5650
-- https://issues.apache.org/jira/browse/CLOUDSTACK-5642
-- https://issues.apache.org/jira/browse/CLOUDSTACK-4870 (naming
conventions on Marvin?)
-- https://issues.apache.org/jira/browse/CLOUDSTACK-4759 (thoughts here
Daan?)
-- https://issues.apache.org/jira/browse/CLOUDSTACK-4523
-- https://issues.apache.org/jira/browse/CLOUDSTACK-4365
-- https://issues.apache.org/jira/browse/CLOUDSTACK-4232
-- https://issues.apache.org/jira/browse/CLOUDSTACK-3896
-- https://issues.apache.org/jira/browse/CLOUDSTACK-3477
-- https://issues.apache.org/jira/browse/CLOUDSTACK-3012
-- https://issues.apache.org/jira/browse/CLOUDSTACK-1524 (Mike Tutkowski,
is this still happenings? Is it possible for you to check?)
-- https://issues.apache.org/jira/browse/CLOUDSTACK-1432 (Mike, any
thoughts here?)
-- https://issues.apache.org/jira/browse/CLOUDSTACK-7379 (title=200MB limit
setting too low for network.throttling.rate and vm.network.throttling.rate;
isn`t it a question for the operator/administrator to configure the default
value?)
-- https://issues.apache.org/jira/browse/CLOUDSTACK-7167
-- https://issues.apache.org/jira/browse/CLOUDSTACK-7142 (let's open
tickets for specific issues and not for a broad class; then, the management
(for us) becomes easier)
-- https://issues.apache.org/jira/browse/CLOUDSTACK-7067 (questions should
be directed to the mailing list)
-- https://issues.apache.org/jira/browse/CLOUDSTACK-7056 (questions should
be directed to the mailing list)
-- https://issues.apache.org/jira/browse/CLOUDSTACK-7048
-- https://issues.apache.org/jira/browse/CLOUDSTACK-6849
-- https://issues.apache.org/jira/browse/CLOUDSTACK-6848
-- https://issues.apache.org/jira/browse/CLOUDSTACK-6643
-- https://issues.apache.org/jira/browse/CLOUDSTACK-6642
-- https://issues.apache.org/jira/browse/CLOUDSTACK-6641
-- https://issues.apache.org/jira/browse/CLOUDSTACK-6640
-- https://issues.apache.org/jira/browse/CLOUDSTACK-6639
-- https://issues.apache.org/jira/browse/CLOUDSTACK-6638
-- https://issues.apache.org/jira/browse/CLOUDSTACK-6637
-- https://issues.apache.org/jira/browse/CLOUDSTACK-6567
-- https://issues.apache.org/jira/browse/CLOUDSTACK-6484
-- https://issues.apache.org/jira/browse/CLOUDSTACK-6059
-- https://issues.apache.org/jira/browse/CLOUDSTACK-6033
-- https://issues.apache.org/jira/browse/CLOUDSTACK-9028 (seems more like a
question that no one replied than a bug)
-- https://issues.apache.org/jira/browse/CLOUDSTACK-9003
-- https://issues.apache.org/jira/browse/CLOUDSTACK-8807 (questions should
be directed to the mailing list)
--

Re: More Jira tickets clean up

Re: More Jira tickets clean up

Re: More Jira tickets clean up

Re: More Jira tickets clean up

Re: More Jira tickets clean up

More Jira tickets clean up

6 matches

Site Navigation

Mail list logo

Footer information