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 Schedule needs an update #20649

Closed
ghost opened this issue Nov 27, 2017 · 5 comments
Closed

Release Schedule needs an update #20649

ghost opened this issue Nov 27, 2017 · 5 comments
Assignees

Comments

@ghost
Copy link

ghost commented Nov 27, 2017

I'm submitting a...


[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  
[ ] Feature request
[x] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question

Current behavior

Release Schedule documentation is old and outdated with the v5 release now done.

Expected behavior

It should be updated with the 5.1+ release schedule.

Minimal reproduction of the problem with instructions

Click here

What is the motivation / use case for changing the behavior?

So people know when to expect 5.1+.

Environment


Angular version: X.Y.Z


Browser:
- [ ] Chrome (desktop) version XX
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX
 
For Tooling issues:
- Node version: XX  
- Platform:  

Others:

@IgorMinar IgorMinar added this to the 5.0.x milestone Dec 1, 2017
@IgorMinar IgorMinar modified the milestones: 5.0.x, 5.1.2-sprint Dec 8, 2017
@IgorMinar IgorMinar self-assigned this Dec 8, 2017
@manughub manughub assigned manughub and unassigned IgorMinar Dec 8, 2017
@ghost
Copy link
Author

ghost commented Dec 20, 2017

Uh oh, looks like this missed the deadline (5.1.2-Sprint 1 (Dec 11 - 19, 2017))! Everything ok?

@IgorMinar
Copy link
Contributor

IgorMinar commented Dec 23, 2017 via email

@MarcusMorba
Copy link

Can some meanwhile post the most important planned release dates here in the comments? Thanks.

IgorMinar pushed a commit to IgorMinar/angular that referenced this issue Jan 10, 2018
IgorMinar added a commit to IgorMinar/angular that referenced this issue Jan 10, 2018
IgorMinar added a commit to IgorMinar/angular that referenced this issue Jan 10, 2018
leo6104 pushed a commit to leo6104/angular that referenced this issue Mar 25, 2018
@ghost
Copy link
Author

ghost commented May 7, 2018

It's fallen out of sync again guys, see new issue: #23754

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Jun 2, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants