Re: [sane-devel] Is it time of a new release?
On Tue, May 2, 2017 at 4:56 PM, Tom Myerswrote: > Do you know if the new release 1.0.26 will be built for macOS Sierra > (10.12)? I would be willing to help a bit on this. I tried to build it with > the latest Xcode and had issues. Not sure if it was me or the code. I am a > bit rusty in using the latest code but would be willing to help if need be. > Tom, we have historically relied on Mattias Ellert to do the OSX versions. I don't know if he had to apply patches to enable the compilation. If you want to give it a go, I would look for any patches like that first. allan -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand" -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Is it time of a new release?
Hi Luiz, Luiz Angelo Daros de Luca writes: > Hi, > > We already have more than 500 commits since 1.0.25. As a downstream > maintainer (openwrt/lede), I get lost between those tons of patches > and how to select them to be backported. > > Shouldn't sane-backend release a new version? As Allan mentioned in another reply, there is talk of releasing sometime in April. > Also, It would be really nice if SANE could keep a stable branch. It would > be, at least, a place to target cherry-picks. Considering the way things work now (as in, we don't do bug fix releases of any kind), the RELEASE_1_0_x tag would be the start of your stable branch for the largest value of x. > Maybe it could change its version number to something like other projects > do as: > > x.y.0 - feature release x.y > x.y.n - fix release n > > It would be better if x.y is year/month. At least there is no discussion on > whether the new release is big enough to tic the first number. This would break the dll backend, like, completely. For better of for worse (the latter if you ask me), that backend's backend loading logic is tightly tied to the package's version number. To such an extent, that we cannot even release a 1.1.x without breaking stuff, IIRC. Hope this, eh, helps, -- Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9 Support Free Softwarehttps://my.fsf.org/donate Join the Free Software Foundation https://my.fsf.org/join -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org
Re: [sane-devel] Is it time of a new release?
We were discussing another release recently. We have at least one major networking security bug we need to fix, and there are a few backends which have some outstanding patches yet to commit. I think perhaps at the end of April these things will be ready. If you are able, taking a pass through our bug tracker looking for things we might have missed would be helpful. allan On Sun, Mar 12, 2017 at 5:29 PM, Luiz Angelo Daros de Lucawrote: > Hi, > > We already have more than 500 commits since 1.0.25. As a downstream > maintainer (openwrt/lede), I get lost between those tons of patches > and how to select them to be backported. > > Shouldn't sane-backend release a new version? > > Also, It would be really nice if SANE could keep a stable branch. It would > be, at least, a place to target cherry-picks. > > Maybe it could change its version number to something like other projects do > as: > > x.y.0 - feature release x.y > x.y.n - fix release n > > It would be better if x.y is year/month. At least there is no discussion on > whether the new release is big enough to tic the first number. > > Regards, > -- > > Luiz Angelo Daros de Luca > luizl...@gmail.com > > > -- > sane-devel mailing list: sane-devel@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel > Unsubscribe: Send mail with subject "unsubscribe your_password" > to sane-devel-requ...@lists.alioth.debian.org -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand" -- sane-devel mailing list: sane-devel@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to sane-devel-requ...@lists.alioth.debian.org