<html><body><div style="color:#000; background-color:#fff; font-family:arial, helvetica, sans-serif;font-size:10pt"><div><span>I agree with all of the below. We can formalize when we start the migration. There is another message on the list from Jody about Git. I'll sound off in there about my preferences for source control there.</span></div><div><br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; margin-top: 5px; padding-left: 5px;"> <div style="font-size: 10pt; font-family: arial, helvetica, sans-serif; "> <div style="font-size: 12pt; font-family: 'times new roman', 'new york', times, serif; "> <font size="2" face="Arial"> <hr size="1"> <b><span style="font-weight:bold;">From:</span></b> James Klassen <klassen.js@gmail.com><br> <b><span style="font-weight: bold;">To:</span></b> Dan Little <danlittle@yahoo.com> <br><b><span style="font-weight: bold;">Cc:</span></b> GeoMOOSE Users List
<geomoose-users@lists.osgeo.org> <br> <b><span style="font-weight: bold;">Sent:</span></b> Monday, November 28, 2011 10:07 AM<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: [Geomoose-users] PSC Update: Progress on Versioned Docs<br> </font> <br>
<div id="yiv540175501">Personally, I would like to see SVN reorganized to follow the general standard form for /trunk /branches and /tags. Besides being less confusing for developers from other projects, this will make use of hg/git/bzr as clients to the svn repository much easier for those who like to develop offline or maintain site-specific local branches. I'm thinking the best time to do this is when the repository is moved over to OSGEO hosting from <a target="_blank" href="http://SF.net">SF.net</a>, since everyone will need to switch or re-checkout anyway.<div>
<br></div><div>I'm thinking something along the lines of</div><div>/moose</div><div> /trunk</div><div> /branches</div><div> /tags</div><div> /1.0</div><div> /1.1</div><div> /1.4</div><div> /1.6 (this currently doesn't exist in SVN, but IIRC we released it)</div>
<div>/moose2</div><div> /trunk</div><div> /branches (used to add changes to older version of the code like the 2.4.1 fixes we've been discussing)</div><div> /2.0</div><div> /2.2 (also not currently in SVN)</div><div>
/2.4</div><div> /tags (the rule is if it gets released, it gets tagged)</div><div> /2.0</div><div> /2.2 (also not currently in SVN)</div><div> /2.4</div><div> /2.4.1</div><div> /current</div><div><br></div><div>As far as I know, my /moose2-branches/url_mapbook-jk is way out of date and doesn't have value anymore and can be deleted. I'm not sure what /sandbox-len is?</div>
<div><div><div><div><br><div class="yiv540175501gmail_quote">On Mon, Nov 28, 2011 at 8:55 AM, Dan Little <span dir="ltr"><<a rel="nofollow" ymailto="mailto:danlittle@yahoo.com" target="_blank" href="mailto:danlittle@yahoo.com">danlittle@yahoo.com</a>></span> wrote:<br><blockquote class="yiv540175501gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
You can see the differences here:<br>
- http://www.geomoose.org/2.4/<br>
<br>
- http://www.geomoose.org/2.4/api/<br>
- http://www.geomoose.org/trunk/<br>
<br>
- http://www.geomoose.org/trunk/api/<br>
<br>
<br>
Right now "/" points to a different directory altogether called "snapshot_20111128", until this morning "/" pointed the docs built from trunk. Back in Denver we discussed that this is sub-optimal since very few users actually work straight out of trunk. Sorry JimK, you will ned to use "/trunk" to find it into the future. When we finalize the 2.6 docs, we will mark that as the "current" branch in the doc build scripts and point "/" to that.<br>
<br>
This change has not effected the organization in SVN so Eli, myself, and others should be able to continue as normal.<br>
<br>
There are also two super-nerd changes we should consider:<br>
1) Support IPv6. This is a tenant of JimK's religion. While I'm not observant of his church, I think it certainly would like to see us execute on this particular project.<br>
2) SSL? A freebie signed certificate is available but I'm really not sure it's necessary as we do not collect, require, nor disseminate PII.<br>
<br>
_______________________________________________<br>
Geomoose-users mailing list<br>
<a rel="nofollow" ymailto="mailto:Geomoose-users@lists.osgeo.org" target="_blank" href="mailto:Geomoose-users@lists.osgeo.org">Geomoose-users@lists.osgeo.org</a><br>
http://lists.osgeo.org/mailman/listinfo/geomoose-users<br>
</blockquote></div><br></div></div></div></div>
</div><br><br> </div> </div> </blockquote></div> </div></body></html>