Hi,
On 2021-08-18 3:25 a.m., Povilas Kanapickas wrote:
On 8/17/21 8:11 PM, Ralph Little wrote:
Hi,
OK, seems like we have an appetite for a release.
Since this is the first time we have done this without Olaf, I suggest
that we give ourselves plenty of time to figure out the ropes.
I propose the following timeline:
Feature Freeze - Sept 24
Code Freeze - Oct 7
Release - Oct 14
I propose that we omit code freeze stage on Oct 7 and instead start a
release branch at around that time. This way the master branch continues
to be open for changes and we don't need to hurry to do the actual release.
I also suggest that we do one or more release candidates. This way
significant issues can be caught before we release to the wide public.
My suggested timeline is this:
Feature Freeze - Sept 24
Release branch created, master is open for new changes - Oct 7
Release-candidate released - Oct 7
Either the final release or a next release candidate depending on the
number and seriousness of new bugs filled: Every two weeks after that
I can manage all the dance with the creation of release branches and
release candidates.
Since the majority of users get their releases from their distros, who
for the most part seem pretty conservative about their SANE releases, do
you think we would get sufficient buy-in from distros for the release
candidates to get much exposure?
I can certainly cut an RC release on the sane-release PPA so that people
using that can get a taster.
Also we would need a phase before the first release candidate is
generated to get translations in. That could be between Sept 24 and the
first release candidate I guess, but before we had a specific period of
time for translation where we wouldn't be expecting to see code changes.
Looking back now, I wonder if my proposed start for the timeline is too
conservative at Sept 24th. That's more than a month away.
This was mostly chosen as I have some stuff going on over the next few
weeks that will mean that I am away for a few days.
Let's keep it that way though as we are few and we're also busy people :D
This follows a similar timeframe to our previous release, but with a
longer lead time to the start of the process to allow us to figure it
all out. It also keeps the month dates similar to before.
I will try to assemble the tasks in the meantime.
If anyone wishes to take on any of the release tasks then feel free to
step forward!
From what I can think of from the top of my head:
- Calling for translations
- Building the changelog
- Updating the PPAs and creating a 1.0.33 on sane-release (which I will do)
- Creating a milestone on GitLab to assign all relevant issues/MRs to
- Other things that I have probably forgotten about.
This sounds about right.
I also found Olaf's doc/releases.md file which seems to summarise what
he used to do quite nicely.
For the changelog I propose we adopt a tool like
https://github.com/twisted/towncrier which allows to build release notes
during the development process instead of scrambling to do that just
before release.
I would build the initial release notes before the release.
I'll check it out.
Cheers,
Ralph
