yes I was thinking about git tags too, but since I have never tried this with pharo or other smalltalk I had my concerns how well it would work. I am really glad it works for you, that means it will works for me as well if I want some versioning for users. I also like the github url very much, simple concise and direct to the point. Thanks for the link too, I am reading it now.
On Sun, Nov 16, 2014 at 12:03 AM, Dale Henrichs < [email protected]> wrote: > > > On Sat, Nov 15, 2014 at 9:54 AM, kilon alios <[email protected]> > wrote: > >> Travis seems like an overkill for me right now. Sure if I was bombarded >> by pull requests from other developers but in reality I work alone . But I >> will definitely keep it in mind in case my projects become so popular that >> people start to send me pull requests regularly. >> > > Makes sense. > > >> >> All I wanted was an easy way to install code from github to pharo without >> the need to install git and you gave me that. Next step is to see how I >> would integrate github with pharo better, should I use Configuration >> versions or is it better to use branches ? I am more orientated towards >> branches. >> > > With git I think that configurations are really no longer necessary ... I > prefer to use branches to isolate development work from the master branch > (topic branches) and then use tags to identify release points ... with > travis-ci validating the commits, I can do continuous deployment on the > master branch ... For Seaside31 we are using tags to stay in sync with the > mcz repository so the tags are useful when folks are used to talking about > useing a particular version of Seaside31. To replace symbolic versions > (like #release3 or #release3.1) we have introduced pattern matching for > tags. You can use the following github url to load the latest version of > 3.1: > > github://GsDevKit/Seaside31:3.1.?/repository > > >> I have stared your repos to make sure I get keep updated in any progress >> you make. I plan also to go back and re read that metacello chapter to >> better understand metacello. >> > > Take a look at the Metacello User Guide[1] as well for information about > using the Metacello Scripting API. > > [1] > https://github.com/dalehenrich/metacello-work/blob/master/docs/MetacelloUserGuide.md > > >> >> Thank you very much for your hard work, keep rocking :) >> >> > Haha, my pleasure! > > Dale > >
