# 1.0.0 Release Planning
Permalink: https://hackmd.io/@porter/v1-release-planning

## Agenda
* Timeline and remaining issues
* https://github.com/getporter/porter/milestone/16
* Yingrong has been vetting remaining bugs
* Possible errors users WILL see, we need docs ready to support these
* Data migration required
* Version mismatch of plugins/mixins
* Schema version mismatch of resources (e.g. installation, parameter set)
* Alpha
* 1.0.0-alpha.20 was last alpha release
* No more planned schema changes
* Do we need an alpha release for the latest bundle dependency change in the bundle format?
* No we can release it in beta.1 and just not make further changes going forward.
* If we end up needing dependency changes later, we need to queue that up for v2.
* Beta
* Starting with beta.1 porter supports migrating existing data from v0.38
* If we make any schema changes from now on, we have to suport migrating existing users
* Someone should be able to use their current data with beta onwards though our final release
* Data Migration
* New PORTER_HOME
* We don't touch old data so that you can go back if needed
* `porter storage migrate --old-home ~/.porterv0`
* Identify who are our beta testers
* Release Candidate
* Starting with rc.1 we should have made ALL planned changes
* We stay in rc until people stop reporting must fix bugs
* Must fix = security, or blockers
* Identify RC testers and who can help us decide that we've vetted the RC "enough"
* What is the minumum amount of time an RC should be out before we can promote it to 1.0.0?
* Release Process - What needs to happen to cut a v1.0.0 release
* Once we have a viable RC, we will retag that same commit as 1.0.0
* Branches (main, release/v1, release/v0.38.*), timing of when we move release/v1 to main
* Website (domain, versioning)
* Plugin and mixin releases should be coordinated.
* All plugins are now at 1.0.0-beta, and will go to 1.0.0 when we release
* The exec mixin will automatically go 1.0.0 with Porter
* Are there other mixins that should go 1.0.0?
* Update plugin and mixin pages with compatibility ranges
* Announcement
* blog posts
* Announce release and explain migration
* Revisit major features and changes?
* Mega rollup or separate?
* social media
* We will do a series of tweets about the key points in the blog posts
* Ask CNCF to retweet the 1.0.0 announcement
* homepage refresh
* List adopters with logos on homepage
* Make sure our features listed still make sense
* Improve/hone the explanation of what Porter is
* Highlight CNCF sandbox? (double check sandbox promotion rules)
* Gifs and Videos
* CNCF webinar
* Where are we with F5 on their own promotion around their usage?
* SLA and support expectations
* How long do we support v0.38? What constitutes "support"?
* No internal teams are using v1.0 yet.
* EY is going to start evaluating v1.0 after we hit beta.1 and support migrations
* F5 is dogfooding v1.0