Page History

...

• Monitoring the remote branches. Sometimes, there are remote branches created accidentally in the Apache Flink repo. Branches should generally been created in the forks. We might want to reach out to contributors to delete these accidentally created remote branches. The following branches shouldn't be touched:
  
  • master 
  • release-*
  • master 
  • experiment_gha_docs  & exp_github_actions (see Chesnay Schepler's comment in the related ML post)
  • dependabot/* (related ML thread)cron-master-dependency_check  & cron-master-maven_compat are still up for discussion and shouldn't be touched till decided

Jira maintenance

• Build failures should be reported in the corresponding Jira issue (or a Jira issue should be created if none exists, yet). Contributors should be pinged to fix instabilities as soon as possible to ensure a stable infrastructure of the course of the release cycle. More details on Jira issues can be found on the Flink Jira Process wiki page.
• Newly created Jira issue should follow the Flink Jira Process guide
• Jira issues should be correctly labeled with fixVersion, affectedVersion, component

...