James C. McPherson wrote:
Mike Kupfer wrote:
Here are a few more thoughts on requirements, after spending 20 minutes
or so looking through the Bugster functional specs.
* automated account creation (conditional requirement?). It should be
possible to use one's opensolaris.org account to access the BTS.
Example implementation techniques: (1) the BTS has an extensible
authentication mechanism, so that we can write a plugin that talks to
the opensolaris.org authentication service; (2) the BTS's account
table is open enough that the opensolaris.org webapp can update it.
Agreed. We should get this tied in to the opensolaris.org registered
email address so that you can get bug updates sent to (eg)
[EMAIL PROTECTED]
and that be forwarded/redirected to
[EMAIL PROTECTED]
* multi-release support (optional requirement?). It should be easy to
match up a bug with the releases that the bug appears in, and to track
backports.
MR support is a requirement. I think MRs are one of
the features that I could say that I actually enjoy
using - makes tracking backports that I work on much
easier than the rather fuzzy bugtraq+ way of tracking.
Multi-release support would make it much easier to cope with
variant distros as well; one could figure out which Nexenta
or Bellanix release incorporated a particular fix easiy....
- Bart
--
Bart Smaalders Solaris Kernel Performance
[EMAIL PROTECTED] http://blogs.sun.com/barts
_______________________________________________
tools-discuss mailing list
tools-discuss@opensolaris.org
