<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 2014/09/24 22:16, nicolas bozon
wrote:<br>
</div>
<blockquote
cite="mid:CA+FFBY9OaT2OohQ8aKm_3htbomAYOXmQNzAerSD+yhyhKvRXjw@mail.gmail.com"
type="cite">
<pre wrap="">Hi all,
As this step is needed for Incubation process, and because the document is
good enough for now IMO (it can be improved in future of course), may i
suggest a motion for voting ?
"Accepting the ZOO-Project Release Procedure available at [1]"
+1 Nick</pre>
</blockquote>
+1 Venka<br>
<br>
<blockquote
cite="mid:CA+FFBY9OaT2OohQ8aKm_3htbomAYOXmQNzAerSD+yhyhKvRXjw@mail.gmail.com"
type="cite">
<pre wrap="">
Thanks in advance
Best,
Nick
[1] <a class="moz-txt-link-freetext" href="http://zoo-project.org/trac/wiki/ReleaseProcedure">http://zoo-project.org/trac/wiki/ReleaseProcedure</a>
.
2014-09-18 17:02 GMT+02:00 Angelos Tzotsos <a class="moz-txt-link-rfc2396E" href="mailto:tzotsos@gmail.com"><tzotsos@gmail.com></a>:
</pre>
<blockquote type="cite">
<pre wrap="">Hi,
I would also like to add that the incubation process also needs the source
code review step.
For pycsw, we asked Jody for advice and he pointed us to the GeoServer
wiki, where there are examples of the code review process.
Also have a look here about release documentation:
<a class="moz-txt-link-freetext" href="https://github.com/geopython/pycsw/wiki/Release-Packaging">https://github.com/geopython/pycsw/wiki/Release-Packaging</a>
Best,
Angelos
On Thu, Sep 18, 2014 at 4:01 PM, Daniel Kastl <a class="moz-txt-link-rfc2396E" href="mailto:daniel@georepublic.de"><daniel@georepublic.de></a>
wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi Gerald,
Is this release "checklist" based on how other projects do?
I thought it might be worth to think about following the crowds and also
move to Github for example. It may also simplify contributions by people,
that may maintain there own copy and changes without being able to
contribute in an easy way.
On Github then I would create an issue for each release and assign it to
the release manager. Issues on Github in the meanwhile support also
checklists, which are very convenient for a release. See the example
checklist of the latest pgRouting release:
<a class="moz-txt-link-freetext" href="https://github.com/pgRouting/pgrouting/issues/120">https://github.com/pgRouting/pgrouting/issues/120</a>
Also release notes and release downloads can be managed automatically
with Github. So I feel this is more convenient. And no need to run an SVN
server.
Daniel
On Thu, Sep 18, 2014 at 2:13 PM, Fenoy Gerald <a class="moz-txt-link-rfc2396E" href="mailto:gerald.fenoy@geolabs.fr"><gerald.fenoy@geolabs.fr></a>
wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Dear PSC,
I would like to ask you to review the following document [1].
I would appreciate any kind of comment about it. This document represent
the last thing which we consider missing for incubating at OSGeo.
Waiting for comments or direct editing of the wiki page.
Best regards,
[1] <a class="moz-txt-link-freetext" href="http://zoo-project.org/trac/wiki/ReleaseProcedure">http://zoo-project.org/trac/wiki/ReleaseProcedure</a>
Gérald Fenoy
<a class="moz-txt-link-freetext" href="http://wiki.osgeo.org/wiki/User:Djay">http://wiki.osgeo.org/wiki/User:Djay</a>
_______________________________________________
Zoo-psc mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Zoo-psc@lists.osgeo.org">Zoo-psc@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/zoo-psc">http://lists.osgeo.org/cgi-bin/mailman/listinfo/zoo-psc</a>
</pre>
</blockquote>
<pre wrap="">
--
Georepublic UG & Georepublic Japan
eMail: <a class="moz-txt-link-abbreviated" href="mailto:daniel.kastl@georepublic.de">daniel.kastl@georepublic.de</a>
Web: <a class="moz-txt-link-freetext" href="http://georepublic.info">http://georepublic.info</a>
_______________________________________________
Zoo-psc mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Zoo-psc@lists.osgeo.org">Zoo-psc@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/zoo-psc">http://lists.osgeo.org/cgi-bin/mailman/listinfo/zoo-psc</a>
</pre>
</blockquote>
<pre wrap="">
--
Angelos Tzotsos
Remote Sensing Laboratory
National Technical University of Athens
<a class="moz-txt-link-freetext" href="http://users.ntua.gr/tzotsos">http://users.ntua.gr/tzotsos</a>
_______________________________________________
Zoo-psc mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Zoo-psc@lists.osgeo.org">Zoo-psc@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/zoo-psc">http://lists.osgeo.org/cgi-bin/mailman/listinfo/zoo-psc</a>
</pre>
</blockquote>
<pre wrap="">
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Zoo-psc mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Zoo-psc@lists.osgeo.org">Zoo-psc@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/cgi-bin/mailman/listinfo/zoo-psc">http://lists.osgeo.org/cgi-bin/mailman/listinfo/zoo-psc</a></pre>
</blockquote>
<br>
</body>
</html>