<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Jim,<br>
<br>
I'm sure I don't understand all the ramifications of what you've
written, but one thing I'd insist on is the tag rule: if we release
it, it gets tagged. Otherwise support gets too hard....<br>
<pre class="moz-signature" cols="72">Best Regards,
Brent Fraser</pre>
<br>
On 11/28/2011 9:07 AM, James Klassen wrote:
<blockquote
cite="mid:CAHqX795V_yD3BkdDOWsdMJcTFtJJOovcKpjkytVtg9_jceZ-Tw@mail.gmail.com"
type="cite">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
SF.net, 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="gmail_quote">On Mon, Nov 28, 2011 at 8:55 AM,
Dan Little <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:danlittle@yahoo.com">danlittle@yahoo.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex;">
You can see the differences here:<br>
- <a moz-do-not-send="true"
href="http://www.geomoose.org/2.4/" target="_blank">http://www.geomoose.org/2.4/</a><br>
<br>
- <a moz-do-not-send="true"
href="http://www.geomoose.org/2.4/api/"
target="_blank">http://www.geomoose.org/2.4/api/</a><br>
- <a moz-do-not-send="true"
href="http://www.geomoose.org/trunk/"
target="_blank">http://www.geomoose.org/trunk/</a><br>
<br>
- <a moz-do-not-send="true"
href="http://www.geomoose.org/trunk/api/"
target="_blank">http://www.geomoose.org/trunk/api/</a><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 moz-do-not-send="true"
href="mailto:Geomoose-users@lists.osgeo.org">Geomoose-users@lists.osgeo.org</a><br>
<a moz-do-not-send="true"
href="http://lists.osgeo.org/mailman/listinfo/geomoose-users"
target="_blank">http://lists.osgeo.org/mailman/listinfo/geomoose-users</a><br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Geomoose-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Geomoose-users@lists.osgeo.org">Geomoose-users@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/geomoose-users">http://lists.osgeo.org/mailman/listinfo/geomoose-users</a>
</pre>
</blockquote>
</body>
</html>