-1

I have an opensource project hosted on the GitHub. After each release of my damn project I want to write out new features and bug fixes list to some file like History.md. It will look like:

=== Version 0.0.1 2012-12-21

Version with a new awesome bugs has been released

* [added] New feature
* [fixed] Some bug fixed

But I hesitate. May be I wrong? I don't know, so I ask. Is there are any guidlines/rules/suggestions/good expirience/anything else about how to format history changes? Or maybe change list should not be a single file?

Or more generally: what is the best way to track version changes (in a human readable format, of course) for Github (or any others hostings) projects and incapsulete it into the project itself in more pleasant way?

4

1 に答える 1

0

Githubにはマイルストーンに関する問題があります。

リリースをマイルストーンにリンクし、すべての変更をチケットにリンクすると、マイルストーン内のすべての閉じられたチケットは、人間が読める形式の変更ログを形成します。

于 2012-11-16T14:23:26.183 に答える