RMI / RMI/practices

No releases on Friday

Open
#48 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
3
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Something we just agreed to on PBTAR, but it warrants documenting.

We have a release branch cut and approved and ready to push to PROD but will delay it to Monday morning so we don’t end up with any weekend surprises. 

I think this should be a common practice/rule for SPD (i’ll add an issue on practices)

Cc @AlexAxthelm @lloyd-rmi @mbarlow12

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file, test, or entry point is named. Start by inspecting the repository's existing practice and release documentation to find the appropriate location and conventions. Done means the agreed rule to delay approved releases until Monday is documented clearly and consistently.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.