com]
> Sent: 15 August 2012 16:34
> To: Ewan Mellor
> Cc: cloudstack-dev@incubator.apache.org
> Subject: Re: Bug tracker: Re: [DISCUSS] - A must do tasks for the coming 1-2
> months
>
> I just submitted it to bugs.cloudstack.org thinking I could just resubmit
> later.
&g
David Nalley [mailto:da...@gnsa.us]
>> Sent: 15 August 2012 13:03
>> To: cloudstack-dev@incubator.apache.org
>> Subject: Re: Bug tracker: Re: [DISCUSS] - A must do tasks for the coming 1-2
>> months
>>
>> On Wed, Aug 15, 2012 at 3:59 PM, Ewan Mellor
>> wro
> -Original Message-
> From: David Nalley [mailto:da...@gnsa.us]
> Sent: 15 August 2012 13:03
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: Bug tracker: Re: [DISCUSS] - A must do tasks for the coming 1-2
> months
>
> On Wed, Aug 15, 2012 at 3:59
On Wed, Aug 15, 2012 at 3:59 PM, Ewan Mellor wrote:
> That really depends on how long it's going to take. David, any idea how long
> that Jira request will take to fulfil?
>
No idea.
An infra person with admin privs on Jira - likely a volunteer, will
have to take it up and get it done, and then
che.org
> Subject: Re: Bug tracker: Re: [DISCUSS] - A must do tasks for the coming 1-2
> months
>
> So the impression is that we should wait for the jira setup to submit any
> further bugs, correct?
>
> On Tue, Aug 14, 2012 at 11:18 AM, Chiradeep Vittal
> wrote:
> &
So the impression is that we should wait for the jira setup to submit
any further bugs, correct?
On Tue, Aug 14, 2012 at 11:18 AM, Chiradeep Vittal
wrote:
>
>
> On 8/14/12 9:50 AM, "Joe Brockmeier" wrote:
>
>>On Tue, Aug 14, 2012 at 12:12:27PM -0400, David Nalley wrote:
>>> One more thing. Since
On 8/14/12 9:50 AM, "Joe Brockmeier" wrote:
>On Tue, Aug 14, 2012 at 12:12:27PM -0400, David Nalley wrote:
>> One more thing. Since this doesn't look like it locks us in to either
>> side of this equation irreversibly, if someone doesn't object in the
>> next 5-6 hours my intention is to reques
On Tue, Aug 14, 2012 at 12:12:27PM -0400, David Nalley wrote:
> One more thing. Since this doesn't look like it locks us in to either
> side of this equation irreversibly, if someone doesn't object in the
> next 5-6 hours my intention is to request the above. Let me know if
> this irks anyone.
No
On Tue, Aug 14, 2012 at 12:09 PM, David Nalley wrote:
> On Mon, Aug 13, 2012 at 5:18 PM, David Nalley wrote:
>> On Tue, Jul 31, 2012 at 2:08 PM, David Nalley wrote:
>>> On Mon, Jul 30, 2012 at 4:45 PM, Mohammad Nour El-Din
>>> wrote:
Hi...
I was talking to David Nalley over I
On Mon, Aug 13, 2012 at 5:18 PM, David Nalley wrote:
> On Tue, Jul 31, 2012 at 2:08 PM, David Nalley wrote:
>> On Mon, Jul 30, 2012 at 4:45 PM, Mohammad Nour El-Din
>> wrote:
>>> Hi...
>>>
>>>I was talking to David Nalley over IRC and we spotted two main tasks
>>> that we should put our foc
> -Original Message-
> From: Caleb Call [mailto:calebc...@me.com]
> Sent: 13 August 2012 20:57
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: Bug tracker: Re: [DISCUSS] - A must do tasks for the coming 1-2
> months
>
> There may be other issues I've
>
> Will
>
>
> From: David Nalley [da...@gnsa.us]
> Sent: Monday, August 13, 2012 7:18 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: Bug tracker: Re: [DISCUSS] - A must do tasks for the coming 1-2
> months
>
> On Mon,
, but I can't see that happening.
Will
From: David Nalley [da...@gnsa.us]
Sent: Monday, August 13, 2012 7:18 PM
To: cloudstack-dev@incubator.apache.org
Subject: Re: Bug tracker: Re: [DISCUSS] - A must do tasks for the coming 1-2
months
On Mon,
On Mon, Aug 13, 2012 at 8:48 PM, Ewan Mellor wrote:
>> -Original Message-
>> From: David Nalley [mailto:da...@gnsa.us]
>>
>> [Snip]
>>
>> So my thoughts are:
>>
>> We should abandon thoughts of migration, and start from scratch on the
>> ASF's bug tracker.
>> We'll redirect bugs.cloudstack
August 14, 2012 5:57 AM
To: cloudstack-dev@incubator.apache.org
Subject: RE: Bug tracker: Re: [DISCUSS] - A must do tasks for the coming 1-2
months
I'm for this move to quickly start a brand new bug DB simply because there's
almost no workflow process for 4.0 or at least a way of track
> -Original Message-
> From: Chip Childers [mailto:chip.child...@sungard.com]
> Sent: Monday, August 13, 2012 5:52 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Re: Bug tracker: Re: [DISCUSS] - A must do tasks for the coming 1-2
> months
>
> Also, ca
On Mon, Aug 13, 2012 at 5:56 PM, Will Chan wrote:
> I'm for this move to quickly start a brand new bug DB simply because there's
> almost no workflow process for 4.0 or at least a way of tracking bugs that
> need to be fixed for 4.0 release.
+1 - we should absolutely get started fresh in the AS
> -Original Message-
> From: David Nalley [mailto:da...@gnsa.us]
>
> [Snip]
>
> So my thoughts are:
>
> We should abandon thoughts of migration, and start from scratch on the
> ASF's bug tracker.
> We'll redirect bugs.cloudstack.org to the ASF's jira instance.
> We should leave the existi
end to at least duplicate the bug from the current repo to the
new ASF one.
Will
> -Original Message-
> From: David Nalley [mailto:da...@gnsa.us]
> Sent: Monday, August 13, 2012 2:18 PM
> To: cloudstack-dev@incubator.apache.org
> Subject: Bug tracker: Re: [DISCUSS] - A must do
Hi Justin:
So currently, I am restoring the database and attachments to a set of
test machines.
I then delete any ticket that triggers a security level higher than
public or none.
Then use jira's XML export to export the bugs themselves.
And of course a separate archive of the attachments.
Then I
Dave,
Is this a problem that has not been able to take advantage of a
programmatic solution? I guess the question I am asking is what is the
current workflow that is being used?
On Mon, Aug 13, 2012 at 5:18 PM, David Nalley wrote:
> On Tue, Jul 31, 2012 at 2:08 PM, David Nalley wrote:
> > On M
On Tue, Jul 31, 2012 at 2:08 PM, David Nalley wrote:
> On Mon, Jul 30, 2012 at 4:45 PM, Mohammad Nour El-Din
> wrote:
>> Hi...
>>
>>I was talking to David Nalley over IRC and we spotted two main tasks
>> that we should put our focus on in the coming 1-2 months and
>> more preferably the comi
22 matches
Mail list logo
