[PyWPS-dev] PyWPS 4.2

[Luí­s Moreira de Sousa]

Hi again,

the idea of having bugs in 4.2.1 was simply to prioritize bug fixing. However, it might be better to keep it simple and move everything to 4.4. If any major bug gets resolved in the meantime we can then release 4.2.1. The correct way would be to open a branch for 4.2 were bugs would be resolved, but that would increase management complexity too much.

Carsten, since you have been the person managing things closer, I propose we wait for you to flag "good to go" on 4.2. We can then have a formal PSC vote for the new release.

Another important thing is to collect all the new features in a pretty release note. Who can do that?

Thank you all.

--
Luís Moreira de Sousa
Email: luis.de.sousa at protonmail.ch
RingID: ring:7ca91d83f4f9dec82fec9f1144b8e5c1ef2a110c
URL: https://ldesousa.github.io

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Tuesday, December 11, 2018 11:34 PM, 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](https://protonmail.com) Secure Email.
>
>> _______________________________________________
>> pywps-dev mailing list
>> pywps-dev at lists.osgeo.org
>> https://lists.osgeo.org/mailman/listinfo/pywps-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pywps-dev/attachments/20181212/de6cbf6b/attachment.html>