What is the nature of the bug fix? Is it going to cause scanners that worked with the prior release to be broken with this one? How big is the fix? How likely to cause regressions?
allan On Fri, May 19, 2017 at 5:13 AM, Rolf Bensch <r...@bensch-online.de> wrote: > Are we already in Code Freeze? > > I would like to commit a bug fix this weekend. > > Rolf > > > Am 28.04.2017 um 14:04 schrieb m. allan noah: >> Ok folks, it's time to get another sane-backends release out the door. >> >> Olaf has done a good job of cleaning up our contributors list and >> curating the bug tracker. However, there are a handful of patches in >> the bug tracker that could still be applied, once they are reviewed. >> Also, quite a number of backends that are now unmaintained. So, this >> is a good time to get involved with sane. If you benefit from this >> project, and have some programming experience, we could use the help. >> >> Schedule: >> >> May 7: Feature freeze (only fix bugs and update docs after this date) >> May 14: Code freeze (only update docs after this date) >> May 21: Release >> >> Any questions or concerns, let me know. >> >> 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
