Release Tag with version number about myq_gadgets HOT 5 CLOSED

I left off version #'s long ago, simply because my work has been very occasional and I've just pulled from HEAD. The CHANGELOG is woefully out of date, I'm afraid.

I'm curious what packages you are making?

from myq_gadgets.

Thanks a lot for your quick reply. I would like to create a Debian / Ubuntu package to make it easier to provision the scripts on our servers. The idea to have an "release version number" is to have an reference from the package to the version on GitHub.

from myq_gadgets.

Are there any specific constraints on Debian packaging that precludes using a datestamp-like version ( e.g., myq_gadgets-20141218) or does it need to be more traditional (1.1, 2.0, etc.)?

On Dec 18, 2014, at 8:31 AM, Thomas Merkel [email protected] wrote:

Thanks a lot for your quick reply. I would like to create a Debian / Ubuntu package to make it easier to provision the scripts on our servers. The idea to have an "release version number" is to have an reference from the package to the version on GitHub.

—
Reply to this email directly or view it on GitHub #8 (comment).

Jay Janssen, Managing Consultant, Percona
http://about.me/jay.janssen

from myq_gadgets.

Reference from the debian policy a version number as epoch is also valid. If possible for you the version number as epoch should YYYYMMDD. But from my side I prefer every version number you could provide me :-)

[1] http://www.fifi.org/doc/debian-policy/policy.html/ch-versions.html

from myq_gadgets.

For now I've created an 0.4.0 release: https://github.com/jayjanssen/myq_gadgets/releases/tag/0.4.0

Does that meet your immediate needs?

I want to do some work on this project and formalize the releases a bit better, but for now I'll just maintain this version and update when I get poked.

from myq_gadgets.