<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<tt><font size="+1">Hi Lennart,<br>
<br>
I'm looking into this. What should I use for versioning? a.b.c
where<br>
a = major<br>
b = minor<br>
c = bug-fixes<br>
?<br>
<br>
This seems in line with other genabel packages. Am I right?<br>
<br>
Also, how do you deal with the copyright line <br>
<br>
"Copyright (C) 2009--2014 ..."<br>
<br>
in every source file? Do you simply edit (sed?) all of them
every new year?<br>
<br>
Thanks!<br>
<br>
</font></tt>
<div class="moz-cite-prefix">On 01/13/2015 10:18 AM, L.C. Karssen
wrote:<br>
</div>
<blockquote cite="mid:54B4E2FE.6060101@karssen.org" type="cite">
<pre wrap="">Dear list,
I was just looking at the OmicABEL page on <a class="moz-txt-link-abbreviated" href="http://www.genabel.org">www.genabel.org</a> when it
struck me that OmicABEL doesn't seem to have a version number. I also
did a quick grep in the code and couldn't find a version/release number
there either. Maybe I somehow missed it, but if not, I think we really
should add a version number to each release. Having a version number is
good for various reasons like packaging/upgrading, marketing
(announcements), reproducible research, etc.
Best regards,
Lennart.
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
genabel-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:genabel-devel@lists.r-forge.r-project.org">genabel-devel@lists.r-forge.r-project.org</a>
<a class="moz-txt-link-freetext" href="https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/genabel-devel">https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/genabel-devel</a></pre>
</blockquote>
<br>
</body>
</html>