Rough estimation dates in roadmap/Release policy

microsoft / TypeScript

TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

https://www.typescriptlang.org

Apache License 2.0

100.24k stars 12.39k forks source link

Rough estimation dates in roadmap/Release policy #7651

Closed donaldpipowitch closed 7 years ago

donaldpipowitch commented 8 years ago

Hi, this is a documentation feature request: Could we add a rough estimation date on the roadmap? No fixed date. Maybe the estimated month or at least the season? It would be nice to know if 2.0 means "summer 2016" or "by the end of 2017".

raybooysen commented 8 years ago

Would love to see this. We're looking at features in 2.1 and would like a general ballpark idea of when these versions will appear.

mhegazy commented 8 years ago

We try to keep releases 6-8 weeks apart. last 1.8 went out a week ago. Will look into adding dates on the roadmap as well.

donaldpipowitch commented 8 years ago

Thank you!

NoelAbrahams commented 8 years ago

@mhegazy, I would like to see a pre-release of --strictNullChecks if possible. At present it's only available in the nightlies. A pre-release would get you input from a wider audience.

Also, when you say "1.8 went out a week ago" I only see the last release available for visual studio as 1.8.5 released 22 days ago.

mhegazy commented 8 years ago

We are definitely planning a pre-release. we just need to land the emitter work as well (https://github.com/Microsoft/TypeScript/issues/5595).

and 1.8.9 is the last one actually.

NoelAbrahams commented 8 years ago

@mhegazy, okay, thank for the update.

My question was: "Is there a VS plugin for 1.8.9?"

This is all I see:

mhegazy commented 8 years ago

yes. :D once it is available, I will update the release page.

mhegazy commented 8 years ago

the trick here is synchronizing multiple things at the same time, VSCode releases, VS releases, new language features, etc.. so it is not always easy to give concrete information/dates all the time.

mrmckeb commented 8 years ago

@mhegazy I've noted that 2.0 is the next release, and there's nothing between that and 1.8. Does that mean we should expect 2.0 in the coming weeks? Like @raybooysen, I'm also working on a project that could benefit greatly from some of the 2.1 features.

It would be great to have a rough idea of release dates, as this would help when deciding if TypeScript is right for a project.

mhegazy commented 8 years ago

I've noted that 2.0 is the next release, and there's nothing between that and 1.8. Does that mean we should expect 2.0 in the coming weeks?

TS 2.0 is the next release. I do not believe it is ready to be out in the next few weeks. i would expect 4-6 weeks for a public release (likely TS 2.0-beta). We are currently looking into TS 2.1 planning and i should have more information to share soon.

I'm also working on a project that could benefit greatly from some of the 2.1 features.

what features are you specifically looking for?

mrmckeb commented 8 years ago

Hi @mhegazy, understood. It looks like there's a lot going in to 2.0!

The absolute biggest feature I'm after is "Support ES8 object property spread and rest". It will increase readability of apps greatly, especially when using Redux (which we are). Babel supports this already, but I understand they don't have types to worry about.

I followed the link (issue #2103) and can see that I'm not the only person seeking this feature, but I understand it may be too late to get it into 2.0.

mhegazy commented 8 years ago

We might be able to get this done in 2.0.

mrmckeb commented 8 years ago

That would be great, as it's a killer feature. Thanks for your time @mhegazy!

jaime-olivares commented 8 years ago

The Asp.Net Core project had a clear roadmap with release dates (see https://github.com/aspnet/Home/wiki/Roadmap). I think you should have something similar instead of few rumors in the Issues section.

donaldpipowitch commented 8 years ago

I'd love the see a different release policy for TypeScript in the future. I'm a little bit unhappy about how 2.0 will be released.

Maybe TypeScript could adopt Embers pattern:

Say the current version is 1.x.y.
Release new features as 1.(x + 1).y. If they are very experimental make them only available behind a feature flag.
Release bug fixes as 1.x.(y + 1).
Deprecate old features (warn about usage).
Use a major version bump to 2.0.0 only to remove deprecated features. If you have no deprecation warnings in the latest 1.x version, you should upgrade to 2.0.0 without an error. Don't introduce new features.

What TypeScript currently does with 2.0:

Bug fixes are not released separately in patch versions, but as major versions (see https://github.com/Microsoft/TypeScript/issues/7566#issuecomment-217971515).
New features are released in one big bang. This makes upgrading harder and slows down adoption of new features, which are already finished.
No clear deprecations (?)

// cc @otbe

donaldpipowitch commented 8 years ago

@mhegazy Will there be a new release policy in the post-2.0-era?

mhegazy commented 8 years ago

yes. I should be updating the roadmap with tentative release dates in the next few days. so stay tuned.

donaldpipowitch commented 8 years ago

Nice, thank you!

mhegazy commented 7 years ago

Thanks for the feedback. Road map should be updated now to reflect the plan for TypeScript 2.1, also including planned release dates. we are currently targeting November 2016 for this release. moving forward we will include planned release dates for milestones as they appear.