Skip to content

Latest commit

 

History

History
52 lines (35 loc) · 1.75 KB

DEV_NOTES.md

File metadata and controls

52 lines (35 loc) · 1.75 KB
Raw

Notes for development

Unorganized notes which may be useful during development.

Release process (for tagged versions)

These are the "regular" versions, e.g., 0.4.0 or 0.4.0-RC1.

  1. Commit every change.
  2. Make sure there are no untracked files in git.
  3. Push any new commits.
  4. Wait for CI to become green.
  5. Tag the release (e.g., git tag -s "v1.2.3"), but don't push the new tag.
  6. In sbt, call release (requires Sonatype credentials).
  7. If everything looks right, push the new tag (git push --tags).
  8. Create a "release" on github for the new tag.

Release process for "hash" versions

These are "preview" versions, e.g., 0.4-39d987a.

  1. Commit every change.
  2. Make sure there are no untracked files in git.
  3. Push any new commits.
  4. In sbt, call releaseHash (requires Sonatype credentials).

Lincheck

A warning like this appears when running tests in stressLinchk:

OpenJDK 64-Bit Server VM warning: Sharing is only supported for boot loader classes because bootstrap classpath has been appended

According to https://stackoverflow.com/a/57957031, this is harmless.