Discussion
Discussion copied to clipboard
vuejs
1.0 plans
As many of you know, 0.12 is planned to be the last point release and I believe Vue is in a stable enough state to consider a 1.0 in the near future. There's no date guarantee yet, but I want to make the upgrade process as pain-less as possible. Ember's recent 2.0 release has made a good example, so here's the brief plan for the road to 1.0:
1.0.0-alpha
The alpha versions will introduce no breaking changes. Anything that runs in ^0.12.10 should run in 1.0.0-alpha. However, the alpha versions will start to raise deprecation warnings on features that will be droped/changed in 1.0.0. You can consider 1.0.0-alpha a continuation of 0.12 but with deprecation warnings; its purpose is to allow you to use it in any 0.12.10 compatible app without any refactoring, but clearly know what features you are using will be deprecated in the future.
New features / replacements of the deprecated features will also land in the alpha. It allows you to gradually migrate to new features at a pace you see fit. For details on planned changes/deprecations in 1.0, see issue tracking in core.
1.0.0-beta
Beta versions will start to gradually remove the deprecated features; The final beta release would have removed all deprecated features. The purpose of the beta is stability testing; it's expected to be used by early-adopters to ensure it works properly in real applications.
1.0.0
1.0.0 will simply be a symbolic release that makes it official so that we can celebrate! Also, if your app works without raising deprecations in 1.0.0-alpha, it should work in 1.0.0.
So that's the plan, let me know what you think - if you have suggestions that requires breaking the current API, now is the time to make it heard!
I've already started using 0.12 in some of our internal production applications and am excited for a 1.0 release! We're currently in the process of defining a new technology stack for future development and Vue is the front-runner for data model binding. I know you said there's no date guarantee but was wondering if you had any expectations on a 1.0 beta. Do you think it's reasonable we'd see a 1.0 beta within the next few months?
With the number of changes proposed, would it not make sense to go to 0.90 or something rather than to 1.00alpha - or is this in the hopes of getting more attention?
@Mat-Moo I think @yyx990803 was saying that there won't be many changes. He declared that anything running 0.12.0 should run in 1.0.0
If that's true, it makes sense to move to 1.0 now, and start adding the .1, .2 features in the future.
Lets look a few month into the future. 1.0.0 is already out, 1.1.0 is upcoming, but my project is still sitting on the latest 0.12.10, because I didn't have time to migrate during 1.0.0-alpha stage.
Then suddenly I get some spare time to work on this project. So the migration route for me is:
- Move to 1.0.0-alpha, nothing should break
- Fix things that cause deprecation warnings
- Move to 1.0.0, test thoroughly
Now look, wouldn't it be meaningful to publish 1.0.0-alpha as 0.13.0 when 1.0.0 comes out? So that people wouldn't have to migrate to a shiny new 1.0.0 though obscure alpha.
Move to 1.0.0-alpha, nothing should break
Why can't you just "Move to 1.0.0, test thoroughly" directly?
@mark-hahn 1.0.0-alpha is compatible with 0.12, but gives hints on things you need to fix before moving to 1.0.0. That's the point of alpha as I see it. And I do not see another way to gradually migrate a large scale project.
Together with 1.0.0 we will also release a version called 1.0.0-migration, which serves the same purpose, but updated with all changes between alpha and 1.0.0, if any. That version should be the go-to version for post 1.0 migration. On Tue, Sep 1, 2015 at 2:25 AM Denis Karabaza [email protected] wrote:
@mark-hahn https://github.com/mark-hahn 1.0.0-alpha is compatible with 0.12, but gives hints on things you need to fix before moving to 1.0.0. That's the point of alpha as I see it. And I do not see another way to gradually migrate a large scale project.
— Reply to this email directly or view it on GitHub https://github.com/vuejs/Discussion/issues/347#issuecomment-136597789.
That's the point of alpha as I see it.
It usually means just an early release of something new. It usually has no other meaning. In hardware products alpha testing is in-house and beta testing is at the customer's location.
On Mon, Aug 31, 2015 at 11:33 PM, Denis Karabaza [email protected] wrote:
@yyx990803 https://github.com/yyx990803 that will do the trick, thanks!
— Reply to this email directly or view it on GitHub https://github.com/vuejs/Discussion/issues/347#issuecomment-136599494.
@mark-hahn there is no field for interpretation and discussion.
You can consider 1.0.0-alpha a continuation of 0.12 but with deprecation warnings; its purpose is to allow you to use it in any 0.12.10 compatible app without any refactoring, but clearly know what features you are using will be deprecated in the future.
there is no field for interpretation and discussion.
I wasn't arguing. I was just explaining my earlier question.
On Tue, Sep 1, 2015 at 11:33 AM, Denis Karabaza [email protected] wrote:
@mark-hahn https://github.com/mark-hahn there is no field for interpretation and discussion.
You can consider 1.0.0-alpha a continuation of 0.12 but with deprecation warnings; its purpose is to allow you to use it in any 0.12.10 compatible app without any refactoring, but clearly know what features you are using will be deprecated in the future.
— Reply to this email directly or view it on GitHub https://github.com/vuejs/Discussion/issues/347#issuecomment-136821837.
你好。1.0 与现在0.12版本变更是否很大？ 新项目建议从何处开始？各组件是否已成熟可以直接支持1.0.0？ 例如 vue-router等
