[Pywps-dev] Development workflow proposal

[Jachym Cepicky]

Yes, there were just features of WPS 2.0.0, not the whole standard

I've added there

https://github.com/geopython/pywps/issues/74



út 9. 2. 2016 v 14:03 odesílatel Tom Kralidis <tomkralidis at gmail.com>
napsal:

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