-
Notifications
You must be signed in to change notification settings - Fork 2k
0.4.0 Release #669
Comments
@codydaig are you sure? they look totally unrelated. |
If you look on and around this line: @igorauad made some of those changes. But it does not cover all the places that #! needed to be removed that #587 points out. |
I'd leave ngBestPractices (#636) PL out and do it more thoroughly for 0.5.0 (it's related to #490 style guide). @rhutchison thoughts? |
Style should follow in 0.4.1 or even 0.5.0 depending on how big of a change it is, but since it doesn't change functionality we should be able to do it anytime. |
@lirantal https://github.com/meanjs/mean/blob/0.4.0/modules/chat/tests/client/chat.client.controller.tests.js is a little bit of an issue, no? |
We should also get rid for either Gulp or Grunt. I would say Grunt as no doubt Gulp is better choice for performance. |
@ravisuhag Gulp is maybe an option for 0.5.0, for 0.4.0 we'll stick with grunt. |
@lirantal, @ilanbiala - I added those chat tests as part of #728. That PR also covers the second bullet in Tests above. |
Hi everyone, We'd like to aggressively push 0.4.0 out before it becomes a monster :-) @ilanbiala suggested closing 0.4.0 out by Thursday (tomorrow) so we can do all the release logistics (merging, etc) and this means we need to close only 'core' 0.4.0 and only important PRs for 0.4.0. The remaining 'nice to have' enhancements we will mark as 0.4.x so we can review and possibly merge them as 0.4.1 and so on soon after 0.4.0 is released. @ilanbiala @codydaig @simison @rhutchison @igorauad @trainerbill @mleanos @cdriscol |
@lirantal @ilanbiala Sounds good to me! |
👍 absolutely. |
@lirantal just waiting for server side tests if we want to include that in 0.4.0 instead of releasing incrementally in 0.4.x. |
since it's a change to the core server.js and grunt I want to push that in a couple of hours for your review. |
+1 Sounds great. |
any update on release date ? thanks :) |
@taninme tomorrow/upcoming week. |
👍 |
before we go ahead with the final 0.4.0 release, if you want to raise a PR for discussion which must be included in 0.4.0 now is the time. |
@ilanbiala looks like I'm not going to make it for the refactoring of the core server.js as I hoped so if we might want to continue without it if I won't ping anything different in the morning. |
Ok. If that's the case, we'll release tomorrow morning and we can start taking care of 0.4.1. |
Cool, I took the day off tomorrow so we can do it on gitter, I'll probably have my coffee ready by 8:30am (GMT+3) |
So that's 10:30 PST? |
09:30PM |
Whoops. Off by 1 hour. |
👍 - awesome! |
released ? missed the party ? |
not yet, 2 more PRs to close, mine and @rhutchison and we're done |
any way to know the schedule for release? |
0.4.0 released now and merged into master branch. |
Thanks everyone for your hard work, couldn't do it with you! |
Congrats everyone! Very good work. |
👍 Everyone here is awesome! Didn't have any merge conflicts from 0.4.0 to master :) Thanks @codydaig for prepping that. |
Great! congratulations guys ! 👏 |
Congrats. Thanks for the excellent work ! |
Thansk and Congrats ! |
Congrats all and quick question ..did you add the admin dashboard to 0.4 ? |
@taninme yes, it's there. |
Excellent! Nice to come back down from the mountains and there's a new release waiting. Thanks everyone who worked on this. It's a massive pile of great commits! |
@simison I'm not going to greet you welcome back until I see some PRs from you :-) |
closing this issue since we already released 0.4.0, you're welcome to continue commenting on any 0.4.0 matters though. |
This is a list of all PRs and Issues that we want fixed and merged to 0.4.0 branch before we release.
General Features
Minor Cleanups
Tests
Documentation
The text was updated successfully, but these errors were encountered: