public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
Cc: isar-users@googlegroups.com
Subject: Re: isar git repository - hash changed
Date: Fri, 25 Nov 2022 11:58:46 +0300	[thread overview]
Message-ID: <01643749-b9ff-3c93-d8af-8df9767f65cf@ilbers.de> (raw)
In-Reply-To: <CAJGKYO4OnbtGW6X0HY2LmiQLpk4cdHavG+i_mnj53xRJK6260Q@mail.gmail.com>

25.11.2022 11:41, Roberto A. Foglietta wrote:
> I saw the document, the following and there is a typo about Continuous:
>
> next is a branch for CI (Continous Integration), testing and early feedback.
>
> means that - if a commit does not pass the CI, testing or users review
> (feedback), it could be removed?
>
> So, the "next" is not a stable branch in the sense that every hash in
> it will remain forever. Isn't that right?
>
> While in the master branch every commit (hash) remains forever. Is that right?
>
> Best regards, R-

Yes, this is how it supposed to be. But currently we are checking every 
commit
on CI at least once even before applying to 'next'. And after applying 
we also
performing CI on daily basis to ensure there are no floating issues, and 
also
there are no complains from downstreams.
Only after that commits are going to 'master'. It means 'next' is quite 
stable
for use, but "no changes" state is not 100% guaranteed.


      parent reply	other threads:[~2022-11-25  8:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-24 23:54 Roberto A. Foglietta
2022-11-25  6:50 ` Anton Mikanovich
2022-11-25  8:05   ` Roberto A. Foglietta
2022-11-25  8:30     ` Anton Mikanovich
2022-11-25  8:41       ` Roberto A. Foglietta
2022-11-25  8:50         ` Baurzhan Ismagulov
2022-11-25  9:04           ` Roberto A. Foglietta
2022-11-25  8:58         ` Anton Mikanovich [this message]

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=01643749-b9ff-3c93-d8af-8df9767f65cf@ilbers.de \
    --to=amikan@ilbers.de \
    --cc=isar-users@googlegroups.com \
    --cc=roberto.foglietta@gmail.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