On Mon, 8 Feb 2010 10:02:01 -0500
m. allan noah kitno455 at gmail.com wrote:
I do not recall seeing any 1.1 API stuff being re-enabled although
there was talk of it. ?Is there any work to be done in that area?
Lets drop that idea for now. It is a roadblock to release.
Wasn't that stuff
On Tue, Feb 9, 2010 at 4:10 AM, Alessandro Zummo
azummo-lists at towertech.it wrote:
On Mon, 8 Feb 2010 10:02:01 -0500
m. allan noah kitno455 at gmail.com wrote:
I do not recall seeing any 1.1 API stuff being re-enabled although
there was talk of it. ?Is there any work to be done in that
why hasn't there been a release in a long time ?
I note that distributions including debian are shipping a version of
sane-backends that is really dated. They are missing out on enabling
working devices because of this (changes are long since committed
to git ).
I know this is not the fault
db db.pub.mail at gmail.com wrote:
Hi,
I know this is not the fault of sane, however this is causing a large
distance between what sane can do and what sane 'does' as shipped.
If there's no release, there's nothing new to package. As simple as
that.
So, yes, it is SANE's fault.
I'm not
I personally will take the great measure of responsibility for this
problem. My time has become very limited since I took over the job of
making releases. I have also allowed the confusion around a new API
prevent us from moving forward with maintenance releases, even though
that is an unrelated
I was going to wait a little closer to 1 year anniversary of last
release before bringing it up but thats starting to creep up on us. I
was also hoping we can get one out in time for Fedora 13 but their
freeze is coming up pretty quick.
I'll offer to help out as much as possible with the
On Mon, Feb 8, 2010 at 9:41 AM, Chris Bagwell chris at cnpbagwell.com wrote:
I was going to wait a little closer to 1 year anniversary of last
release before bringing it up but thats starting to creep up on us. ?I
was also hoping we can get one out in time for Fedora 13 but their
freeze is
m. allan noah kitno455 at gmail.com wrote:
Hi,
I personally will take the great measure of responsibility for this
problem. My time has become very limited since I took over the job of
making releases. I have also allowed the confusion around a new API
prevent us from moving forward with
On Mon, Feb 8, 2010 at 11:54 AM, Julien BLACHE jb at jblache.org wrote:
m. allan noah kitno455 at gmail.com wrote:
Hi,
I personally will take the great measure of responsibility for this
problem. My time has become very limited since I took over the job of
making releases. I have also
m. allan noah kitno455 at gmail.com wrote:
Hi,
Thanks for the vote of confidence, but your comments prove that my
second point is correct. We have allowed ourselves to stall releases
of updated code, because we keep talking about our hopes for the
We knew that could be a problem, but it only
On Mon, Feb 8, 2010 at 12:43 PM, Julien BLACHE jb at jblache.org wrote:
m. allan noah kitno455 at gmail.com wrote:
Hi,
Thanks for the vote of confidence, but your comments prove that my
second point is correct. We have allowed ourselves to stall releases
of updated code, because we keep
11 matches
Mail list logo
