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

[Proposal] Improve the milestones #2637

Closed
alitaheri opened this issue Dec 22, 2015 · 4 comments
Closed

[Proposal] Improve the milestones #2637

alitaheri opened this issue Dec 22, 2015 · 4 comments

Comments

@alitaheri
Copy link
Member

I think Composable Components feels more like a label than milestone. these should be added to roadmap. Milestones indicate important points in a projects lifecycle. I wish to close those milestones and add them to the roadmap. Instead we should add milestones that indicate releases or long term projects like es6-classes babel 6 migration and such. Cross browser support cannot indicate a time in history but rather an aspect of the project.

@oliviertassinari @newoga Thoughts?

@newoga
Copy link
Contributor

newoga commented Dec 22, 2015

I agree that Composable Components is better suited for a label than a milestone. I'm all for using milestones to indicate releases (for example we would have a milestone for 0.14.0). 👍

Edit:
Just noticed we already have milestones for releases, but I'm fine using the milestones for those exclusively.

@alitaheri
Copy link
Member Author

@newoga The most important reason for this is because milestones hold a mutex :D and Composable Components doesn't indicate at what point this issue will be/was resolved.

@oliviertassinari
Copy link
Member

Milestones indicate important points in a projects lifecycle.

I agree with you. Let's change this.

@alitaheri
Copy link
Member Author

@oliviertassinari Alright, thanks ^_^

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants