-
Notifications
You must be signed in to change notification settings - Fork 392
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 4.2 #156
Comments
I hate to say this, but between now and the end of the month, I doubt I Thanks, On Thu, Oct 16, 2014 at 2:46 PM, Bart Nijssen notifications@github.com
|
I hate it too ...
|
You can still freeze the code without releasing the model... Is anybody On Thu, Oct 16, 2014 at 3:57 PM, Bart Nijssen notifications@github.com
|
Yes, but these are changes that you wanted to have in 4.2. Other than you, nobody is using them, but they are now in 4.2 and in the development branches that are leading to 5.0, which is why I want them documented. Having them there without documentation does not make sense. We could have punted on them 6 months ago and you could have just implemented them on your own branch which could have been merged later by you. Suggesting that they should be part of 4.2 and then holding up the release because you don't have time to write documentation (which could have been written months ago when you committed the changes) is unfortunate ... We're all busy ... On Oct 16, 2014, at 4:21 PM, Ted Bohn notifications@github.com wrote:
|
I understand your point. In the future, I will prepare the documentation I will try to get the documentation finished by the end of the month. On Thu, Oct 16, 2014 at 4:38 PM, Bart Nijssen notifications@github.com
|
Thank you - Gracias - Merci - Danke - Dankjewel - Grazie - Origato On Oct 16, 2014, at 4:49 PM, Ted Bohn notifications@github.com wrote:
|
All the issues for 4.2 have now been closed. I will create tags for both the source code and documentation in the morning. Then, tomorrow afternoon, provided everything goes well, I will send an email to the VIC users group announcing the release. |
Excellent
|
4.2 is code-complete (i.e. no new features, additions, etc). The only outstanding issues are
I have moved the release date till the end of October to allow @jhamman time to fix the water balance error and @tbohn to provide documentation for the new features.
No commits other than the bug fix for #147 will be made to 4.2.
This issue can be closed when 4.2. is released.
I will now go ahead with the code reformat from issue #48 and the reorganization from issue #7. I will update the VIC/develop and VIC/dev_5.0 branches accordingly (eventually VIC/dev_5.0 will be deleted).
The text was updated successfully, but these errors were encountered: