[GRASS-dev] [release planning] GRASS GIS 7.8.0 with Python3 support

[Laurent C.]

Le mar. 8 janv. 2019 à 00:44, Veronica Andreo <veroandreo at gmail.com> a
écrit :

> El lun., 7 ene. 2019 a las 11:51, Markus Neteler (<neteler at osgeo.org>)
> escribió:
>
>> On Mon, Jan 7, 2019 at 11:48 AM Martin Landa <landa.martin at gmail.com>
>> wrote:
>> > po 7. 1. 2019 v 11:41 odesílatel Markus Neteler <neteler at osgeo.org>
>> napsal:
>> > > - Proposal of release: 7 Jan 2019
>> > > - Creation of release branch: 24 Jan 2019
>> > > - RC1: 1 Feb 2019
>> > > - RC2: 7 Feb 2019 - if needed
>> > > - Final release: ~14 Feb 2019
>> >
>> > I am afraid that more realistic release date for 7.8 version is
>> > ~May/June 2019. Python3 support is not fully done (Anna will know
>> > more).
>
>
> I've been mostly testing the temporal modules and many of them fail [0] as
> well as many of the temporal tests [1] (dunno if the latter is related to
> python3 though).
> IMHO, this is one of the parts that might require more work and testing. I
> regret I do not know how to answer Anna here:
> https://lists.osgeo.org/pipermail/grass-dev/2019-January/090879.html
>
>
>> We don't have Windows builds for testing yet. It also doesn't
>> > make sense to me to release 7.6 in January and 7.8 in February.
>>
>> Personally I would have rather skipped 7.6 but of course that is not
>> possible.
>>
>> > If we
>> > want to release Python3-ready GRASS version so early we could
>> > integrate it to upcoming version 7.6.
>>
>
> please don't break the temporal framework in 76
>
> Vero
>
> [0] https://trac.osgeo.org/grass/ticket/3727
> [1] https://trac.osgeo.org/grass/ticket/3706
>

I believe that only a major release could be allowed to break a previously
working functionality. It would be very confusing to have a code that work
on one version stops working after a minor version bump.
I my humble opinion it would be contrary to semver that GRASS mostly
follows.

Laurent
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/grass-dev/attachments/20190109/5e3e94dc/attachment.html>