Bug database

[dunx]

I know this forum is basically the bug tracking system for the beta, but an instance of a bug database might be useful too (eg Bugzilla - www.bugzilla.org/ - which is Free).

It would help with duplicates, and with tracking status.

I've been more a user of bug databases than an administrator, but I could probably help setting one up if need be.

[janra]

If you want I can host a bugzilla site for scrivener - already have it installed for another project I work on, so it would be dead easy to set up a second one. Say the word, name the domain, and it's yours :-)

(I notice scrivener doesn't have a domain yet, so if you want scrivener.write-on.org or scrivener-bugs.write-on.org or just about anything under write on's domain you can have that.)

-janra

[KB]

Many thanks for the offer - let me look into Bugzilla and I will get back to you. Right now I like the informal forum approach, as it makes things more friendly - I like the interaction at this stage.
Thanks again,
Keith

[janra]

Yeah, bugzilla can be a little impersonal. Let me know if you decide to try it.

[dunx]

I have to say that I like the interactivity of the forums too. The reason I suggested the bug database was that I've noticeed some problems even with only two beta versions so far of not knowing which version of the code we're talking about. These details are a lot easier to track in a formal bug database.

But maybe that's just me. Maybe having a bug DB running alongside the forums would be a better bet.

[amberv]

I agree with Dunx. A bug tracking system is good for the users too, because it makes it easier to look up a behaviour you have noticed, and then to see the state of it. A good bug tracker will feel a lot like a forum with comments and dialogue, but with a lot of data to help the developer out, such as OS version, hardware, software version, and so on.

But, during November it might be overkill. We had a nice run in October, but now that Nano is going on -- I feel that a lot of us have a drastically reduced beta testing time allotment, and setting up and learning a new system during November might not be necessary.

Eventually though, it would be nice.

[KB]

But on the other hand, would you rather my time went into sorting out and managing a bug tracking system, or into developing Scrivener? I am one pair of hands only. Does Ulysses or Copywrite or Avenir have a bug tracking system? Come to that, does Copywrite or Avenir even have a forum?

[amberv]

That would be the obvious disclaimer to any suggestion I have. As long as it makes bug squashing easier for you, we'll put up with whatever system you prefer. If a tracking db is going to waste more time managing it than using it, then forget it! I don't really mind forums.

I don't think I'll be violating any agreements if I say that Ulysses does have a bug tracking system for beta users, so that we do not clutter up the main user forum. Since the Scrivener forum is for bug users though, that is not really an issue yet. I cannot say anything for the other apps. I am not involved with their development, nor know anything of it.

[janra]

KB: yes, you have only one pair of hands, but I have one pair too, and I have set up bugzilla for a project before :-)

[KB]

Thanks. I think that for now it would just be better if I organised the "to do" page a bit better, so that it is less disorganised. It needs a version history, so that users can check the version they are using and easily see whether or not the bug they have encountered is fixed, ie:

1.1.2b (UPCOMING)
Fixed blah blah

1.1.1b (date of release)
Etc etc

That will be easier for me, and still fairly easy for users.

Janra - thanks again for the offer. At the moment I think I will leave it as it is, though. The "to do" page is a working document for me, and very easy for me to go through systematically.

Keith