<div dir="ltr">Yes, there were just features of WPS 2.0.0, not the whole standard<div><br></div><div>I've added there</div><div><br></div><div><a href="https://github.com/geopython/pywps/issues/74">https://github.com/geopython/pywps/issues/74</a><br></div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr">út 9. 2. 2016 v 14:03 odesílatel Tom Kralidis <<a href="mailto:tomkralidis@gmail.com">tomkralidis@gmail.com</a>> napsal:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
P.S. note that as well all open issues are now imported and milestone'd<br>
accordingly: <a href="https://github.com/geopython/pywps/issues" rel="noreferrer" target="_blank">https://github.com/geopython/pywps/issues</a><br>
<br>
On Tue, 9 Feb 2016, Tom Kralidis wrote:<br>
<br>
> Date: Tue, 9 Feb 2016 07:23:13 -0500 (EST)<br>
> From: Tom Kralidis <<a href="mailto:tomkralidis@gmail.com" target="_blank">tomkralidis@gmail.com</a>><br>
> To: Luís de Sousa <<a href="mailto:luis.a.de.sousa@gmail.com" target="_blank">luis.a.de.sousa@gmail.com</a>><br>
> Cc: Jachym Cepicky <<a href="mailto:jachym.cepicky@gmail.com" target="_blank">jachym.cepicky@gmail.com</a>>,<br>
> "<a href="mailto:pywps-dev@lists.osgeo.org" target="_blank">pywps-dev@lists.osgeo.org</a>" <<a href="mailto:pywps-dev@lists.osgeo.org" target="_blank">pywps-dev@lists.osgeo.org</a>><br>
> Subject: Re: [Pywps-dev] Development workflow proposal<br>
><br>
><br>
> Thanks Luís. FYI <a href="https://github.com/geopython/pywps/milestones" rel="noreferrer" target="_blank">https://github.com/geopython/pywps/milestones</a> is a pure<br>
> copy of <a href="https://github.com/PyWPS/pywps-4/milestones" rel="noreferrer" target="_blank">https://github.com/PyWPS/pywps-4/milestones</a> with the exception of<br>
> renaming the versions per below. Feel free to update these accordingly if<br>
> there's information elsewhere that I missed.<br>
><br>
> On Tue, 9 Feb 2016, Luís de Sousa wrote:<br>
><br>
>> Date: Tue, 9 Feb 2016 13:19:38 +0100<br>
>> From: Luís de Sousa <<a href="mailto:luis.a.de.sousa@gmail.com" target="_blank">luis.a.de.sousa@gmail.com</a>><br>
>> To: Tom Kralidis <<a href="mailto:tomkralidis@gmail.com" target="_blank">tomkralidis@gmail.com</a>><br>
>> Cc: Jachym Cepicky <<a href="mailto:jachym.cepicky@gmail.com" target="_blank">jachym.cepicky@gmail.com</a>>,<br>
>> "<a href="mailto:pywps-dev@lists.osgeo.org" target="_blank">pywps-dev@lists.osgeo.org</a>" <<a href="mailto:pywps-dev@lists.osgeo.org" target="_blank">pywps-dev@lists.osgeo.org</a>><br>
>> Subject: Re: [Pywps-dev] Development workflow proposal<br>
>><br>
>> Hi Tom,<br>
>><br>
>> There is WPS 2.0 missing at least. I can not go through it right now,<br>
>> but I will give a closer look in the next few days. I believe some odd<br>
>> versions could already by set out.<br>
>><br>
>> Cheers,<br>
>><br>
>> Luís<br>
>><br>
>> On 9 February 2016 at 13:13, Tom Kralidis <<a href="mailto:tomkralidis@gmail.com" target="_blank">tomkralidis@gmail.com</a>> wrote:<br>
>>><br>
>>> Hi all: done for review/comment:<br>
>>> <a href="https://github.com/geopython/pywps/milestones" rel="noreferrer" target="_blank">https://github.com/geopython/pywps/milestones</a><br>
>>><br>
>>> Thanks<br>
>>><br>
>>> ..Tom<br>
>>><br>
>>> On Tue, 9 Feb 2016, Jachym Cepicky wrote:<br>
>>><br>
>>>> Date: Tue, 09 Feb 2016 07:39:06 +0000<br>
>>>> From: Jachym Cepicky <<a href="mailto:jachym.cepicky@gmail.com" target="_blank">jachym.cepicky@gmail.com</a>><br>
>>>> To: Luís de Sousa <<a href="mailto:luis.a.de.sousa@gmail.com" target="_blank">luis.a.de.sousa@gmail.com</a>>,<br>
>>>> Tom Kralidis <<a href="mailto:tomkralidis@gmail.com" target="_blank">tomkralidis@gmail.com</a>><br>
>>>> Cc: "<a href="mailto:pywps-dev@lists.osgeo.org" target="_blank">pywps-dev@lists.osgeo.org</a>" <<a href="mailto:pywps-dev@lists.osgeo.org" target="_blank">pywps-dev@lists.osgeo.org</a>><br>
>>>> Subject: Re: [Pywps-dev] Development workflow proposal<br>
>>>><br>
>>>><br>
>>>> Hi all,<br>
>>>><br>
>>>> I support this.<br>
>>>><br>
>>>> As Luís writes: moving milestones from pywps/pywps-4 according to new<br>
>>>> scheme is next step now<br>
>>>><br>
>>>> J<br>
>>>><br>
>>>> út 9. 2. 2016 v 8:22 odesílatel Luís de Sousa <<a href="mailto:luis.a.de.sousa@gmail.com" target="_blank">luis.a.de.sousa@gmail.com</a>><br>
>>>> napsal:<br>
>>>><br>
>>>>> Hi Tom,<br>
>>>>><br>
>>>>> That sounds good to me. We should now import the milestones from the<br>
>>>>> old repository[0], taking into account this new versioning scheme. I<br>
>>>>> will try to come up with a proposal throughout this week.<br>
>>>>><br>
>>>>> Regards,<br>
>>>>><br>
>>>>> Luís<br>
>>>>><br>
>>>>> [0] <a href="https://github.com/PyWPS/pywps-4/milestones" rel="noreferrer" target="_blank">https://github.com/PyWPS/pywps-4/milestones</a><br>
>>>>><br>
>>>>> On 9 February 2016 at 04:34, Tom Kralidis <<a href="mailto:tomkralidis@gmail.com" target="_blank">tomkralidis@gmail.com</a>> wrote:<br>
>>>>>><br>
>>>>>> Hi all: as we move ahead with OSGeo incubation and PyWPS 4, I'd like to<br>
>>>>>> propose / confirm the following workflow option for development.<br>
>>>>>><br>
>>>>>> 1./ <a href="https://github.com/geopython/pywps" rel="noreferrer" target="_blank">https://github.com/geopython/pywps</a> is the codebase<br>
>>>>>><br>
>>>>>> We have imported <a href="https://github.com/PyWPS/pywps-4" rel="noreferrer" target="_blank">https://github.com/PyWPS/pywps-4</a> (source code) to<br>
>>>>>> <a href="https://github.com/geopython/pywps/tree/pywps-4" rel="noreferrer" target="_blank">https://github.com/geopython/pywps/tree/pywps-4</a>. When branch pywps-4<br>
>>>>>> is deemed ready we can merge/move as master branch.<br>
>>>>>><br>
>>>>>> 2./ branches are based on minor versions (i.e. pywps-x.y)<br>
>>>>>><br>
>>>>>> We can copy pywps-3.2.3 branch to pywps-3.2 which will signify our 3.x<br>
>>>>>> support and then release 3.x releases against pywps-3.2.<br>
>>>>>><br>
>>>>>> When 4.0.0 is released, we can branch pywps-4.0<br>
>>>>>><br>
>>>>>> 3./ semantic versioning [1] and even/odd strategy [2] tags<br>
>>>>>><br>
>>>>>> This allows us to safely make dev releases which communicate<br>
>>>>>> to users that a given release is unstable by design, i.e.:<br>
>>>>>><br>
>>>>>> 4.0.0 - stable<br>
>>>>>> - 4.0.1 - bugfix based on 4.0 branch<br>
>>>>>> 4.1.0 - unstable based off master<br>
>>>>>> 4.2.0 - stable<br>
>>>>>><br>
>>>>>> I'm more than willing to move items forward to help the dev team<br>
>>>>>> as per above if folks are in agreement.<br>
>>>>>><br>
>>>>>> Confirmation of the above would (IMHO) significantly increase the<br>
>>>>>> clarity<br>
>>>>>> of the PyWPS story for things like OSGeo incubation between PyWPS<br>
>>>>>> versions, lower the barrier for new developers. Given the significant<br>
>>>>><br>
>>>>> efforts<br>
>>>>>><br>
>>>>>> behind PyWPS 4, it's probably a good time to bring this into<br>
>>>>><br>
>>>>> geopython/pywps<br>
>>>>>><br>
>>>>>> to move the project forward.<br>
>>>>>><br>
>>>>>> Thoughts?<br>
>>>>>><br>
>>>>>> ..Tom<br>
>>>>>><br>
>>>>>> [1] <a href="http://semver.org" rel="noreferrer" target="_blank">http://semver.org</a><br>
>>>>>> [2]<br>
>>>>><br>
>>>>><br>
>>>>> <a href="http://producingoss.com/en/development-cycle.html#release-number-even-odd-strategy" rel="noreferrer" target="_blank">http://producingoss.com/en/development-cycle.html#release-number-even-odd-strategy</a><br>
>>>>>><br>
>>>>>> _______________________________________________<br>
>>>>>> pywps-dev mailing list<br>
>>>>>> <a href="mailto:pywps-dev@lists.osgeo.org" target="_blank">pywps-dev@lists.osgeo.org</a><br>
>>>>>> <a href="http://lists.osgeo.org/mailman/listinfo/pywps-dev" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/pywps-dev</a><br>
>>>>><br>
>>>>> _______________________________________________<br>
>>>>> pywps-dev mailing list<br>
>>>>> <a href="mailto:pywps-dev@lists.osgeo.org" target="_blank">pywps-dev@lists.osgeo.org</a><br>
>>>>> <a href="http://lists.osgeo.org/mailman/listinfo/pywps-dev" rel="noreferrer" target="_blank">http://lists.osgeo.org/mailman/listinfo/pywps-dev</a><br>
>>>><br>
>>>><br>
>>><br>
>><br>
><br>
</blockquote></div>