Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release 0.2.0 #1641

Closed
18 of 20 tasks
SeanTAllen opened this issue Oct 16, 2017 · 6 comments
Closed
18 of 20 tasks

Release 0.2.0 #1641

SeanTAllen opened this issue Oct 16, 2017 · 6 comments
Assignees
Milestone

Comments

@SeanTAllen
Copy link
Contributor

SeanTAllen commented Oct 16, 2017

For tracking work related to the 0.2.0 release of Wallaroo.

Release Target

We are aiming to release 0.2.0 by EOD Wednesday to coincide with the blog post John will be posting Thursday morning.

Testing Process Round 1

The testing process should begin ASAP and should be completed by 12PM EST on Tuesday 10/17. Testing includes: running through the instructions below and opening any issues that you may run into during the testing process.
Please file separate issues for each problem you encounter under the 0.2.0 release milestone.

Installation Instructions

Follow the instructions for setting up and installing Wallaroo.

  • OSX - Jonathan
  • Xenial - Scott
  • Trusty - Sean

Run a Wallaroo Application

Find instructions here

  • OSX - Jonathan
  • Xenial - Scott
  • Trusty - Sean

Examples

Run through all the Python examples and make sure they work. This means everything in examples/python.

Making Sure it Works:

  • Building and running all examples/python applications

    • verifying all applications build and run as expected
    • verifying memory stays within an expected range. Memory for machida applications should be in the 50mb-150mb range conservatively. You can run the application for 5 mins and if you see a memory value that you're uncertain about, please open an issue so we can compare across OS's and get a definitive answer on whether it should be considered memory growth or not.
  • OSX - Jonathan

  • Xenial - Scott

  • Trusty - Sean


Testing Process Round 2

The testing process should begin ASAP once ponyc 0.20.0 has been released and documentation on the release-0.20.0 branch has been updated. Testing should be completed by 12PM EST on Wednesday 10/18. Testing includes: running through the instructions below and opening any issues that you may run into during the testing process.
Please file separate issues for each problem you encounter under the 0.2.0 release milestone.

Installation Instructions

Follow the instructions for setting up and installing Wallaroo.

  • OSX - Jonathan
  • Xenial - Scott
  • Trusty -Jonathan

Run a Wallaroo Application

Find instructions here

  • OSX - Jonathan
  • Xenial - Scott
  • Trusty - Jonathan

Examples

Run through all the Python examples and make sure they work. This means everything in examples/python.

Making Sure it Works:

  • Building and running all examples/python applications

    • verifying all applications build and run as expected
    • verifying memory stays within an expected range. Memory for machida applications should be in the 50mb-150mb range conservatively. You can run the application for 5 mins and if you see a memory value that you're uncertain about, please open an issue so we can compare across OS's and get a definitive answer on whether it should be considered memory growth or not.
  • OSX - Jonathan

  • Xenial - Scott

  • Trusty - Jonathan


After Testing is Complete

If there are any issues, we will discuss during sync whether to continue to fix and push back the release or move forward and cut the release that day.

Cutting a Release

If we agree to release during sync, a release will be cut by @SeanTAllen Wednesday evening.

Release Checklist

  • merge release-0.2.0 branch into the release branch
  • give gitbook at docs.wallaroolabs.com cursory glance to verify the gitbook update was pushed successfully

Vagrant Notes

If you are testing with Vagrant, you'll want to give 4 gigs of memory to virtualbox, this is done by adding something like the following to your Vagrantfile:

  config.vm.box = "ubuntu/xenial64"

  config.vm.provider "virtualbox" do |v|
    v.memory = 4084
  end

where

  config.vm.provider "virtualbox" do |v|
    v.memory = 4084
  end

is what you'll be adding.

When you first spin up your vagrant virtual box, run this command:

sudo swapon -s

If you don't have swap enabled, do the following:

sudo fallocate -l 4G /swapfile
sudo chmod 600 /swapfile
sudo mkswap /swapfile
sudo swapon /swapfile

or else you'll hit an OOM issue when building Machida.

@SeanTAllen
Copy link
Contributor Author

release-0.2.0 branch has been created.

documentation is up on gitbook at https://www.gitbook.com/book/wallaroo-labs/wallaroo-release-candidate/details

@SeanTAllen
Copy link
Contributor Author

@slfritchie the key for ponyc binary for running:

sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys "8756 C4F7 65C9 AC3C B6B8 5D62 379C E192 D401 AB61"

is incorrect.

I am opening an issue to fix.

@SeanTAllen
Copy link
Contributor Author

SeanTAllen commented Oct 16, 2017

I'm unable to build Machida on a stock Trusty install. Looking into it. Linker errors.

Here's the ticket for the fix:

#1645

@SeanTAllen
Copy link
Contributor Author

SeanTAllen commented Oct 16, 2017

@JONBRWN ran into an issue on OSX. I've opened a PR against ponyc homebrew recipe to address:

Homebrew/homebrew-core#19522.

EDIT decided homebrew was the wrong place to do that change. Opened a Pony PR instead:

ponylang/ponyc#2284

@JONBRWN
Copy link
Contributor

JONBRWN commented Oct 17, 2017

First round of testing is complete, 2nd round is delayed until ponylang/ponyc#2284 is merged and released via the proper channels (brew/apt)

@SeanTAllen
Copy link
Contributor Author

Pony 0.20.0 has been released: https://www.ponylang.org/blog/2017/10/0.20.0-released/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants