On Thu, Apr 20, 2006 at 04:14:19PM -0700, Don Brown wrote:
> Jeff Turner, who set this up, wanted separate instances, and in fact, he 
> wants, IIRC, that to be how JIRA is used at 
> Apache from now on.  The separate instance allows each of our subprojects to 
> have their own JIRA project, and helps 
> isolate problems so that one instance won't bring all projects down.

Separate JIRA instances is mostly a necessary evil at the moment, as
merging JIRA databases isn't possible, so we couldn't merge in Webwork.
It does have its advantage of isolating problems as you say.  I've
attached a mail with further details.

Also, if the Struts JIRA has problems, please report them to
[EMAIL PROTECTED] Griping on the dev list won't help :)


--Jeff

> It also made the migration of existing WebWork tickets much easier, if not 
> even possible.
> 
> Don
> 
> Sean Schofield wrote:
> > Don,
> > 
> > I've been off the list for a while now but can you explain why this is
> > a completely separate JIRA instance from the other ASF projects?  Why
> > not use the existing one at http://issues.apache.org/jira?
> > 
> > +1 (as always) for migrating to JIRA.  I find Bugzilla to be
> > unbearable compared to JIRA.  I just don't see why a separate instance
> > is needed.
> > 
> > Sean
> > 
> > On 4/20/06, Don Brown <[EMAIL PROTECTED]> wrote:
> >> With our JIRA instance stood up, it is time to revisit our earlier 
> >> decision to migration our Struts Bugzilla tickets to
> >> JIRA.
> >>
> >> http://issues.apache.org/struts
> >>
> >> I believe most of this work can be done without bothering infrastructure, 
> >> as the import can be done through JIRA's web
> >> admin interface.  Most of the committers don't have accounts, so please 
> >> create one and let me know so I can give you the
> >> proper access.
> >>
> >> I propose we do the migration this weekend.  Any comments/objections?
> >>
> >> Don
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > 
> > 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
--- Begin Message ---
On Mon, Apr 17, 2006 at 07:43:48PM +0400, Andrus Adamchik wrote:
> Jeff,
> 
> Before I open an INFRA issue on that, I wanted to check with you. Our  
> new Jira works well, but there is a strong sentiment among our  
> mentors and committers that we should be moved to a shared Apache  
> Jira instance.

There is an equally strong sentiment amongst infra people, because one
Jira is easier to maintain than 4 (and counting) and uses less memory.
However, merging relational datasets is not the easiest thing to do.
Conflicts potentially arise with users, permission schemes, notification
schemes, custom fields, field screens.. pretty much every admin-level
object that relates to a project. Inter-project issue links may break,
user dashboards refer to now nonexistent projects, etc.

The relevant feature request for JIRA is:

http://jira.atlassian.com/browse/JRA-1604

A simpler approach is to allow single sign-on by reusing a single user
database (userbase).  This would require some work on OSUser, the library
JIRA uses for user/profile management:

http://opensymphony.com/osuser/

Specifically, although OSUser allows two differently configured
ProfileProviders, they would both reuse the same PropertySet instance
(where user profile details are looked up). Some work needs to be done so
that each ProfileProvider can be configured with its own PropertySet.
I've been playing around on my laptop, but can't promise anything.

Hope that clarifies things :) Feel free to forward to people who might be
inclined to vote for the issue above. 


--Jeff

> See this thread for the discussion:
> 
> http://objectstyle.org/cayenne/lists/cayenne-devel/2006/04/0170.html
> 
> People want the ability to cross-link and have a single sign on point  
> with other projects. I tend to agree with that too.
> 
> Do you see any problems in moving as to the main Jira?
> 
> Thanks
> Andrus


--- End Message ---
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to