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

NEWS file/page #13

Closed
jorgenschaefer opened this issue Oct 9, 2012 · 2 comments
Closed

NEWS file/page #13

jorgenschaefer opened this issue Oct 9, 2012 · 2 comments
Labels
Milestone

Comments

@jorgenschaefer
Copy link
Collaborator

Once we had our first release, we should maintain a NEWS file or wiki page describing user-visible changes since the last release. I can see points for both the wiki and a file in the distribution.

Pro file: Can be updated in the same commit as the change that introduces the user-visible change. Also, it's The Way It Has Always Been Done.

Con file: Difficult to link to on a user's system, especially considering package.el

Pro wiki: Doesn't depend on commits. Especially making it more readable, fixing typos, or even just adding a forgotten entry all cause spurious edits. Wiki pages are accessible via a globally unique URL.

Con wiki: The information doesn't come with the distribution.

Opinions?

@retroj
Copy link
Collaborator

retroj commented Oct 9, 2012

I vote for wiki. On one large project I work on, we don't do a NEWS file, but instead, the wiki is the manual, and we have a wiki page called BreakingChanges to inform users of changes that will affect their config or user experience.

@jorgenschaefer
Copy link
Collaborator Author

Now on the wiki:

https://github.com/jorgenschaefer/circe/wiki/News.

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

No branches or pull requests

2 participants