Update changelog for 0.6.2 #231
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Member
Author
|
#232 should be the last one. Then we're ready. @nextcloud/mail |
Signed-off-by: Christoph Wurst <christoph@winzerhof-wurst.at>
ChristophWurst
force-pushed
the
changelog-062
branch
from
0e0bcaf to
e28fd9a
Compare
skjnldsv
approved these changes
Dec 12, 2016
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and questions. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Everything in 0.6.1 was moved to 0.6.2 because we had to release a NC11 compatible version and I chose it to be 0.6.1.
Therefore, I now increased the version number for master and added all relevant changes that were made in this milestone. If no blocking issues are found in the next few days (I'm using the nightly build to verify in production), I will push it to the app store. Again, we did not release anything for three months, although we've learned from the past that smaller and more regular releases are easier to handle. I'd like to get back to that strategy and release more often now.
cc @Gomez @jancborchardt @nextcloud/mail