[sane-devel] Preparing for a sane-backends release
m. allan noah
kitno455 at gmail.com
Thu Aug 6 12:15:04 UTC 2015
On Thu, Aug 6, 2015 at 2:22 AM, Stef <stef.dev at free.fr> wrote:
> On 03/08/2015 20:08, m. allan noah wrote:
>> It's been a long time since we have done a sane-backends release, and
>> much code has changed. I propose to do a release sometime in mid
>> Unfortunately, there have been a number of patches posted to this
>> mailing list or the bug tracker, which have not been applied. In
>> particular, I know that Gentoo has some systemd compilation fixes. We
>> also have a large number of open bug reports- sometimes waiting years
>> for reporter responses.
>> 1. Is there someone willing to volunteer to find some of the patches
>> we missed, and investigate their suitability?
>> 2. Are backend authors able to investigate and close some tickets?
>> If we can clean some of these things up, I will pick a date, and do the
> I'm already currently working on closing as much tickets I can on the
> backends I maintain.
> I think we shouldn't do a release without the new pie backend (see
> I planned to have a look at it once I have done fixing bugs in genesys
Agreed- I also have not had a chance to look at it.
> And I'd rather not close any ticket because it is too old. I have seen
> that process to many times at work:
> 1 - don't answer the bug reports because your are busy adding more
> 2 - wait for too long
> 3 - close them because they are too old when management get scared of
> the tickets stock pile
> Bug reports are accumulating because we need more developers.
I was speaking specifically about bug reports where we have asked the
original reporter for more information, and they have not gotten back
to us. If the report is open because a sane developer needs to do
something, then it should probably stay open.
"well, I stand up next to a mountain- and I chop it down with the edge
of my hand"
More information about the sane-devel