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 <[email protected]> wrote: > db <[email protected]> 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> > <[email protected]> GPG KeyID 0xF5D65169 > > -- > sane-devel mailing list: [email protected] > http://lists.alioth.debian.org/mailman/listinfo/sane-devel > Unsubscribe: Send mail with subject "unsubscribe your_password" > to [email protected] > -- "The truth is an offense, but not a sin" -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
