[sane-devel] why hasn't there been a release in a long time ?

[m. allan noah]

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 coming up pretty quick.
>
> I'll offer to help out as much as possible with the release.  I can do
> my set of platform checks (cygwin, osx, solaris, pulling any Fedora
> patches that make sense, etc).  Basically, I can make sure the steps
> in release.txt are pain free up to the Announcing Release step.

If you have the time to dig into distributor patches, that would be
very helpful. Also trying to build on more platforms is always good.
Also, there are many outstanding issues in the bug tracker that need
to be looked at. Most are individual backend problems, but at least a
few are 'sane-wide' issues. Not sure if you want to look at those too.

> 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.

allan

>
> Chris
>
> On Mon, Feb 8, 2010 at 8:16 AM, m. allan noah <kitno455 at gmail.com> wrote:
>> 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 issue.
>>
>> If someone else wants to step up and schedule/make the release, I'd be
>> happy for the help. Otherwise, let me look at a calendar, and come up
>> with a plan. Thanks for the kick in the pants :)
>>
>> allan
>>
>> On Mon, Feb 8, 2010 at 6:39 AM, Julien BLACHE <jb at jblache.org> wrote:
>>> 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 packaging git snapshots because I cannot support them in a
>>> stable Debian release. I used to package CVS snapshots when I knew a
>>> release was coming up and would be out & suited for Debian stable at a
>>> time where I could still push it into stable.
>>>
>>> With the 1.1 API stuff and no release schedule, I can't do that anymore.
>>>
>>> JB.
>>>
>>> --
>>> Julien BLACHE                                   <http://www.jblache.org>
>>> <jb at jblache.org>                                  GPG KeyID 0xF5D65169
>>>
>>> --
>>> sane-devel mailing list: sane-devel at lists.alioth.debian.org
>>> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
>>> Unsubscribe: Send mail with subject "unsubscribe your_password"
>>>             to sane-devel-request at lists.alioth.debian.org
>>>
>>
>>
>>
>> --
>> "The truth is an offense, but not a sin"
>>
>> --
>> sane-devel mailing list: sane-devel at lists.alioth.debian.org
>> http://lists.alioth.debian.org/mailman/listinfo/sane-devel
>> Unsubscribe: Send mail with subject "unsubscribe your_password"
>>             to sane-devel-request at lists.alioth.debian.org
>>
>



-- 
"The truth is an offense, but not a sin"