There may be other issues I've missed in the discussions on separating them but, instead of standing up two separate Jira instances, why not just use separate projects within the current Jira project? Make the current CS project read-only and/or locked down to only admins (or whoever is deemed necessary to have access), use the CP project for citrix customers/bugs, and create a new one for the Apache release??? Just a thought, I'm sure I've missed something in previous discussions. This approach would also simplify the export/import of existing bugs because any existing bugs that needs to be, could be moved to the new project. Then the existing bugs would automatically redirect to the new project for that same bug.
-Caleb On Aug 13, 2012, at 9:19 PM, Will Chan <will.c...@citrix.com> wrote: > Dave, > > 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. > > 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, Aug 13, 2012 at 8:48 PM, Ewan Mellor <ewan.mel...@eu.citrix.com> > 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.org 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 bugs.cloudstack.org 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 anyway. >> > > 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 bugs.cloud.com > to bugs.cloudstack.org) 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 oldbugs.cloudstack.org. > > --David
