-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Grunt 0.5 "Update Release" #1045
Comments
👍 LGTM |
I agree 100% with this proposal. I'm happy to help to whatever extent necessary @cowboy. |
|
This approach to the 0.5 release seems pretty solid. Over the next few weeks I'll be looking at Grunt to see what does and doesn't make sense in the proposed list. We should update the wiki to change the mention of 0.5 to something else, like 0.future or something. |
We had a talk on IRC and have decided not to drop 0.8 in 0.5 and push that to 0.6 or "0.next" |
👍 I like it. |
@vladikoff can you make |
What’s the current status on this update? Seems to be that Grunt, on both npm and this repository, hasn’t been updated for a long time. |
Is there a more recent roadmap or release schedule somewhere? |
@jzaefferer sorry Jörn, no schedule yet. I closed this because it seems like this proposal is not going to work out. |
How many years have we been hearing about v0.5 now? |
@cowboy any word about the future of grunt? |
+1 for a word on the future of grunt. for me it seems grunt is dead :/ |
+1. i'd like to hear anything about the working process as well. |
My proposal here is to make Grunt 0.5 an "Update Release". Meaning this release will mostly consist of updates and fixes that can't be landed with a minor bump. Efforts such as node-task will probably take longer than expected and in my opinion that should be pushed to 0.6. The plugin ecosystem should be able to update to this release with minimal effort.
Updated 11/03/2014
Include in 0.5 (draft list):
grunt-contrib-*
0.next:
Thoughts? @cowboy @tkellen @shama and everyone else...
The text was updated successfully, but these errors were encountered: