Valerie Bubb Fenwick <[EMAIL PROTECTED]> writes: > On Wed, 28 Nov 2007, Dave Miner wrote: > >> Danek Duvall wrote: >>> On Tue, Nov 27, 2007 at 02:41:59PM +0000, Darren J Moffat wrote: >>> >>>> How do I get a Buzilla category for http://defect.opensolaris.org/bz >>>> added for an opensolaris.org hosted project ? >>>> >>>> ZFS Crypto in particular. >>> >>> Stephen and I (anyone else?) have admin access. >> >> Comay, Glynn, Alan Burlison and I do as well. Thanks for doing this >> one, Danek. > > Hi Dave - > > I brought this up to Danek offline, but I didn't realize there were > so many administrators for this bugzilla instance, so I guess I should > mention it on the alias. > > I was under the impression that we were going to try to keep bugster & > bugzilla in sync for product "solaris" for now (I realize darren's request > was for a different product, so it's not really relevant now, but made > me think it was worth discussing before we had a more specific request).
I was under the opposite impression. If *I* gave you that impression, I certainly didn't intend to. > We want to keep these in sync right now for two reasons: ease of > migration, and right now we are proposing using bugster as an > annotation database for bugzilla (ie somewhere to store customer > records, confidential information, and information about older > releases). Bugzilla should, per the requiments, have a mechanism to store confidential information, though I can guess (and understand) the reason why it wouldn't be suitable. > (If we decide later to go with something else, then obviously the > need to keep in sync goes away - but if we diverge now, it will > be harder later on if we do want to use it as an annotation database). Are you suggesting they be cleaned up/changed in sync, or neither be changed? Beyond that, if a project doesn't *want* any information in bugster (I wouldn't, for instance, at least while under development), that must be handled. > That being he case, we should come up with some sort of guidelines for > administrators to make sure these databases do keep in sync for the time > being. For example, only adding things under product solaris to > bugzilla that have already been added to bugster. For the time being perhaps, but if and when bugzilla becomes our primary DTS, the reverse must be true. There is at least one too many barriers on the bugster side for me to even vaguely endorse the above as written (the requirement for an RM). > As far as making new "products" for development things, I would also > advise that the maintainers come up with a policy for that. Consistency > now will help you in the long term. I'd be happy to tell you how > we handle this for bugster, but I think as long as you come up with > something all administrators agree on, I think it'll be fine. > I'd like to see the information, even if the chances are I'll disagree with much of it, since I always seem to. :) -- Rich _______________________________________________ tools-discuss mailing list [email protected]
