From: Anton Mikanovich <amikan@ilbers.de>
To: isar-users@googlegroups.com, "Kowalsky,
Clara (FT RPD CED OES-DE)" <clara.kowalsky@siemens.com>
Subject: Re: Decide on official Isar release cycle
Date: Tue, 16 Dec 2025 09:58:51 +0200 [thread overview]
Message-ID: <b67d5a04-9010-439d-9f36-34945c664229@ilbers.de> (raw)
In-Reply-To: <bc956063-d79d-4a38-b60d-5b8b5570c036@siemens.com>
16/12/2025 09:37, 'Clara Kowalsky' via isar-users wrote:
> Hi,
>
> last week at the Isar Community Meetup, the desire was expressed to
> finally have a v1.0 Isar release to demonstrate project maturity, as
> well as to have more releases per year, ideally quarterly.
> So far, the approach has been to release approximately one minor
> release per year, which brings us to v0.11 at present.
> My suggestion would be to follow a similar approach as Debian and have
> a major release every two years, along with a minor release every
> quarter.
>
> How should we proceed? Which strategy do we want to establish?
> Ideally, we could release the first major version in January and then
> proceed with a quarterly cycle.
>
> Best regards,
> Clara Kowalsky
>
Hello Clara,
I think Isar is looking stable enough to have v1.0 release.
But we should choose the date carefully, because it will require some
pre-release work (like retesting all the targets) every year on this period.
Some steps I hope will be automated soon, while some still require manual
involving.
Also following should be taken in account:
- Incomming commits activity. It is usually variable during the year.
- Debian releases. Few months after and before Debian release date don't
look
like stable base point.
- Any holidays when people can be on vocations.
Having all this in mind my suggestion is February.
Regarding the period of releases not sure we need to have 4 minor
releases per
year, because preparations will probably be the same as for major ones.
Maybe
having one stable release every year will be more useful and will allow
to have
some big changes more "polished" to the moment of the release.
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/b67d5a04-9010-439d-9f36-34945c664229%40ilbers.de.
next prev parent reply other threads:[~2025-12-16 7:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-16 7:37 'Clara Kowalsky' via isar-users
2025-12-16 7:58 ` 'Jan Kiszka' via isar-users
2025-12-16 7:58 ` Anton Mikanovich [this message]
2025-12-16 8:06 ` 'Jan Kiszka' via isar-users
2025-12-16 10:53 ` Baurzhan Ismagulov
2025-12-16 11:36 ` 'Jan Kiszka' via isar-users
2025-12-16 12:27 ` Baurzhan Ismagulov
2025-12-16 13:14 ` 'Jan Kiszka' via isar-users
2025-12-16 11:42 ` 'Andreas Naumann' via isar-users
2025-12-16 11:28 ` 'Andreas Naumann' via isar-users
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b67d5a04-9010-439d-9f36-34945c664229@ilbers.de \
--to=amikan@ilbers.de \
--cc=clara.kowalsky@siemens.com \
--cc=isar-users@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox