[GenABEL-dev] OmicABEL version number

[Diego Fabregat]

Alright, so where do I start form? 0.1.0? 1.0.0?

On 01/14/2015 04:31 PM, L.C. Karssen wrote:
> Hi Diego, Yurii, others,
>
> On 14-01-15 15:24, Yurii Aulchenko wrote:
>>> On 14 Jan 2015, at 15:13, Diego Fabregat
>>> <fabregat at aices.rwth-aachen.de <mailto:fabregat at aices.rwth-aachen.de>>
>>> 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
>>> ?
> 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).
>
>> true, complying with R quasi-standars. c = odd = version in work; c =
>> even = “release”
> 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.
>
>> Yurii
>>
>>> 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?
> Good point! That didn't cross my mind yet. I think using sed is the
> easiest.
>
>
>
> Some background: the GPL Howto (https://gnu.org/licenses/gpl-howto.html)
> 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.
>
>
>
>>> Thanks!
>>>
>>> On 01/13/2015 10:18 AM, L.C. Karssen wrote:
>>>> Dear list,
>>>>
>>>> I was just looking at the OmicABEL page on www.genabel.org 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
>>>> genabel-devel at lists.r-forge.r-project.org
>>>> https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/genabel-devel
>>> _______________________________________________
>>> genabel-devel mailing list
>>> genabel-devel at lists.r-forge.r-project.org
>>> <mailto:genabel-devel at lists.r-forge.r-project.org>
>>> https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/genabel-devel
>>
>>
>> _______________________________________________
>> genabel-devel mailing list
>> genabel-devel at lists.r-forge.r-project.org
>> https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/genabel-devel
>>
>
>
> _______________________________________________
> genabel-devel mailing list
> genabel-devel at lists.r-forge.r-project.org
> https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/genabel-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.r-forge.r-project.org/pipermail/genabel-devel/attachments/20150115/f0c86305/attachment-0001.html>