incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Will Chan <>
Subject RE: Bug tracker: Re: [DISCUSS] - A must do tasks for the coming 1-2 months
Date Tue, 14 Aug 2012 03:19:00 GMT

>From a Citrix point of view, we will always need our own JIRA instance unless you just
mean the bugs.cs.o URL is going away only.  We will continue to carry on specific Citrix CloudPlatform
releases that will invariably differ in version and codename.  If we removed our JIRA instance,
we will have the same exact problem that ASF CS faces today.  There will be CCP upgrade, build,
and perhaps potential customer sensitive issues that just cannot be tracked in the ASF Jira
instance.  I am assuming ASF bug instance is not going to be used for Citrix's releases nor
anyone else's.

That said, my mandate for the engineering team is to always keep bugs tracked on the ASF Jira
instance unless it must be kept private.  If some time from now that we really don't find
a need for the CCP JIra instance, then sure we can decomission it, but I can't see that happening.


From: David Nalley []
Sent: Monday, August 13, 2012 7:18 PM
Subject: Re: Bug tracker: Re: [DISCUSS] - A must do tasks for the coming 1-2 months

On Mon, Aug 13, 2012 at 8:48 PM, Ewan Mellor <> wrote:
>> -----Original Message-----
>> From: David Nalley []
>> [Snip]
>> So my thoughts are:
>> We should abandon thoughts of migration, and start from scratch on the
>> ASF's bug tracker.
>> We'll redirect to the ASF's jira instance.
>> We should leave the existing jira instance as it is. (Citrix will be migrating
>> either to a new instance as part of the migration plan already), and available
>> for reference purposes in a read only state.
> Yeah, I think we're suffering now in this limbo state with the bug tracker there but
not really useful.  A clean slate sounds best to me.  The old data will still be there if
people need it.
> Is there any need to redirect though?  Wouldn't we just tell everyone
what the new URL is for the new project?  It's not like any of the URLs will redirect cleanly

Well bugs.cs.o is going to go away in the long term. Besides, I want
things to be unmistakably clear to folks who visit what currently is
bugs.cs.o that it is read only and not send tons of messages asking
why the can't file bugs (as happened when we moved from
to Maybe in the short term we load an
intermediate page announcing the change and have the page redirect
after some small reading time.
I suppose the existing instance will stay around at least till license
expiration, which should get us to April or May next year. We can
reevaluate then.
My expectation is that what is currently bugs.cs.o will become
read-only, and only exist for historical reasons, and we'd make the
url something that clearly denotes its deprecated state, perhaps
something like

View raw message