<br><br><div class="gmail_quote">On Tue, May 3, 2011 at 5:06 PM, Igor Stasenko <span dir="ltr"><<a href="mailto:siguctua@gmail.com">siguctua@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><br>
On 3 May 2011 16:57, Mariano Martinez Peck <<a href="mailto:marianopeck@gmail.com">marianopeck@gmail.com</a>> wrote:<br>
> Instead of discussing where to commit I would discuss how to merge and<br>
> define the process with VMMaker. I mean, how WE (the community) and Eliot,<br>
> manage the development of Cog (the VMMaker part).<br>
><br>
> Take as an example today. There is "our branch" which is in<br>
> VMMaker-oscog-XXX.NUMBER. For example, the last one is<br>
> VMMaker-oscog-MarianoMartinezPeck.66.<br>
> Eliot commits are in (since now) VMMaker.oscog-eem.56. Who merges? Eliot?<br>
> us? Would Eliot took the result of the merge as his next base version?<br>
> Because suppose I merge it, and I get VMMaker-oscog-MarianoMartinezPeck.67<br>
> which is the merge with VMMaker.oscog-eem.56. Will Eliot take that version<br>
> and follow his code from that one?<br>
> or he will release VMMaker.oscog-eem.5N tomorrow, and we will need to merge<br>
> with VMMaker-oscog-MarianoMartinezPeck.6N? if so, the merge will always be<br>
> more complicated and the differences will be more and more...<br>
><br>
<br>
</div>As to me the rule is simple:<br>
- before making new release (or snapshot) an author should merge with<br>
latest available version.<br>
<br>
it means, whoever are responsible for update, he should merge previous<br>
work (or just base his work on<br>
latest available version).<br>
<br>
This btw, a typical rule for group development. I've been followed it<br>
since using CVS, then SVN<br>
in many other project i were involved.<br>
Its simple and straightforward.<br>
Why we should invent something else?<br></blockquote><div><br><br>Because it is not fun to do the same merge over and over. And the merge will be each time bigger and bigger.<br>This is why I would like to know whether Eliot will take the result of the merge or not as the base of his next version<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<br>
Okay. So, Mariano, it is your call. Please do the merge eem.56 +<br>
MarianoMartinezPeck.66<br>
and then create new ConfigurationOfCog, so next time we will build new<br>
VMs based on this version.<br>
<br></blockquote><div><br>mmm I don't promise anything. I don't feel brave enough. My unique commit to VMMaker (.66) was a simple change in VMMakerTool to avoid the WorldMenu. There are more than 10 commits between them and none of them done by me. So...I am not sure I will be able to do it or to do it correctly (as opposite to CMakeVMMaker where I feel more confortable to commit and merge). Moreover one of the commits of Dave changed almost all classes (I am not saying it is bad ehh!!)...so the merge doesn't look easy. I would appreciate if you can take a look this time. <br>
<br>Otherwise, I will try to do it along the week.<br> <br>Cheers<br><br>mariano<br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
> Cheers<br>
><br>
> Mariano<br>
<font color="#888888"><br>
<br>
--<br>
</font><div><div></div><div class="h5">Best regards,<br>
Igor Stasenko AKA sig.<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Mariano<br><a href="http://marianopeck.wordpress.com" target="_blank">http://marianopeck.wordpress.com</a><br><br>