[Geomoose-users] PSC Update: Progress on Versioned Docs

[James Klassen]

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.

I'm thinking something along the lines of
/moose
 /trunk
 /branches
 /tags
  /1.0
  /1.1
  /1.4
  /1.6 (this currently doesn't exist in SVN, but IIRC we released it)
/moose2
 /trunk
 /branches (used to add changes to older version of the code like the 2.4.1
fixes we've been discussing)
  /2.0
  /2.2 (also not currently in SVN)
  /2.4
 /tags (the rule is if it gets released, it gets tagged)
  /2.0
  /2.2 (also not currently in SVN)
  /2.4
  /2.4.1
  /current

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?

On Mon, Nov 28, 2011 at 8:55 AM, Dan Little <danlittle at yahoo.com> wrote:

> You can see the differences here:
> - http://www.geomoose.org/2.4/
>
> - http://www.geomoose.org/2.4/api/
> - http://www.geomoose.org/trunk/
>
> - http://www.geomoose.org/trunk/api/
>
>
> 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.
>
> This change has not effected the organization in SVN so Eli, myself, and
> others should be able to continue as normal.
>
> There are also two super-nerd changes we should consider:
> 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.
> 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.
>
> _______________________________________________
> Geomoose-users mailing list
> Geomoose-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/geomoose-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/geomoose-users/attachments/20111128/a516eaad/attachment.html