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 Flocker 0.2.0 #795

Closed
wallrj opened this issue Sep 24, 2014 · 4 comments
Closed

Release Flocker 0.2.0 #795

wallrj opened this issue Sep 24, 2014 · 4 comments
Assignees
Milestone

Comments

@wallrj
Copy link
Contributor

wallrj commented Sep 24, 2014

No description provided.

@wallrj wallrj self-assigned this Sep 24, 2014
@wallrj wallrj added this to the Release 0.2 milestone Sep 24, 2014
@adamtheturtle
Copy link
Contributor

We have decided to do 0.1.3 first. When this is done the NEWS file can include the following (formatting and cleanup needed):

#498 - Flocker can be installed on OS X using Homebrew
#484 (and #622) - Documentation is now automatically spell-checked
#95 (with sub-tickets #568, #569, #586, #593) - Environment variables can now be passed to Docker containers
#567 - The Vagrant provider when following the tutorial is explicitly VirtualBox
#348 - A "Frequently Asked Questions" section has been added to the documentation
#560 - Documentation has a warning if it is not for a stable version
#91 (with sub-tickets #33, #201) - Network links can be added between containers
#46 (with sub-tasks #657, #658, #669) - Incremental ZFS sends allow a potentially significantly reduced amount of data to be sent between nodes

@adamtheturtle adamtheturtle removed their assignment Sep 24, 2014
@lukemarsden
Copy link
Contributor

I'd put the last two as headline features and the remainder as bugfixes/improvements.

@wallrj wallrj self-assigned this Sep 30, 2014
@lukemarsden
Copy link
Contributor

IOW, put the last two up first. Add formatting accordingly as you deem fit.

@adamtheturtle
Copy link
Contributor

This has been done, so I'm closing

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

Successfully merging a pull request may close this issue.

3 participants