<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <font size="+1"><tt>Alright, so where do I start form? 0.1.0? 1.0.0?<br>
        <br>
      </tt></font>
    <div class="moz-cite-prefix">On 01/14/2015 04:31 PM, L.C. Karssen
      wrote:<br>
    </div>
    <blockquote cite="mid:54B68BCD.3040301@karssen.org" type="cite">
      <pre wrap="">Hi Diego, Yurii, others,

On 14-01-15 15:24, Yurii Aulchenko wrote:
</pre>
      <blockquote type="cite">
        <pre wrap="">
</pre>
        <blockquote type="cite">
          <pre wrap="">On 14 Jan 2015, at 15:13, Diego Fabregat
<<a class="moz-txt-link-abbreviated" href="mailto:fabregat@aices.rwth-aachen.de">fabregat@aices.rwth-aachen.de</a> <a class="moz-txt-link-rfc2396E" href="mailto:fabregat@aices.rwth-aachen.de"><mailto:fabregat@aices.rwth-aachen.de></a>>
wrote:

Hi Lennart,

I'm looking into this. What should I use for versioning? a.b.c where
a = major
b = minor
c = bug-fixes
?
</pre>
        </blockquote>
        <pre wrap="">
</pre>
      </blockquote>
      <pre wrap="">
Yes, that's what I do with ProbABEL and other package I maintain (note
that for R packages the form a.b-c is more common).

</pre>
      <blockquote type="cite">
        <pre wrap="">true, complying with R quasi-standars. c = odd = version in work; c =
even = “release”
</pre>
      </blockquote>
      <pre wrap="">
I'm not sure about the even/odd thing. At least I don't use it in that
way. As far as I know, the "Writing R Extensions" document doesn't
mention this.

</pre>
      <blockquote type="cite">
        <pre wrap="">
Yurii

</pre>
        <blockquote type="cite">
          <pre wrap="">
This seems in line with other genabel packages. Am I right?

Also, how do you deal with the copyright line

"Copyright (C) 2009--2014 ..."

in every source file? Do you simply edit (sed?) all of them every new
year?
</pre>
        </blockquote>
      </blockquote>
      <pre wrap="">
Good point! That didn't cross my mind yet. I think using sed is the
easiest.



Some background: the GPL Howto (<a class="moz-txt-link-freetext" href="https://gnu.org/licenses/gpl-howto.html">https://gnu.org/licenses/gpl-howto.html</a>)
states the following:
     "The copyright notice should include the year in which you
      finished preparing the release (...)"
and
     "For software with several releases over multiple years, it's okay
      to use a range (“2008-2010”) instead of listing individual years
      (...) if and only if every year in the range, inclusive, really
      is a “copyrightable” year that would be listed individually; and
      you make an explicit statement in your documentation about this
      usage."

So ProbABEL doesn't follow this to the letter, but I guess it's good enough.


Best,

Lennart.



</pre>
      <blockquote type="cite">
        <blockquote type="cite">
          <pre wrap="">
Thanks!

On 01/13/2015 10:18 AM, L.C. Karssen wrote:
</pre>
          <blockquote 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.


_______________________________________________
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>
          <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-rfc2396E" href="mailto:genabel-devel@lists.r-forge.r-project.org"><mailto: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>
        <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>
      <pre wrap="">
</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>