But well… is done :) behold the new pharo-nosql organisation! https://github.com/pharo-nosql <https://github.com/pharo-nosql>
already running with travis ci (appveyor is on the way, in fact is done, I just need to modify the vm :P) btw, Martin: your replicaset changes broke mongotalk tests :P (first immediate positive feedback from moving there) Esteban > On 09 Jun 2016, at 20:20, Esteban A. Maringolo <[email protected]> wrote: > > 2016-06-09 13:21 GMT-03:00 Martin Dias <[email protected]>: >> On Thu, Jun 9, 2016 at 9:07 AM, Yanni Chiu <[email protected]> wrote: >>> On Thu, Jun 9, 2016 at 2:58 AM, Esteban Lorenzano <[email protected]> >>> wrote: > >>>> And finally, more we move, more we have encourage to improve the tools, >>>> complete the missing parts… > >>> About a year ago I tried to use git for a project, but gave up because it >>> was not clear to me what tools and processes should be used. Having an >>> active project to follow (like PharoNoSQL) would maybe fill in the missing >>> git knowledge I need. >>> >> Yes, the same happened to me. > > Ditto here. > > I do use GitHub and Bitbucket for other projects, with branches, pull > requests and all the jazz. > But with Pharo I only used filetree, and I'm never know exactly how > the changes are handled, what's all the metadata thing about, and so > on. But maybe because I commited the same package to both an MC repo > (STHub) and Git. > > Regards! > > > Esteban A. Maringolo >
