<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">@Tom Thanks :)<div class=""><br class=""></div><div class="">I have opened a ticket for the raised question (release howto):</div><div class=""><a href="https://github.com/geopython/pywps/issues/435" class="">https://github.com/geopython/pywps/issues/435</a></div><div class=""><br class=""></div><div class="">We only have the Python 2.x package uploaded on pypi:</div><div class=""><a href="https://github.com/geopython/pywps/issues/436" class="">https://github.com/geopython/pywps/issues/436</a></div><div class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 17 Dec 2018, at 2:25 am, Tom Kralidis <<a href="mailto:tom.kralidis@gmail.com" class="">tom.kralidis@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hi all: thanks for everyone's support here. Updates on my side:<br class=""><br class="">- cut 4.2.0 tag<br class="">- created pywps-4.2 branch<br class="">- created 4.2.1 milestone and moved all 4.2.0 issues to 4.2.1<br class="">- closed 4.2.0 milestone<br class="">- updated <a href="http://pywps.org/download" class="">http://pywps.org/download</a><br class="">- updated version in MASTER to 4.3.dev0 (N.B. to be PEP 440 compliant<br class="">moving forward)<br class="">- built the 4.2.0 docs on <a href="http://readthedocs.io" class="">readthedocs.io</a><br class="">- published to PyPI<br class=""><br class="">TODO:<br class="">- I have not update pywps-flask (not sure what the state of this is).<br class="">- I propose we remove<br class=""><a href="https://github.com/geopython/pywps/blob/master/RELEASE-howto.md" class="">https://github.com/geopython/pywps/blob/master/RELEASE-howto.md</a> in<br class="">lieu of updating<br class=""><a href="https://github.com/geopython/pywps/wiki/ReleasePackaging" class="">https://github.com/geopython/pywps/wiki/ReleasePackaging</a>, given the<br class="">process changes over time (having it on wiki makes it more<br class="">collaborative IMHO). Thoughts?<br class="">- communications/release announcement:<br class=""> - I haven't sent out the email yet because I'm not sure of state of<br class="">pywps-flask, but can do so once I have a thumbs up from someone else<br class="">from the PSC<br class=""> - can someone write a blogpost? Even a copy / paste of the email<br class="">will be helpful to circulate to there blog aggregators/etc. out there<br class=""><br class="">..Tom<br class=""><br class=""><br class="">On Wed, Dec 12, 2018 at 12:58 PM Carsten Ehbrecht <<a href="mailto:ehbrecht@dkrz.de" class="">ehbrecht@dkrz.de</a>> wrote:<br class=""><blockquote type="cite" class=""><br class="">I would say, go ahead with the release when you have time to do so. Having a release this year would be nice.<br class=""><br class="">Any open PRs that can’t be merged before can go into 4.2.1 … and we can have a patch release early next year.<br class=""><br class=""><blockquote type="cite" class="">On 11 Dec 2018, at 23:34, Tom Kralidis <<a href="mailto:tomkralidis@gmail.com" class="">tomkralidis@gmail.com</a>> wrote:<br class=""><br class="">Thanks Luís. Suggest (slight mod):<br class=""><br class="">- Finalize commits<br class="">- keep milestone 4.2. All issues that will not be fixed for 4.2 go into either 4.2.1 or 4.4<br class="">- release 4.2.0 off master<br class=""><br class="">Comments? I can do the release/PyPI.<br class=""><br class="">Sent from my iPhone<br class=""><br class="">On Dec 11, 2018, at 13:05, Luís Moreira de Sousa <<a href="mailto:luis.de.sousa@protonmail.ch" class="">luis.de.sousa@protonmail.ch</a>> wrote:<br class=""><br class=""><blockquote type="cite" class="">Dear all,<br class=""><br class="">last week PyWPS 4.0 commemorated 2 years (yes, already). There has been no new release since, even though there are some important bugs in that tag. In spite of all the great contributions we have had the past two years, the issue list for the 4.2 milestone appears to never shorten enough. The project needs to have more frequent releases to signal the community all the improvements that have been introduced.<br class=""><br class="">I think PyPWS needs to have a new release shortly. I propose the following:<br class="">1. move all bugs in milestone 4.2 to a new one named 4.2.1<br class="">2. move all the other issues not marked as bugs in milestone 4.2 to milestone 4.4<br class="">3. tag the current head as 4.2 and release it<br class=""><br class="">Makes sense? Anything that absolutely needs to be finished before 4.2 is released?<br class=""><br class="">Cheers.<br class="">--<br class="">Luís Moreira de Sousa<br class=""><a href="mailto:luis.de.sousa@protonmail.ch" class="">Email: luis.de.sousa@protonmail.ch</a><br class="">RingID: ring:7ca91d83f4f9dec82fec9f1144b8e5c1ef2a110c<br class="">URL: https://ldesousa.github.io<br class=""><br class="">Sent with ProtonMail Secure Email.<br class=""><br class="">_______________________________________________<br class="">pywps-dev mailing list<br class="">pywps-dev@lists.osgeo.org<br class="">https://lists.osgeo.org/mailman/listinfo/pywps-dev<br class=""></blockquote>_______________________________________________<br class="">pywps-dev mailing list<br class=""><a href="mailto:pywps-dev@lists.osgeo.org" class="">pywps-dev@lists.osgeo.org</a><br class="">https://lists.osgeo.org/mailman/listinfo/pywps-dev<br class=""></blockquote><br class=""></blockquote></div></div></blockquote></div><br class=""></div></body></html>