semver & git inspired upgrade flow
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- git
- Domain
- release
Research direction
Start by examining how global improvement proposals currently govern changes, then map the proposed individual branches into dev and main. Define the semantic-version release process, such as dorg-2.1.0, and document what proposal-gate, branch, and release behavior would count as complete.
Written by the indexing model from the issue text.
Description
Rather than having every change to the DAO happen through global "improvement proposals", we could have a more open process where anyone can push modifications to individual branches which ripple up to a dev branch that can only be merged to main through a proposal.
We could also use semantic versioning to track updates to the DAO as releases (e.g. dorg-2.1.0).
- Dominant language
- No language data
- Stars
- 1
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from dOrgTech/DIPs
Similar issues
-
Help-Wanted Needs-Triage Package-Request
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
microsoft/winget-pkgs#438680 ·
-
package-update
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
oSoWoSo/vOid_Community_repOsitory#148 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
documentation pkg infrastructure
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
epiverse-trace/epiparameter#511 ·