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
Thoughts about CHANGELOG #443
Comments
|
I've added the changelog for 1.1.0, and shortened the commit links. I agree that the 1.0.0 bit has gotten a bit confusing with the changes in early betas that were reverted or changed further in later betas. However with 249 commits between 0.18 and 1.0 it's not a trivial undertaking to redo it! |
|
Ya I forgot 1.1.0 Changelog, my bad :( On Jan 29, 2013, at 8:11 AM, Andrew Haines notifications@github.com wrote:
|
|
@kuraga it has sense, since some users could get stuck on any of the old versions, including betas. Today I understood that 0.17 -> 1.0 is a painful process. |
|
Yes, some sort of 'upgrading guide' would be nice to have. Marking this as a feature request. :) |
|
Ha! Then done! |
|
@killthekitten ok, that's an argument. I think it'll be good to make first release with current version of API ( |
Good day!
Maybe it's not an important thing but I'm thinking about CHANGELOG :-)
1.0.0.betaXafter1.1.0release?1.0.0betaXand then removed (added back, changed) in1.0.0betaY(X > Y). Maybe store last change only in CHANGELOG? Then we can do small0.18.0..1.0.0changelog (not upgrade guide nor commit history). Current CHANGELOG... I don't know what to do with it then :-)I can help you with it. And where is
1.1.0CHANGELOG? Thanx :-)The text was updated successfully, but these errors were encountered: