Hi,
I started converting my Libraries/Frameworks to GitHub/Tonel/TravisCI. So far I did the following: https://github.com/svenvc/NeoJSON https://github.com/svenvc/NeoCSV https://github.com/svenvc/ztimestamp https://github.com/svenvc/P3 https://github.com/svenvc/stamp https://github.com/svenvc/SimpleRedisClient https://github.com/svenvc/NeoConsole More will follow, in particular Zinc/Zodiac and STON, both of which are more complex. The TravisCI builds now run for Pharo 7 (32 & 64 bits) and Pharo 6.1. By loading the latest Metacello and Tonel, the code is also loadable in Pharo 6 or 5. After a while I will switch the Catalog entries and declare these repo the main ones. Sven -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org |
+100 Thank you Sven. On Fri, Oct 5, 2018 at 9:06 AM Sven Van Caekenberghe <[hidden email]> wrote: Hi, |
In reply to this post by Sven Van Caekenberghe-2
Great! And yet another reminder that all projects should consider moving to git.
Norbert > Am 05.10.2018 um 14:05 schrieb Sven Van Caekenberghe <[hidden email]>: > > Hi, > > I started converting my Libraries/Frameworks to GitHub/Tonel/TravisCI. > So far I did the following: > > https://github.com/svenvc/NeoJSON > https://github.com/svenvc/NeoCSV > https://github.com/svenvc/ztimestamp > https://github.com/svenvc/P3 > https://github.com/svenvc/stamp > https://github.com/svenvc/SimpleRedisClient > https://github.com/svenvc/NeoConsole > > More will follow, in particular Zinc/Zodiac and STON, both of which are more complex. > > The TravisCI builds now run for Pharo 7 (32 & 64 bits) and Pharo 6.1. > By loading the latest Metacello and Tonel, the code is also loadable in Pharo 6 or 5. > > After a while I will switch the Catalog entries and declare these repo the main ones. > > Sven > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > > > > > |
In reply to this post by Sven Van Caekenberghe-2
Excellent!
Tx Sven. I love Tonel :). I'm super happy because I dreamt about bootstrap in 2001 and Tonel also and now we get them. On Fri, Oct 5, 2018 at 2:06 PM Sven Van Caekenberghe <[hidden email]> wrote: > > Hi, > > I started converting my Libraries/Frameworks to GitHub/Tonel/TravisCI. > So far I did the following: > > https://github.com/svenvc/NeoJSON > https://github.com/svenvc/NeoCSV > https://github.com/svenvc/ztimestamp > https://github.com/svenvc/P3 > https://github.com/svenvc/stamp > https://github.com/svenvc/SimpleRedisClient > https://github.com/svenvc/NeoConsole > > More will follow, in particular Zinc/Zodiac and STON, both of which are more complex. > > The TravisCI builds now run for Pharo 7 (32 & 64 bits) and Pharo 6.1. > By loading the latest Metacello and Tonel, the code is also loadable in Pharo 6 or 5. > > After a while I will switch the Catalog entries and declare these repo the main ones. > > Sven > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > > > > > |
In reply to this post by Sven Van Caekenberghe-2
Very cool. Thank you very much,
Can you make releases for your repos? In my repos I did a release of a version saying it is the same as the last on smalltalkhub. So people can pinpoint to a specific release. I think this is a good way of doing it. Norbert > Am 05.10.2018 um 14:05 schrieb Sven Van Caekenberghe <[hidden email]>: > > Hi, > > I started converting my Libraries/Frameworks to GitHub/Tonel/TravisCI. > So far I did the following: > > https://github.com/svenvc/NeoJSON > https://github.com/svenvc/NeoCSV > https://github.com/svenvc/ztimestamp > https://github.com/svenvc/P3 > https://github.com/svenvc/stamp > https://github.com/svenvc/SimpleRedisClient > https://github.com/svenvc/NeoConsole > > More will follow, in particular Zinc/Zodiac and STON, both of which are more complex. > > The TravisCI builds now run for Pharo 7 (32 & 64 bits) and Pharo 6.1. > By loading the latest Metacello and Tonel, the code is also loadable in Pharo 6 or 5. > > After a while I will switch the Catalog entries and declare these repo the main ones. > > Sven > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > > > > > |
> On 10 Oct 2018, at 11:15, Norbert Hartl <[hidden email]> wrote: > > Very cool. Thank you very much, > > Can you make releases for your repos? In my repos I did a release of a version saying it is the same as the last on smalltalkhub. So people can pinpoint to a specific release. I think this is a good way of doing it. OK, I am still learning ;-) What is the technical/practical differences between a tag and a release then ? > Norbert > > >> Am 05.10.2018 um 14:05 schrieb Sven Van Caekenberghe <[hidden email]>: >> >> Hi, >> >> I started converting my Libraries/Frameworks to GitHub/Tonel/TravisCI. >> So far I did the following: >> >> https://github.com/svenvc/NeoJSON >> https://github.com/svenvc/NeoCSV >> https://github.com/svenvc/ztimestamp >> https://github.com/svenvc/P3 >> https://github.com/svenvc/stamp >> https://github.com/svenvc/SimpleRedisClient >> https://github.com/svenvc/NeoConsole >> >> More will follow, in particular Zinc/Zodiac and STON, both of which are more complex. >> >> The TravisCI builds now run for Pharo 7 (32 & 64 bits) and Pharo 6.1. >> By loading the latest Metacello and Tonel, the code is also loadable in Pharo 6 or 5. >> >> After a while I will switch the Catalog entries and declare these repo the main ones. >> >> Sven >> >> -- >> Sven Van Caekenberghe >> Proudly supporting Pharo >> http://pharo.org >> http://association.pharo.org >> http://consortium.pharo.org >> >> >> >> >> > > |
> Am 10.10.2018 um 15:58 schrieb Sven Van Caekenberghe <[hidden email]>: > > > >> On 10 Oct 2018, at 11:15, Norbert Hartl <[hidden email]> wrote: >> >> Very cool. Thank you very much, >> >> Can you make releases for your repos? In my repos I did a release of a version saying it is the same as the last on smalltalkhub. So people can pinpoint to a specific release. I think this is a good way of doing it. > > OK, I am still learning ;-) > > What is the technical/practical differences between a tag and a release then ? None :) On Github you press the button „Create a new release“ on git commandline you create a tag. Same same Norbert > >> Norbert >> >> >>> Am 05.10.2018 um 14:05 schrieb Sven Van Caekenberghe <[hidden email]>: >>> >>> Hi, >>> >>> I started converting my Libraries/Frameworks to GitHub/Tonel/TravisCI. >>> So far I did the following: >>> >>> https://github.com/svenvc/NeoJSON >>> https://github.com/svenvc/NeoCSV >>> https://github.com/svenvc/ztimestamp >>> https://github.com/svenvc/P3 >>> https://github.com/svenvc/stamp >>> https://github.com/svenvc/SimpleRedisClient >>> https://github.com/svenvc/NeoConsole >>> >>> More will follow, in particular Zinc/Zodiac and STON, both of which are more complex. >>> >>> The TravisCI builds now run for Pharo 7 (32 & 64 bits) and Pharo 6.1. >>> By loading the latest Metacello and Tonel, the code is also loadable in Pharo 6 or 5. >>> >>> After a while I will switch the Catalog entries and declare these repo the main ones. >>> >>> Sven >>> >>> -- >>> Sven Van Caekenberghe >>> Proudly supporting Pharo >>> http://pharo.org >>> http://association.pharo.org >>> http://consortium.pharo.org >>> >>> >>> >>> >>> >> >> > > |
Same same Tag is a git concept that marks a specific commit. Release is a hosting platform (GitHub/GitLab/...) concept that wraps a tag with some fancy stuff (release page, downloads, whatnot). However each release is tied to a git tag. From pharo/metacello dependency perspective, only git tags are relevant. Peter
|
Free forum by Nabble | Edit this page |