[PyWPS-dev] PyWPS 4.2

[Carsten Ehbrecht]

I would say, go ahead with the release when you have time to do so. Having a release this year would be nice.

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.

> On 11 Dec 2018, at 23:34, Tom Kralidis <tomkralidis at gmail.com> wrote:
> 
> Thanks Luí­s. Suggest (slight mod):
> 
> - Finalize commits
> - keep milestone 4.2. All issues that will not be fixed for 4.2 go into either 4.2.1 or 4.4
> - release 4.2.0 off master
> 
> Comments? I can do the release/PyPI.
> 
> Sent from my iPhone
> 
> On Dec 11, 2018, at 13:05, Luí­s Moreira de Sousa <luis.de.sousa at protonmail.ch> wrote:
> 
>> Dear all,
>> 
>> 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.
>> 
>> I think PyPWS needs to have a new release shortly. I propose the following: 
>> 1. move all bugs in milestone 4.2 to a new one named 4.2.1
>> 2. move all the other issues not marked as bugs in milestone 4.2 to milestone 4.4
>> 3. tag the current head as 4.2 and release it
>> 
>> Makes sense? Anything that absolutely needs to be finished before 4.2 is released?
>> 
>> Cheers.
>> -- 
>> Luís Moreira de Sousa
>> Email: luis.de.sousa at protonmail.ch
>> RingID: ring:7ca91d83f4f9dec82fec9f1144b8e5c1ef2a110c
>> URL: https://ldesousa.github.io
>> 
>> Sent with ProtonMail Secure Email.
>> 
>> _______________________________________________
>> pywps-dev mailing list
>> pywps-dev at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/pywps-dev
> _______________________________________________
> pywps-dev mailing list
> pywps-dev at lists.osgeo.org
> https://lists.osgeo.org/mailman/listinfo/pywps-dev