Hi Sean, Le 3 déc. 2013 à 06:43, Sean P. DeNigris a écrit :
Wow, it's light years ahead of where I last saw it! It is already much better than writing configs by hand. I was able to do about 75% via the UI to go from nothing, to an initial commit with a baseline including dependent projects and my packages.
A few notes. It would be nice to be able... ⢠to specify other repos for dependent project
Can you explain me your use case?
⢠to select the project's repo from a list if it's already known by the system instead of having to type
Do you mean for a new project? Yes, maybe the developer has already done some commits. I will add that.
Bugs: ⢠I added BabyMock as a dependent project, Versionner showed "(stable)" in the UI, but when it added it to the baseline, it was loading bleeding edge
Indeed. Looks like a bug.
⢠Added packages were a mixture of strings and symbols i.e. 'FMOD', #FMODSpecification, 'BabyMock-Core' should be easy to fix
⢠I added a main repository to Versionner, but it didn't appear in baseline when clicked "update dev" I also noticed that. It is a bug in MetacelloToolBox. I need to catch it.
⢠If you accidentally navigate away from the version you're viewing, e.g. by clicking on another version, all changes are lost without warning
It is the first item on my list because you can loose your time here. I will add a warning.
Keep up the great work. This is a very important tool!
By the way, Versionner will be part of Pharo 3.0 image in a few days. Thanks for your kind feedbacks. Christophe.