[sane-devel] [janitorial] Rescheduling 1.0.29

Olaf Meeuwissen paddy-hack at member.fsf.org
Thu Jan 2 11:49:46 GMT 2020

Hi all,

Thinking I'd give the list of release activities[1] a quick rundown to
see what can be done already, I noticed that I had pretty much totally
ignored what was written down there :-/

 [1]: https://gitlab.com/sane-project/backends/blob/master/doc/releases.txt

To make up for that, I've decided to push back the release to 2020-02-02
(a nice palindromic date, btw) and added a milestone[2] to the project.
I'll cut a release branch on 2020-01-12 (around 12:00UTC), when we enter
"Feature freeze".  Any changes on this branch will be merged back to
`master` after the release.  In the mean time, changes to `master` can
continue as usual.

 [2]: https://gitlab.com/sane-project/backends/-/milestones/3

I have gone through the open merge requests and issues and added those
that will be included.  For some of the assigned merge requests I have
contacted the assignee to check what should be done.

To make collecting content for the NEWS file a bit easier, I will go
through the closed issues and add those that led to code changes after
1.0.28 to the milestone.  Finally, I think I saw a few open issues that
can be closed but I need to double check.

Hope this helps,
Olaf Meeuwissen, LPIC-2            FSF Associate Member since 2004-01-27
 GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13  F43E B8A4 A88A F84A 2DD9
 Support Free Software                        https://my.fsf.org/donate
 Join the Free Software Foundation              https://my.fsf.org/join

More information about the sane-devel mailing list