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 dates in the Roadmap #10450

Closed
olegchir opened this issue Aug 20, 2016 · 5 comments
Closed

release dates in the Roadmap #10450

olegchir opened this issue Aug 20, 2016 · 5 comments
Labels
Question An issue which isn't directly actionable in code

Comments

@olegchir
Copy link

The Roadmap on GitHub contains no release dates.
Could you please estimate and fill in dates for 2.0 and 2.1?

Sorry for not using standard bug template, but I feel that this question shouldn't be on Stackoverflow, because it's a strategic question for the team.

The Rules of our company (and I believe we are not alone) don't allow us the use of pre-release versions. For new projects, the gap between 1.8 and 2.x may be too large, and It may lead to the use of fundamentally incorrect design decisions. It would be a great advantage if we could say to our QA: look, Typescript 2.x will be released way before our own first milestone! I'm writing this in order to show how this issue is important to us. We don't even need a specific date, at least a month should be ok.

@DickvdBrink
Copy link
Contributor

Sometimes the VSCode team leaks some info for the TypeScript release (microsoft/vscode#10145) but it isn't always correct but might be helpful sometimes ;)

@yahiko00
Copy link

yahiko00 commented Aug 20, 2016

I use to check the milestones tab in Github to make my own estimation of releases: https://github.com/Microsoft/TypeScript/milestones
For instance, I would say that TS 2.0.1 shall be released in couple of weeks, let us say 2 months maximum.
For TS 2.1, I would say, the beta could be release at the end of the year/begining of next year.

Since TS is an Open-Source project, I would feel bad to ask deadline comittments to the TypeScript Team. They are doing their best but quality takes time ;)

@nippur72
Copy link

asked also in #7651

@RyanCavanaugh RyanCavanaugh added the Question An issue which isn't directly actionable in code label Aug 22, 2016
@RyanCavanaugh
Copy link
Member

2.0 is a quality-driven release and we'll be shipping it when it's "ready", subject to divisional alignments. The current bug incoming rate is still a bit too high and we have about a dozen bugs left to fix, but there won't be any more feature work going into this release. We have our estimates of when it will be ready but a) we don't announce release dates (sorry!) and b) your guess (given available data) is probably not substantially worse than ours.

2.1 will be where we enable the new emit pipeline, which should have a shorter bug tail but is much riskier (bad emit is much more dangerous). The distance between 2.1 and 2.0 should be much shorter than the distance between 1.8 and 2.0 (which is already too long).

@mhegazy
Copy link
Contributor

mhegazy commented Sep 30, 2016

The road map should now have release-dates. We are targeting November 2016 for the 2.1 release.

@mhegazy mhegazy closed this as completed Sep 30, 2016
@microsoft microsoft locked and limited conversation to collaborators Jun 19, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Question An issue which isn't directly actionable in code
Projects
None yet
Development

No branches or pull requests

6 participants