Hello
Claves, thank you for your suggestion and knowledge. i am happy to study other opensource's convention. :)
Fom your email, I found out that version modification has been made manually. In addtion, Luigi already formulated the convention of standard Quantlib version. (the file "dev_tools/version_numbers.txt" says everything that i mention)
So, to help Luigi managing and other members (including me) able to check version easily, i implemented today a tiny version bumping tool in Python. It follows Luigi's convention as much as possible. (We can check the main version tag string is in dev_tools/version_tag.txt!!! Just one string file)
I implemented it based on Luigi's latest commit result. (that is, i added filelist that version_numbers.txt doesnt mention too) This tool check the filelist in dev_tools/version_filelist.txt.
Finally, the code can show the differences between original and modified files. right now, to avoid overwrite, i made a test directory in root of repo to output the result of this tool.
Because i cant open xla file at all, this tool doesnt change QuantLibXL/framework/QuantLibXL.xla. Please help me.
In conclusion, how can i upload my result without interfering others' work in git? i just want to know the process of contribution, but i feel fear to use git. May i just commit and push to upstream? Anyway, i ve just push my tools in my own repo.
http://github.com/jhyoocoder/quantlib
Thank you all,
Best regards,
Jae
p.s. there is a very very very tiny typo in dev_tools/version_numbers.txt. R010300a2 is 1.3.0a2, not 1.3.1.a2 :)
Hi,
maybe it would be less confusing if we identified the current
development version assigning strings like 1.8b, 1.8rc or
1.8-SNAPSHOT? Number-only sequences could be assigned only to stable
releases.
In this case, once the new stable version can be released, the version
number will be promoted to 1.8, tagged and made available for
download. The new version in trunk would be in fact immediately
promoted to 1.9b, etc...
Apache Maven for instance takes care of all the renaming and tagging
via the commands release:prepare and release:perform. Not sure if any
such utility exists for C++ projects.
Regards,
Claves
On 27 November 2015 at 08:54, Luigi Ballabio <[hidden email]> wrote:
> That's correct. The version released as 1.7 is tagged in the repository as
> QuantLib-v1.7. What goes in the repository after that will be in the next
> release, so 1.8.
>
> Luigi
>
>
> On Fri, Nov 27, 2015 at 8:28 AM cheng li <[hidden email]>
> wrote:
>>
>> Hi Jae,
>>
>>
>>
>> Here “bump” just means update or upgrade or change simply. Since 1.7 has
>> been released a few days ago, Luigi bumped the version number to 1.8 to
>> distinguish from the released. The commits labeled as “Bump version number
>> to 1.8” I think only affects the version number.
>>
>>
>>
>> Regards,
>>
>> Cheng
>>
>>
>>
>> 发件人: Jae Hyeon Yoo [mailto:[hidden email]]
>> 发送时间: 2015年11月27日 14:31
>> 收件人: [hidden email]
>> 主题: [Quantlib-users] A question about bumping version to 1.8?
>>
>>
>>
>> Hello.
>>
>> I am Jae and a totally newbie of opensource culture including Quantlib. In
>> fact, this is my first opensource in which i participate. So... i want to
>> ask a foolish question again to all.
>>
>> I found out that the version says 1.8 not 1.7 in Readme.txt after i cloned
>> repo from Luigi's. i thought 'Pardon? Oh, it may be a typo and it can be my
>> first (and very tiny) contribution to opensource!' But when i checked the
>> upstream i saw a message and committed results from Luigi: "Bump version
>> number to 1.8". May I ask what happened? I think i dont know the exact
>> meaning of 'bump'. Is anyone who teach me this word and what happend in this
>> version? Is there no version 1.7 anymore? I am really curious about it.
>>
>> In addtion, i want to confess that i couldnt configure src at all right
>> after 'git clone'. I am a ubuntu user. I couldnt find 'configure file' at
>> all. i've just solved the problem and am compiling. i leave my results of
>> struggling. Of course, I know that most of developers are already experts.
>> However, for other newbies like me who want to dive into quantlib, i
>> summarized the commands for installation. (I assume that boost is already
>> installed.)
>>
>> $ git clone https://github.com/lballabio/quantlib
>> $ cd quantlib/QuantLib
>> $ sudo apt-get install autoconf libtool
>> $ ./autogen.sh
>> $ ./configure --disable-shared # quantlib.org/faq.shtml ... FAQ4.1
>> $ make
>> $ sudo make install
>>
>> i hope this could help others.
>>
>> p.s
>> Peter, for the previous mail, Really Thank you very much for Carol's(and
>> my) question. i could learn about the structure of quantlib more.
>>
>> Best regards,
>> Jae
>>
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> QuantLib-users mailing list
>> [hidden email]
>> https://lists.sourceforge.net/lists/listinfo/quantlib-users
>
> --
>
> <http://leanpub.com/implementingquantlib>
> <http://implementingquantlib.com>
> <http://twitter.com/lballabio>
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> QuantLib-users mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/quantlib-users
>
| Free forum by Nabble | Disable Popup Ads | Edit this page |