anchor.diff:  == Affecting Labels and Milestones
   
   Affecting labels and milestones is very important in our process.
  -
  -Before each release, we check that we don't have any
  -closed issues that don't have either a milestone affected or
  -some of the "excluding" labels.
  -
  -Thus:
  -
  -* If you close a pull request because the committers have decided to not merge it,
  -  please add the appropriate `triage/` label: `triage/invalid`, `triage/out-of-date`,
  -  `triage/wontfix` are usually in order.
  -* If you close an issue because it has been fixed, either add the milestone
  -  if you can find it easily or use the `triage/out-of-date` if you can't.
  -* If you close an issue for any other reason, one of the aforementioned `triage/` labels
  -  is probably adequate.
  +The Quarkus Bot does it in most cases.
  +
  +In some cases, you might have to add some manually though:
  +
  +* If you close an issue that has not been closed automatically, either affect a milestone if it has been fixed
  +  or one of the `triage/invalid`, `triage/out-of-date`, `triage/wontfix` labels if not.
   * Some issues are created as `kind/bug` but are more support questions:
  -  in this case, remove the `kind/bug` label and add the `kind/question` label.
  +  in this case, remove the `kind/bug` label and add the `kind/question` label
  +  or even better redirect them to the Discussions section.
   
   [[backporting-process]]
   == Backporting Process
  
positive.code: 
  While not absolute, here is some advice:
  
  * If you really want a review by a specific person, make it a named reviewer via GitHub's "Reviewers" UI
  * If someone asked for a specific reviewer, better give some time for this person to review the PR.
    If not reviewed in a reasonable amount of time, better ping them again to have some information
    or ask the original author if we should go ahead.
  * If in doubt (on a specific part or because you're not comfortable reviewing documentation or any other reason),
  
negative.code: We partially rely on Dependabot for https://github.com/quarkusio/quarkus/blob/main/.github/dependabot.yml[a curated list of dependencies].
  
  Some dependencies are critical for Quarkus and quite complex.
  Good examples would be Netty, Vert.x or Hibernate ORM.
  
  It is good practice to update these core dependencies at the beginning of a given
  release cycle to let them time to bake in the main branch before being released.
  And, in any case, we should avoid upgrading these dependencies after the CR1 when we can.
  
  [[backward-compatibility]]
  == Backward Compatibility
  
  Quarkus evolves very fast and we decided we could break backward compatibility as long as:
  