<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" data-hsystem="true"></head>
<body><style>p{margin: 0;padding: 0;}
</style>
<p>Hi Jim -</p>
<p> </p>
<p> several parts to this: workflow is now in 'git' .. currently, primarily at
Github.com,</p>
<p>so an update to a script is a "pull request". git workflow has several
possibilities, but a reliable pattern is ...</p>
<p> </p>
<p>Clone the Master Repo</p>
<p> - clone the master repository to your own repository somewhere</p>
<p> </p>
<p>New Branch</p>
<p> - make a new git branch for your feature, give it a descriptive name</p>
<p> - ensure you are editing on that branch..the "current branch" is your
new feature branch...</p>
<p> </p>
<p>Edit and Commit</p>
<p> - make the changes as you see fit; commit those changes</p>
<p> - make sure the changes are visible on the network ..</p>
<p> if you had a local repo push branch to YOUR CLONE of the
project</p>
<p> </p>
<p>Make a Pull Request</p>
<p> - make a "pull request" to the master git repo from your net-visible
repo</p>
<p> - Github.com has a simple interface to this, but it is optional to use
those features</p>
<p> - if you have new binary resources, make those visible on the net
somewhere</p>
<p> </p>
<p>Changes are Reviewed</p>
<p> - a full build is executed using a named branch, so the revision can be
built for testing.</p>
<p> - if things look good, the named branch is merged to master, and the
feature branch is deleted</p>
<p> </p>
<p>--</p>
<p>Debian Packaging:</p>
<p> there is an ambitious and detailed effort to bring much of the software
stack</p>
<p>into Debian Packaging... at a minimum, Debian GIS
https://pkg-grass.alioth.debian.org/</p>
<p>a.k.a. pkg-grass gets dot-deb files with their source descriptions
dot-dsc into their workflow.</p>
<p> </p>
<p>At the UbuntuGIS PPA level, there are also packages, mostly and largely based
on Debian GIS,</p>
<p>but not the exact same content. Please *do* consult with the Debian packagers
on this list and elsewhere</p>
<p>on their preferred methods !</p>
<p> </p>
<p> </p>
<p> comments and corrections welcome </p>
<p> best from Berkeley, California</p>
<p> --Brian</p>
<p> </p>
<p><br><br>On Mon, 23 May 2016 13:39:36 -0500, Jim Klassen
<jklassen@sharedgeo.org> wrote:</p>
<blockquote style="border-left: 2px solid #000000; padding-right: 0px;
padding-left: 5px; margin-left: 5px; margin-right: 0px;">All,<br><br> In
response to the Kicking off OSGeo-Live 10.0 build process, was<br> thinking it
would be good to update the installed version of GeoMoose to<br> the current
stable version. But, it looks like things have changed a<br> bit since the last
time I updated the GeoMoose installer for OSGeo-Live. <br><br> What is the
current process for updating GeoMoose from 2.8.0 to 2.9.0?<br><br> Jim
Klassen<br><br> _______________________________________________<br> Live-demo
mailing list<br> Live-demo@lists.osgeo.org<br>
http://lists.osgeo.org/mailman/listinfo/live-demo<br> http://live.osgeo.org<br>
http://wiki.osgeo.org/wiki/Live_GIS_Disc<br>
</blockquote>
<p><br><br></p>
<p><br> --<br>Brian M Hamlin<br> OSGeo California Chapter<br>
blog.light42.com<br></p>
<p> </p>
</body>
</html>