[sane-devel] Entering code freeze (was Re: [janitorial] Let's release 1.0.31 in August)
paddy-hack at member.fsf.org
Sun Aug 16 13:35:15 BST 2020
Olaf Meeuwissen writes:
> Hi all,
> Olaf Meeuwissen writes:
>> Hi all,
>> I've been dragging my feet of late. Not just as far as the SANE Project
>> is concerned but in general. For one reason or another I just can't get
>> myself to do much after I get home from work ... :-/
>> Let's see if I can change that a bit by upping the pressure (on myself)
>> and announce intent to release sane-backend-1.0.31 sometime next month.
>> That would keep us on track for a roughly half-yearly release cycle, not
>> counting security bug fix releases like 1.0.30.
>> In keeping with what's in our `doc/release.txt` (minus a day or two), I
>> would like to proceed along the following timeline
>> 2020-07-21 Kick-off
>> 2020-08-02 Feature Freeze (-> cut release/1.0.31 branch)
> I just cut the release/1.0.31 branch.
> If there's any bug fixes or documentation/translation updates you want
> to get into 1.0.31, make sure to target that branch.
> Any feature additions should go to master, as usual.
>> 2020-08-16 Code Freeze
Just want to let you know that we've entered code freeze for 1.0.31.
As per long tradition this means that
only fixes for hardware destroying bugs, compile failures, fixing
completely unusable backends and documentation fixes are allowed
to enter the release/1.0.31 branch now.
# Cutting release branches is something rather recent though.
Any other changes can still go to master any time they're deemed ready.
There is still one (re)opened issue on the milestone but I think the
(additional) changes are not a show-stopper for 1.0.31. Trying to get
the remaining problems on that issue on a separate issue as I write.
>> 2020-08-23 Release
BTW, aiming for a release around 12:00 UTC.
That works nicely for me because it's around 21:00 my time ;-)
>> You can find a milestone for 1.0.31 at
>> I'll be adding issues fixed and merge requests to be included or already
>> included in the coming weeks and hope to finish that before the feature
>> freeze. Help with that chore is welcome by the way.
> I think I've added all merged merge requests between 1.0.29 (remember,
> 1.0.30 was a security bug fix and was merged to master) and the point
> where I cut release/1.0.31 to the milestone. I also think I've added
> all closed issues that resulted in code changes. The ones with merge
> requests were easy to find but I may have missed issues without any.
> If you find any such issues, please set their milestone. The list of
> possible issues is at
> and you're looking for the issues that were last updated after 1.0.29
> was released, i.e. 2020-02-02.
> I've already merged the Ukranian message updates, thanks Yuri!, and am
> just done syncing the po/*.po files with the latest code.
> FTR, French and British English were updated on master already before I
> cut release/1.0.31 but I have taken the liberty to bump the version and
> date and last translater in their *.po files where appropriate.
>> # FTR, I'll be mostly off-line during the August 12-16 period.
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