Skip to content
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

introduce Changelog file to quickly track changes #68

Closed
gogolok opened this issue Jan 10, 2013 · 16 comments
Closed

introduce Changelog file to quickly track changes #68

gogolok opened this issue Jan 10, 2013 · 16 comments
Assignees

Comments

@gogolok
Copy link

gogolok commented Jan 10, 2013

It's hard to get a quick overview what has changed between version 0.1.8 and 0.1.9.
It would be nice to have a Changelog file.

@swanandp
Copy link
Contributor

Good idea.

@philippfranke
Copy link
Contributor

+1

@swanandp
Copy link
Contributor

@gogolok Any suggestions on doing it for historical data?

@gogolok
Copy link
Author

gogolok commented Mar 2, 2014

@swanandp Maybe in the Wiki?

@philippfranke
Copy link
Contributor

How about creating a markdown file? Headlines represent the version and unordered lists are the changes. Like:

# 0.1.6 (November 4th, 2012)
** Bugs **
- Fixing ...
- ...
** Features **
- ...

# Previous
Previous changes can be seen by reading the commit messages.

/cc @swanandp @gogolok

@fabn
Copy link
Contributor

fabn commented Oct 9, 2014

+1

1 similar comment
@gogolok
Copy link
Author

gogolok commented Jan 1, 2015

+1

@fabn
Copy link
Contributor

fabn commented Jan 22, 2015

@swanandp, you should really consider this. I've just updated my bundle and I got couple of tests failing and I don't know why. For the moment I've pinned aal to version 0.4.0, then I'll use github diff tool to find what's changed in range 0.4.0..0.6.0 but this is really painful.

Please take care of us 🙏

@swanandp
Copy link
Contributor

Yup, I've been negligent on this so far. But no more. I'll see if I can do retrospective changelog.

@swanandp swanandp self-assigned this Jan 22, 2015
@twelvelabs
Copy link

Please, please, please can you add a changelog? It's very tedious to have to use github's compare when updating apps w/ many dependencies.

@fabn
Copy link
Contributor

fabn commented Sep 14, 2015

Still no trace of changelog 😢 😢

@swanandp
Copy link
Contributor

Sorry to disappoint you folks, this task is more tedious than it sounds. But I hope to wrap this up soon.

@fabn
Copy link
Contributor

fabn commented Sep 15, 2015

@swanandp I understand this is boring. However and quick and pretty easy fix would be to introduce a changelog file and start to use it right now for every important change (bugfix or new feature). Alternatively github releases feature is also good.

For past releases a github compare link would be enough (and easy to add), however this repo has no tags thus I can't submit a PR for that. Do you have some way to tag past releases?

@fabn
Copy link
Contributor

fabn commented Sep 15, 2015

You can tag past releases using rubygems changelog and for the future use bundler gem tasks to release the gem, in this way it will be automatically tagged and pushed to github.

@fabn
Copy link
Contributor

fabn commented Dec 15, 2015

Addressed by #177

@fabn
Copy link
Contributor

fabn commented Dec 16, 2015

Changelog file has been generated and it's now present in master branch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants