I dont know if refactoring in a branch is necessary or is all that easy to do with our current SVN system. I think the communication channels we have now (IRC, this mailing list) generally work fairly well. There have been a few times where I wanted to work on a certain area of the code, i.e. physics, and I need to work off of trunk otherwise I may not be able to commit my changes as they would be incompatible. If breaking changes are coming down the pipe then I can work around them if the communication channels are working. So far the longest I've had to wait before attempting any changes has been maybe 8 hours and I've been able to do something else in the meantime so it was not wasted time.<div>
<br></div><div>I don't know if other open source projects have any better ways of managing these types of issues.. perhaps this could be the subject of another thread.</div><div><br></div><div>Anyway, +1 on the changes and if it breaks anything, please offer an update about when things return to normal (whatever normal means).</div>
<div><br><br><div class="gmail_quote">On Thu, Apr 30, 2009 at 10:10 AM, <span dir="ltr"><<a href="mailto:diva@metaverseink.com">diva@metaverseink.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div bgcolor="#ffffff" text="#000000">
Around now, or last week, would probably be a good time to tag
something stable :-)<br>
<br>
I don't mind at all moving this refactoring to a branch, but since we
have never done that I wouldn't even know what to do. I don't expect
this to be bad. The transition to RESTComms was done without almost
anyone noticing it, except the brave explorers in OSGrid who have to
deal with having neighbors on all sorts of different versions. But
except for the version mismatches, which are really impossible to
manage from a development perspective, most people only noticed when
suddenly OpenSim.ini didn't have the remoting port anymore. And
RESTComms actually involved a complete replacement of the underlying
protocol from Remoting to http+REST, which is not the case here -- the
protocol won't change, at least not now.<br>
<br>
Charles Krinke wrote:
<blockquote type="cite"><div><div></div><div class="h5">
<div style="font-family:arial,helvetica,sans-serif;font-size:12pt">
<div>It is always a balance between keeping functionality in an
evolving project and refactoring and experimenting.<br>
<br>
I will support and encourage refactoring and experimentation with one
proviso. That proviso is a few paragraphs on the wiki giving clues to
allow those deploying OpenSim what is going on and how to work around
trunk during a period of refactoring and experimentation.<br>
<br>
Charles<br>
</div>
<div style="font-family:arial,helvetica,sans-serif;font-size:12pt"><br>
<div style="font-family:arial,helvetica,sans-serif;font-size:10pt"><font face="Tahoma" size="2">
<hr size="1"><b><span style="font-weight:bold">From:</span></b>
Mike Dickson <a href="mailto:mike.dickson@hp.com" target="_blank"><mike.dickson@hp.com></a><br>
<b><span style="font-weight:bold">To:</span></b>
<a href="mailto:opensim-dev@lists.berlios.de" target="_blank">"opensim-dev@lists.berlios.de"</a> <a href="mailto:opensim-dev@lists.berlios.de" target="_blank"><opensim-dev@lists.berlios.de></a><br>
<b><span style="font-weight:bold">Sent:</span></b> Thursday, April
30, 2009 8:57:24 AM<br>
<b><span style="font-weight:bold">Subject:</span></b> Re:
[Opensim-dev] moving away from grid vs. standalone<br>
</font><br>
I'll echo a sentiment I've tried to express before. This sort of<br>
aggressive refactoring and experimentation is really important to the<br>
growth of OpenSim. The "release" process has been focused on trying to<br>
figure out a stable point and snapshot-ing that. That places a burden on<br>
the "release coordinator" to poll folks for what that stable "snapshot"<br>
is. IMO, ideally the heavy refactoring would happen on a branch or<br>
separate tree and then pushed to HEAD when it stabilizes. <br>
<br>
Again, I'm completely for the heavy research and refactoring focus.<br>
But IMO if for a shared project you want to do that you need to adopt a<br>
development approach that gracefully allows that to happen.<br>
<br>
Mike<br>
<br>
<br>
On Thu, 2009-04-30 at 15:37 +0000, Dahlia Trimble wrote:<br>
> We need to be careful about how things are broken and make repairs<br>
> expeditiously as we also hinder other developers if they are
unable to<br>
> use their regions for development and testing.<br>
> <br>
> On Wed, Apr 29, 2009 at 3:01 PM, Melanie <<a href="mailto:melanie@t-data.com" target="_blank">melanie@t-data.com</a>> wrote:<br>
> Maybe these things need to be broken. We are almost locked<br>
> into a<br>
> rigid schema, now we still have a chance to go to true<br>
> modularity<br>
> and we should take it. After all, trunk is meant to be<br>
> broken :)<br>
> <br>
> <br>
> Melanie<br>
<br>
<br>
<br>
_______________________________________________<br>
Opensim-dev mailing list<br>
<a href="mailto:Opensim-dev@lists.berlios.de" target="_blank">Opensim-dev@lists.berlios.de</a><br>
<a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
</div>
</div>
</div>
</div></div><pre><hr size="4" width="90%"><div class="im">_______________________________________________
Opensim-dev mailing list
<a href="mailto:Opensim-dev@lists.berlios.de" target="_blank">Opensim-dev@lists.berlios.de</a>
<a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a>
</div></pre>
</blockquote>
<br>
</div>
<br>_______________________________________________<br>
Opensim-dev mailing list<br>
<a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
<a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
<br></blockquote></div><br></div>