What exactly do we want to track? IMO...
- Bugs
- Feature Requests
- Support Requests
- Patches
Ideally I'd like to have a SXEmacs interface to all these trackers.
For both developers (us) and users. I understand that a SXEmacs
front-end won't always be practical or possible (think bug report about
a SXEmacs that refuses to start).
Maybe we could go with something like BugZilla and write a SXEmacs
front-end to it some time in the future?
Oh, before I go any further, here's one of the things I absolutely
*HATE* about BugZilla... You have to create an "account" and log in
_before_ you can submit a bug report. I _really_ do not want to put
that burden on our users.
Anyway, here's how I sort of see it working...
1) User finds a problem and submits a report. (ideally with `M-x
sxemacs-report-bug').
2) The user is immediately sent out an acknowledgment/thank you
email. This email will contain things like a "bug number" that
the user should quote in any correspondence pertaining to this
issue. Also instructions on how they can monitor the progress of
the bug.
3) At the same time as the user gets their ack, the bug report will
come here (to the mailing list), and if possible, to the
developer who has assigned themselves to be in charge of bugs in
that particular area of SXEmacs.
4) The SXEmacs developer who is responsible for this bug will update
the bug tracker each time something is done toward fixing it.
Each time the tracker is updated the original submitter will get
email saying so. Also anyone who wishes to "follow" the bug will
get email.
5) Once the bug is "closed", in other words it is no longer a bug
because it has been fixed ("fixed" can also mean "user
instruction or hand holding"), the original submitter is notified
and thanked.
I want...
o To be able to search the bug database using the details from a
submitted bug for the search criteria. So we can determine
whether this bug has already been reported. Ideally, I'd like
this to happen automatically at bug submission time.
If someone submits a bug that is already in the database, I'd like
the submitter to be informed of such and be offered to be added to
the list of people who are "following" the bug. Or if it has
already been resolved, point them to where they can find out about
it.
o Constant communication between the bug submitter and Us. With as
much as possible being automated so it isn't forgotten about.
o A real live person to get into contact with the bug submitter
_within 48 hours_ of the bug report coming in.
o In absolutely no circumstances will any bug report get lost or
forgotten or neglected. I want the bug tracker to send out
automated reminders to whoever takes responsibility for the bug.
The higher the priority of the bug, the more frequent the
reminders.
Feature requests and support requests should work the same way as bug
reports. Although I believe that support requests should generate
contact from a real live person _within 24 hours_.
Patch tracking will probably work in a similar way too. I'd
definitely want `M-x sxemacs-submit-patch' to automate the process for
the user.
For us with patches, I'm not going to put too many restrictions on
it. Basically once you have commit privileges you'll be able to
commit when or what you like (there may be times when this isn't the
case). If you fuck something up you immediately remove it or fix it.
Simple.
Obviously it goes without saying that you'd inform us of your plans
here before you start committing oodles of new whiz-bang features.
CVS can easily be made to post diffs to a "sxemacs-patches" mailing
list.
Well that's pretty much how I see SXEmacs Issue Tracking. I've only
heard of three issue trackers... BugZilla, Gnats, and whatever SF and
Savannah uses. I don't know any of them all that well.
Give me options folks! Is there anything out there that will give us
what I want?
--
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
| In space, |
| No one can hear you rip a stinky |
|------------------------------------<steve@xxxxxxxxxxx>---|
pgpS10dvGclAq.pgp
Description: PGP signature
|