Yes I can definitely appreciate that there are some good things to be said about a 'release often and early' strategy - but we do need to strike a balance with stability.<br><br>Also, I am far less concerned about features than stability. If we are stable, I'd be willing to increase my CFM coeficient for a release *winks*<br>
<br>I *think* we are pretty much feature-complete as far as a 0.6 stomp goes anyways.<br><br>As far as this sim filtering code goes, I really have some half-educated hope that it might help us somewhat with the stability problem.<br>
<br>Cheers!<br>James<br><br><br><div class="gmail_quote">On Wed, Nov 5, 2008 at 2:48 PM, Justin Clark-Casey <span dir="ltr"><<a href="mailto:jjustincc@googlemail.com">jjustincc@googlemail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">Charles Krinke wrote:<br>
> My key issue on the 0.6 tag release is having a sufficient number of<br>
> folks comfortable with moving forward. Nebadon and daTwitch are two<br>
> folks I depend on to help move us in an "increasing reliability and<br>
> stability" direction. So, I would appreciate both feeling a bit more<br>
> comfortable with a 0.6 release. Perhaps we will get there by Sunday,<br>
> perhaps not.<br>
<br>
</div>It just struck me that this can still be done for 0.6 even if it isn't in there by then. We would simply treat the<br>
interface version number as 0 if it isn't present, which would make it initially compatible until the next incompatible<br>
change.<br>
<br>
So please go ahead with the release without this. If the release doesn't happen on Sunday for whatever reason, I may<br>
insert this next week.<br>
<div><div></div><div class="Wj3C7c"><br>
><br>
> Justin, if you want to add in your logic, please feel free. I can not<br>
> imagine that it will decrease stability or reliability in any way. As I<br>
> currently understand the problem, our issue for stability and<br>
> reliability is that a) Sims have been freezing, b) Sims seem to consume<br>
> memory until they start swapping or crash. If we feel that we have a<br>
> reasonable enough trunk to tag it as 0.6, I am delighted to do so, and I<br>
> hope we can get there by Sunday.<br>
><br>
> I think the key criteria for this tagged release is not what features<br>
> exist, but rather, when we tag it, and those who only download tagged<br>
> releases start using it will a) It work at least half-way reliably b)<br>
> Connect to various grids c) Not increase our support overhead on IRC. If<br>
> those three constraints are met, then I would vote "full speed ahead and<br>
> darn the torpedoes".<br>
><br>
> Charles<br>
><br>
> ----- Original Message ----<br>
> From: Justin Clark-Casey <<a href="mailto:jjustincc@googlemail.com">jjustincc@googlemail.com</a>><br>
> To: <a href="mailto:opensim-users@lists.berlios.de">opensim-users@lists.berlios.de</a><br>
> Sent: Wednesday, November 5, 2008 11:42:01 AM<br>
> Subject: Re: [Opensim-users] [PROPOSAL]: Sim version filtering (was Re:<br>
> Sim Version Filtering (re: Mantis #0002361...)<br>
><br>
> Charles Krinke wrote:<br>
> > This seems eminently reasonable to me also.<br>
> ><br>
> > On the 0.6 front, I would like to aim for this coming Sunday to tag svn<br>
> > for a 0.6 release and start the cycle of zip/tarball and binaries for<br>
> > download. As a consequence, this week needs to be one of reliability and<br>
> > stability testing.<br>
><br>
> Ah okay, if we are doing this Sunday then there probably isn't time to<br>
> both do this and give it a reasonable shakedown.<br>
> It would need an extra week, I think. It's your call - I'm easy<br>
> either way.<br>
><br>
> ><br>
> > We had a few problems last week with freezes of regions and this appears<br>
> > to be getting better.<br>
> ><br>
> > This is the time to push for stability as we head towards Sunday with a<br>
> > few to how to minimize support issues on both this channel and our IRC.<br>
> ><br>
> > Charles<br>
> ><br>
> > ----- Original Message ----<br>
</div></div><div class="Ih2E3d">> > From: Sean Dague <<a href="mailto:sdague@gmail.com">sdague@gmail.com</a> <mailto:<a href="mailto:sdague@gmail.com">sdague@gmail.com</a>>><br>
> > To: <a href="mailto:opensim-users@lists.berlios.de">opensim-users@lists.berlios.de</a><br>
</div><div><div></div><div class="Wj3C7c">> <mailto:<a href="mailto:opensim-users@lists.berlios.de">opensim-users@lists.berlios.de</a>><br>
> > Sent: Wednesday, November 5, 2008 7:28:42 AM<br>
> > Subject: Re: [Opensim-users] [PROPOSAL]: Sim version filtering (was Re:<br>
> > Sim Version Filtering (re: Mantis #0002361...)<br>
> ><br>
> > Justin Clark-Casey wrote:<br>
> > > PROPOSAL FOR SIM VERSION FILTERING<br>
> > ><br>
> > > Not being able to stop sim versions that implement obsolete comms<br>
> > interfaces from connecting to a grid is becoming an<br>
> > > increasingly awkward problem. As you can imagine, it leads to a high<br>
> > volume of support requests, particular if the grid<br>
> > > is upgrading quite often (which is the case in large development test<br>
> > grids).<br>
> > ><br>
> > > There has been a proposal (in<br>
> > <a href="http://opensimulator.org/mantis/view.php?id=2361" target="_blank">http://opensimulator.org/mantis/view.php?id=2361</a>) to have the region<br>
> > server send its SVN<br>
> > > revision number to enable filtering by the grid server. However, I'm<br>
> > not a fan of this idea for the reasons outlined in<br>
> > > the e-mails further below (ties us into a source control system, not<br>
> > necessarily present in binaries/source, not<br>
> > > friendly to non OpenSim implementations).<br>
> > ><br>
> > > Therefore, I am going to propose that there is an interface version<br>
> > number in OpenSim.Framework.Servers.VersionInfo.cs<br>
> <<a href="http://OpenSim.Framework.Servers.VersionInfo.cs" target="_blank">http://OpenSim.Framework.Servers.VersionInfo.cs</a>><br>
> > <<a href="http://OpenSim.Framework.Servers.VersionInfo.cs" target="_blank">http://OpenSim.Framework.Servers.VersionInfo.cs</a>>.<br>
> > > This is separate from the OpenSim version, and would increase by 1<br>
> > every time a change was made to OGS1 or interregion<br>
> > > interfaces that was incompatible with older versions.<br>
> > ><br>
> > > So the sequence would be 1, 2, 3, 4, ...<br>
> > ><br>
> > > On region connection, the version number would be sent. If it<br>
> > differs from that of the grid, the grid would refuse<br>
> > > connection with a message advising version upgrade (or possibly<br>
> > downgrade)<br>
> > ><br>
> > > The advantages of this approach are that<br>
> > ><br>
> > > a) We don't use the SVN revision number<br>
> > > b) Grid operators don't have to manually determine which regions are<br>
> > compatible<br>
> > ><br>
> > > The disadvantages are<br>
> > ><br>
> > > a) Developers have to upgrade the number themselves. I don't<br>
> > believe this is a huge burden. It's also not a disaster<br>
> > > if this is forgotton - one just upgrades it on the next commit.<br>
> > ><br>
> > > This may be the simplest thing that could possibly work whilst<br>
> > avoiding the disadvantages of using the SVN number. One<br>
> > > can get more elaborate (e.g. minor verion numbers for compatible<br>
> > changes) but I don't think the complication is<br>
> > > worthwhile or known to be workable at this point.<br>
> > ><br>
> > > Comments?<br>
> ><br>
> > +1 on this approach. I like not using svn version, as that restricts<br>
> > compatibility too much. I also think we'll have a good success rate at<br>
> > figuring out that something is destabalizing change.<br>
> ><br>
> > I'd *highly* suggest this goes in before 0.6, so that 0.6 regions<br>
> > participate in this system. This will be important as a lot of people<br>
> > will probably go to 0.6 when it comes out and get off the svn tracking<br>
> > at that point.<br>
> ><br>
> > -Sean<br>
> ><br>
> > --<br>
> > Sean Dague / Neas Bade<br>
</div></div>> > <a href="mailto:sdague@gmail.com">sdague@gmail.com</a> <mailto:<a href="mailto:sdague@gmail.com">sdague@gmail.com</a>> <mailto:<a href="mailto:sdague@gmail.com">sdague@gmail.com</a><br>
<div class="Ih2E3d">> <mailto:<a href="mailto:sdague@gmail.com">sdague@gmail.com</a>>><br>
> > <a href="http://dague.net" target="_blank">http://dague.net</a><br>
> ><br>
> ><br>
> ><br>
> > ------------------------------------------------------------------------<br>
> ><br>
> > _______________________________________________<br>
> > Opensim-users mailing list<br>
</div>> > <a href="mailto:Opensim-users@lists.berlios.de">Opensim-users@lists.berlios.de</a> <mailto:<a href="mailto:Opensim-users@lists.berlios.de">Opensim-users@lists.berlios.de</a>><br>
<div class="Ih2E3d">> > <a href="https://lists.berlios.de/mailman/listinfo/opensim-users" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-users</a><br>
><br>
><br>
> --<br>
> justincc<br>
> Justin Clark-Casey<br>
> <a href="http://justincc.wordpress.com" target="_blank">http://justincc.wordpress.com</a><br>
> _______________________________________________<br>
> Opensim-users mailing list<br>
</div>> <a href="mailto:Opensim-users@lists.berlios.de">Opensim-users@lists.berlios.de</a> <mailto:<a href="mailto:Opensim-users@lists.berlios.de">Opensim-users@lists.berlios.de</a>><br>
<div><div></div><div class="Wj3C7c">> <a href="https://lists.berlios.de/mailman/listinfo/opensim-users" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-users</a><br>
><br>
><br>
> ------------------------------------------------------------------------<br>
><br>
> _______________________________________________<br>
> Opensim-users mailing list<br>
> <a href="mailto:Opensim-users@lists.berlios.de">Opensim-users@lists.berlios.de</a><br>
> <a href="https://lists.berlios.de/mailman/listinfo/opensim-users" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-users</a><br>
<br>
<br>
--<br>
justincc<br>
Justin Clark-Casey<br>
<a href="http://justincc.wordpress.com" target="_blank">http://justincc.wordpress.com</a><br>
_______________________________________________<br>
Opensim-users mailing list<br>
<a href="mailto:Opensim-users@lists.berlios.de">Opensim-users@lists.berlios.de</a><br>
<a href="https://lists.berlios.de/mailman/listinfo/opensim-users" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-users</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>===================================<br>The wind<br>scours the earth for prayers<br>The night obscures them<br><br><a href="http://osgrid.org">http://osgrid.org</a><br>
<a href="http://del.icio.us/SPQR">http://del.icio.us/SPQR</a><br><a href="http://twitter.com/jstallings2">http://twitter.com/jstallings2</a><br><a href="http://www.linkedin.com/pub/5/770/a49">http://www.linkedin.com/pub/5/770/a49</a><br>