[PyWPS-dev] PyWPS 4.2

[Tom Kralidis]

Hi all: thanks for everyone's support here.  Updates on my side:

- cut 4.2.0 tag
- created pywps-4.2 branch
- created 4.2.1 milestone and moved all 4.2.0 issues to 4.2.1
- closed 4.2.0 milestone
- updated http://pywps.org/download
- updated version in MASTER to 4.3.dev0 (N.B. to be PEP 440 compliant
moving forward)
- built the 4.2.0 docs on readthedocs.io
- published to PyPI

TODO:
- I have not update pywps-flask (not sure what the state of this is).
- I propose we remove
https://github.com/geopython/pywps/blob/master/RELEASE-howto.md in
lieu of updating
https://github.com/geopython/pywps/wiki/ReleasePackaging, given the
process changes over time (having it on wiki makes it more
collaborative IMHO).  Thoughts?
- communications/release announcement:
 - I haven't sent out the email yet because I'm not sure of state of
pywps-flask, but can do so once I have a thumbs up from someone else
from the PSC
 - can someone write a blogpost?  Even a copy / paste of the email
will be helpful to circulate to there blog aggregators/etc. out there

..Tom


On Wed, Dec 12, 2018 at 12:58 PM Carsten Ehbrecht <ehbrecht at dkrz.de> wrote:
>
> 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
>