about some magritte changes I made...
renggli at gmail.com
Wed Jan 4 21:28:29 MET 2012
I've created http://source.lukas-renggli.ch/magritte2unstable.
If you want I can also setup a continuous build?
On 4 January 2012 20:38, Esteban Lorenzano <estebanlm at gmail.com> wrote:
> ok, as I't might cause some problems because of deprecation of #description (also, it will be even harder after moving descriptions to client side), I prefer to work on an alternative repository in the mean time...
> Problem now is that I can't create a repository for this (just admin has rights). I was trying to create something like "Magritte2Unstable"... Lukas could you create a repository for this?
> El 04/01/2012, a las 2:41p.m., Yanni Chiu escribió:
>> On 03/01/12 12:17 PM, Esteban Lorenzano wrote:
>>>> Feel free to commit it to the current repository, if it doesn't break
>>>> any builds. Otherwise we might want to submit it somewhere else before
>>>> merging into the head.
>>> ok, I will, after I review some small issues.
>> Does this mean you intend to commit it to the Magritte2 repository?
>> I do not build directly from the Magritte2 repository. I use local copies of whatever was the latest, whenever I choose to sync up. So it would be a long time before I see these changes in my build (unless I fork something off to test your changes). I would not want to track a work-in-progress with my regular build, because there would be too many variables (i.e. did I break something, or did something change in Magritte).
>> IMHO, changing Magritte descriptions would warrant using some staging, instead of going directly to head. On the other hand, things often don't get used & tested until they appear in the head. Don't know what the right answer is, except that posting to this list about the changes is important.
>> Magritte, Pier and Related Tools ...
More information about the smallwiki