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 Luca <[email protected]> wrote: > 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 > [email protected] > > > -- > sane-devel mailing list: [email protected] > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel > Unsubscribe: Send mail with subject "unsubscribe your_password" > to [email protected] -- "well, I stand up next to a mountain- and I chop it down with the edge of my hand" -- sane-devel mailing list: [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel Unsubscribe: Send mail with subject "unsubscribe your_password" to [email protected]
