added RELEASE-PROCESS.md and draft of next release note

catmando · catmando · commit 46d271dd9214 · 2021-03-31T14:43:28.000-04:00
diff --git a/RELEASE-PROCESS.md b/RELEASE-PROCESS.md
@@ -0,0 +1,11 @@
+To release a new gem set:
+
+1. Make sure CI is passing
+2. Do a global search for `VERSION = '1.0.alpha1.<current point release>'` and replace with the next point release.
+3. Add a new row to `/current-status.md` with the current data
+4. Add a new file in `/release-notes` (see existing files for format)
+5. Update `README.md` with last entry from `current-status.md`
+6. Commit all the above. <- VERY IMPORTANT TO DO THIS BEFORE ADDING THE TAG
+7. `git tag 1.0.alpha1.<new point release>`
+8. `git push origin edge` <- once build passes gems will be released!!!
+9. Add a new release note (add release in git hub): Copy contents of the release note you created
diff --git a/release-notes/1.0.alpha1.7.md b/release-notes/1.0.alpha1.7.md
@@ -0,0 +1,24 @@
+## 1.0alpha1.7 - 2021-03-29
+
+| Release<br/>Date | Version | Open<br/>Issues | Documentation<br/>Sections<br/>Draft Ready | Documentation<br/>Sections<br/>WIP |
+|--------------|---------|-------------|-------|------|
+| April 5, 2021 | 1.0.alpha1.6 | 167 | 35 | 10 |
+
+> Open issues includes enhancements, documentation, and discussion issues as well as few bugs.
+>
+> The documentation WIP (work in progress) numbers are approx, as more sections may be added.
+
+### New Major Features
++
+
+
+### Breaking Changes
++ [#396](https://github.com/hyperstack-org/hyperstack/issues/396) Fixed: Rejected promises do not move operations to the failure track
+
+### Security
+
+### Added
+
+### Fixed
+
+### Deprecated
