Release v0.6

[yuvipanda]

I want us to try to experiment with time based releases of z2jh, possibly at a 6-8 week cycle. This has several advantages:

1. Forces us to document and automate the release process, so people other than me can do releases
2. Get fixes into the hands of users more quickly
3. Help with a roadmapping process later on.
4. Make upgrades easy and painless for users

To that end, I propose we try to release v0.6 on Jan 24, which is a wednesday close to 6 weeks from when we tagged v0.5 (Dec 13). Whatever makes it by then makes it, and if something doesn't that's ok!

Objections? I'm going to start tagging things as v0.6 and working on them :)

[yuvipanda]

The primary theme I see for 0.6 so far is bug fixes and features that enable autoscalers to work better.

[choldgraf]

+1 to this, I can take a pass and look at the milestone issues today or this weekend as well!

[yuvipanda]

As a note, I really like this workflow! Having clear 'what next to work on?' makes it easy to make PRs that have good impact.

[choldgraf]

Perhaps at the next meeting we can discuss the primary action-items on the v0.6 milestone?

[yuvipanda]

Currently set release date for it is before the next meeting.

…

On Jan 13, 2018 8:32 AM, "Chris Holdgraf" ***@***.***> wrote: Perhaps at the next meeting we can discuss the primary action-items on the v0.6 milestone? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#392 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAB23qtcjWQ1hbu-Op6gCHfUVY6JhlPUks5tKNqngaJpZM4RbZs9> .

[choldgraf]

well then for the next release :-) --

…

On Sat, Jan 13, 2018 at 9:20 AM Yuvi Panda ***@***.***> wrote: Currently set release date for it is before the next meeting. On Jan 13, 2018 8:32 AM, "Chris Holdgraf" ***@***.***> wrote: > Perhaps at the next meeting we can discuss the primary action-items on the > v0.6 milestone? > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > < #392 (comment) >, > or mute the thread > < https://github.com/notifications/unsubscribe-auth/AAB23qtcjWQ1hbu-Op6gCHfUVY6JhlPUks5tKNqngaJpZM4RbZs9 > > . > — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#392 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABwSHeR7a8d6o7KFDAvEqoceL7XW3CnOks5tKOX7gaJpZM4RbZs9> .

[yuvipanda]

I am going to count end of this week as 'feature freeze' date, and then focus only on testing, documentation and polish after that.

[choldgraf]

@yuvipanda can I help w/ drafting a release document etc? There are still a few issues to finish up but I can work on the release comms material and then we can 🚢 it ~ on time

[yuvipanda]

@choldgraf yes! Can you look at the git log since last release and start a hackmd with changelog? I can edit and pick cricketer (you are also welcome to pick cricketer!)

[yuvipanda]

Since we've had two male cricketers so far, I think we should either pick a female cricketer this time.

[choldgraf]

I've started putting together pieces for a release here:

https://hackmd.io/BwJghgxgjAnCAsBaYAGeBmR8CmB2GyAbIRIjAEbooAmKEMAZrmOUA===?both

It's currently got a suggested cricketer, a list of the (non merge) commits, and some highlights I pulled outta there. I probably missed some stuff, so please add comments as you think of them!

[willingc]

Close #467