Skip to content

Commit

Permalink
Tweaks to docs for the 0.6.pre2 release.
Browse files Browse the repository at this point in the history
I just noticed that the bytearray removal broke OHeap encoding.

I'm going to punt on that for this release.  Users have no need for
OHeap.
  • Loading branch information
Andy Chu committed Aug 19, 2018
1 parent 54020f3 commit 7756af0
Show file tree
Hide file tree
Showing 3 changed files with 18 additions and 2 deletions.
3 changes: 2 additions & 1 deletion benchmarks/report.sh
Original file line number Diff line number Diff line change
Expand Up @@ -88,7 +88,8 @@ all() {
osh-runtime
vm-baseline
ovm-build
oheap
# Commented out for the 0.6.pre2 release, where we removed bytearray.
#oheap
}

# For view
Expand Down
5 changes: 4 additions & 1 deletion doc/release-index.md
Original file line number Diff line number Diff line change
Expand Up @@ -80,10 +80,13 @@ Tree-shaking:
run compared to other shells?
- [Virtual Memory Baseline](benchmarks.wwz/vm-baseline/). How much memory to
shells use at startup?
- [OHeap](benchmarks.wwz/oheap/). Metrics for a possible AST encoding format.
- [OVM Build](benchmarks.wwz/ovm-build/). How long does it take for end users
to build Oil? How big is the resulting binary?

<!-- - [OHeap](benchmarks.wwz/oheap/). Metrics for a possible AST encoding format. -->

NOTE: OHeap was broken in this release due to the removal of `bytearray`. It
may be back in the future.

<!-- TODO:
/src/ annotated/cross-referenced source code
Expand Down
12 changes: 12 additions & 0 deletions scripts/release.sh
Original file line number Diff line number Diff line change
Expand Up @@ -49,6 +49,18 @@ log() {
echo "$@" 1>&2
}

# For redoing a release. This is everything until you have to 'git pull' the
# benchmark-data repo to make reports.
auto-machine1() {
$0 build-and-test
test/wild.sh all
$0 test-opy
$0 spec-all
$0 metrics
$0 benchmark-run
$0 benchmark-run-on-1-machine
}

# TODO:
# - enforce that there is a release/$VERSION branch?

Expand Down

0 comments on commit 7756af0

Please sign in to comment.