Joe,
Please read through for my responses...
Charles Daminato
OpenSRS Product Manager
Tucows Inc. - [EMAIL PROTECTED]
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Joe Rhett
> Sent: April 17, 2001 1:40 PM
> To: Charles Daminato
> Cc: [EMAIL PROTECTED]
> Subject: Re: you make it sound like we don't care
>
>
> The concern is that we have to maintain bug fixes and keep patching them
> into multiple updates to the code. Features are more important than bug
> fixes in your mind, even when the bug fixes are handed to you.
>
We are aware of the difficulty in maintaining updates to fixes - with this
in mind, newer releases of the code include diff files between previous
versions (2.32 to 2.33 for example) and between major versions (2.3 to 2.4,
when we get there). And it is not true that features are more important -
bug fixes have one of the highest priorities in the entire organization.
But we do have to release features to assuade the concerns of other of our
resellers. It's a juggling act.
> The whole 'value' of OpenSRS was to have an open code base that people can
> contribute to. But you've dismissed that entire value by failing to pay
> attention to the people who report the issues.
>
We take in all the issues, and work on them in the most efficient manner
possible - admittedly we're not perfect at this, but we are working on
things and improving our processes (and prioritization criteria) all the
time.
> Frankly, I'm very frustrated with having to track a list of known bugs in
> the programs and the patches people have provided, and then
> compare against
> each new release to find out if you fixed the problem or not. It
> appears to
> take 3-4 updates before a bug is fixed. You don't mention whether
> you fixed
> the bugs or not in your release notes. So all the work is left to us.
>
This is fixed. Current mandate is to release diff files (as mentioned
above), as well as have the ChangeLog state EXACTLY what was fixed (nothing
ambiguous like "mods to reg_system.cgi") as well as what version was
released on which date. And we're now announcing which bugs were fixed with
which release, as well as establishing a protocol (starting this month!)
whereby we tell you, the reseller, what's being worked on now and in some
cases why.
> When people supply patches that _do_ solve the problem and _don't_ break
> anything is it too much to ask that you implement them? Or at least
> acknowledge that you haven't solved the problem in your release notes?
>
We do implement them, and historically haven't been good at tracking that
back into the ChangeLog. Many cooks in this kitchen, and someone threw out
our souffle recipe. The fixes will be released, acknowledgements are going
to be tracked and announced publicly.
I appreciate your comments - there's pull from many of you to "put more
stuff in" and there's pull from many of you to "fix what you have first".
We're working hard to find a middle ground where we can make as many of you
as happy as possible. You can't make everyone happy all of the time
(unfortunately), but we're getting better at prioritizing, fixing,
announceing, etc.
> On Sun, Apr 08, 2001 at 04:20:05PM -0400, Charles Daminato wrote:
> > Dave,
> >
> > It would be nice if we can fix all reported bugs - but you make it sound
> > like a) we don't care, and b) we do nothing at all. We're aware of the
> > issues, and we work on them all as fast as we can, given our
> resources and
> > the way things work out. While it would be nice for us to jump on
> > everything on our list, things crop up from time to time that are out of
> > our control and we have to work on that first - such as an NSI downtime
> > that squirted out some problems (bug's been fixed, data errors are being
> > worked on - we want to be 100% sure that we fix it right, and once).
> >
> > Charles Daminato
> > TUCOWS Product Manager
> > [EMAIL PROTECTED]
> >
> > On Sun, 8 Apr 2001, Dave Warren wrote:
> >
> > > It's too bad that OpenSRS can't be bothered to fix all the
> reported bugs.
> > > There's junk in there that was reported over a year ago that is still
> > > broken.
> > >
> > >
> > > ----- Original Message -----
> > > From: "411" <[EMAIL PROTECTED]>
> > > To: "Robert L Mathews" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> > > Sent: Sunday, April 08, 2001 12:59 PM
> > > Subject: Re: TV - @ for 1 deal.....
> > >
> > >
> > > > simply remove the price from the template and
> > > > say something like "this domain costs more; click the link
> to find out
> > > > the actual price".
> > >
> > >
> > > ========================================================
> > > Dave Warren,
> > > Email: [EMAIL PROTECTED]
> > > Pager: [EMAIL PROTECTED]
> > > ========================================================
> > >
> > >
> > >
>
> --
> Joe Rhett Chief Technology Officer
> [EMAIL PROTECTED] ISite Services, Inc.
>
> PGP keys and contact information:
http://www.noc.isite.net/Staff/
