Re: [xwiki-devs] [Proposal] Update database support strategy
Big +1 to downgrade, the current situation does not make any sense. On Wed, Jun 5, 2019 at 2:22 PM Simon Urli wrote: > > Hi everyone, > > I reactivate this thread because of some issues with Oracle 12. > We announced in November 2018 that we supported Oracle 12 and at that > time we said that we needed to test properly XWiki with Oracle 12. > > Apparently we didn't really perform such test and we obtained a first > major issue with it in April 2019: https://jira.xwiki.org/browse/XWIKI-16327 > From what I understand and what Ilie said on the chat this issue > basically prevents from using XWiki with Oracle 12 right now. > > FTR even if we announced supporting Oracle 12, for now we only perform > some automated docker test with Oracle 11 (see: > https://dev.xwiki.org/xwiki/bin/view/Community/Testing/DockerTesting/#HConfigurationsoptions). > > > So I propose that for now we downgrade to Oracle 11 in > https://dev.xwiki.org/xwiki/bin/view/Community/SupportStrategy/DatabaseSupportStrategy > until we prove that XWiki can indeed be used with Oracle 12. > This involves at least to fix XWIKI-16327 and to perform a manual > testing of XWiki with Oracle 12. > > WDYT? > > Simon > > > On 15/11/2018 08:27, Vincent Massol wrote: > > > > > >> On 14 Nov 2018, at 16:08, Vincent Massol wrote: > >> > >> > >> > >>> On 14 Nov 2018, at 15:58, Eduard Moraru wrote: > >>> > >>> On Tue, Nov 13, 2018 at 3:21 PM Vincent Massol wrote: > >>> > > > > On 13 Nov 2018, at 11:58, Vincent Massol wrote: > > > > There are 2 questions here: > > * Should we add support for MariaDB? And if so which versions. Just > found that there’s an official docker image for it so it should be > relatively easy to support MariaDB in our docker-based testing framework: > https://hub.docker.com/_/mariadb/ (TestContainers also has a wrapper now > for MariaDB: > https://github.com/testcontainers/testcontainers-java/tree/master/modules/mariadb). > Note that the MariaDB versions don’t match the MySQL versions. > > FTR, I’ve tried adding support for MariaDB and it’s currently not > working, > because of > https://github.com/testcontainers/testcontainers-java/issues/949. But we > could provide a PR to them with not so big efforts or using a > GenericContainer (less nice). > > >>> > >>> Maybe I'm misunderstanding, but it looks like we're mixing XWiki's support > >>> of the MariaDB database itself with XWiki's test infrastructure's > >>> capability to support a MariaDB database container, which looks a bit > >>> off-topic to me. I get that we need it integrated in our tests to detect > >>> anomalies, but I don't really see it as an eliminatory criterion. > >> > >> I agree. Some comments: > >> > >> 1) This thread was not about deciding which DB to support. It was to > >> define a strategy to be more explicit in the versions that we support for > >> the various already supported DBs. > >> 2) I also started this thread because the goal is to automate the tests. > >> If the idea is to add more work for manual tests then the answer is no, we > >> don’t want to increase the # of DBs we support since we don’t have the > >> manpower to do that. At least I would be against it simply because we > >> can’t do it for practical purposes. > >> 3) MariaDB support in TC is not a big deal, as I mentioned already (there > >> are several ways to fix it). > > > > BTW on this point, the issue I had was fixed in > > https://github.com/testcontainers/testcontainers-java/pull/950 (just need > > to wait for the next release to get it now, shouldn’t be too long). > > > > Thanks > > -Vincent > > > >> 4) As I said on this thread, there are only 2 questions to answer from my > >> POV: > >> * Should we add support for MariaDB? And if so which versions. > >> * Should we drop support for MySQL? > >> > >> Thanks > >> -Vincent > >> > >>> Thanks, > >>> Eduard > >>> > >>> > > Thanks > -Vincent > > > * Should we drop support for MySQL? > > > > Thanks > > -Vincent > > > >> On 13 Nov 2018, at 11:50, Guillaume Delhumeau < > guillaume.delhum...@xwiki.com> wrote: > >> > >> Hello, > >> > >> We are in a weird situation where we don't say we support MariaDB but > >> "the latest > >> MySQL version of stable Debian repository", which is currently... > MariaDB > >> [1] > >> > >> So we need to update our strategy about this fact. I am currently > setting > >> up a server with debian 9 (stable) and I don't know if I should install > >> MySQL from the Oracle repository our continue with the standard debian > >> package (MariaDB). > >> > >> On my side, I am not against aligning ourself to debian. Basically, all > >> users installing XWiki with our Debian packages are using MariaDB for a > >> year now [2], and we never encounter any problem so far. > >> > >> Thanks, > >> >
Re: [xwiki-devs] [Proposal] Update database support strategy
Hi everyone,
I reactivate this thread because of some issues with Oracle 12.
We announced in November 2018 that we supported Oracle 12 and at that
time we said that we needed to test properly XWiki with Oracle 12.
Apparently we didn't really perform such test and we obtained a first
major issue with it in April 2019: https://jira.xwiki.org/browse/XWIKI-16327
From what I understand and what Ilie said on the chat this issue
basically prevents from using XWiki with Oracle 12 right now.
FTR even if we announced supporting Oracle 12, for now we only perform
some automated docker test with Oracle 11 (see:
https://dev.xwiki.org/xwiki/bin/view/Community/Testing/DockerTesting/#HConfigurationsoptions).
So I propose that for now we downgrade to Oracle 11 in
https://dev.xwiki.org/xwiki/bin/view/Community/SupportStrategy/DatabaseSupportStrategy
until we prove that XWiki can indeed be used with Oracle 12.
This involves at least to fix XWIKI-16327 and to perform a manual
testing of XWiki with Oracle 12.
WDYT?
Simon
On 15/11/2018 08:27, Vincent Massol wrote:
On 14 Nov 2018, at 16:08, Vincent Massol wrote:
On 14 Nov 2018, at 15:58, Eduard Moraru wrote:
On Tue, Nov 13, 2018 at 3:21 PM Vincent Massol wrote:
On 13 Nov 2018, at 11:58, Vincent Massol wrote:
There are 2 questions here:
* Should we add support for MariaDB? And if so which versions. Just
found that there’s an official docker image for it so it should be
relatively easy to support MariaDB in our docker-based testing framework:
https://hub.docker.com/_/mariadb/ (TestContainers also has a wrapper now
for MariaDB:
https://github.com/testcontainers/testcontainers-java/tree/master/modules/mariadb).
Note that the MariaDB versions don’t match the MySQL versions.
FTR, I’ve tried adding support for MariaDB and it’s currently not working,
because of
https://github.com/testcontainers/testcontainers-java/issues/949. But we
could provide a PR to them with not so big efforts or using a
GenericContainer (less nice).
Maybe I'm misunderstanding, but it looks like we're mixing XWiki's support
of the MariaDB database itself with XWiki's test infrastructure's
capability to support a MariaDB database container, which looks a bit
off-topic to me. I get that we need it integrated in our tests to detect
anomalies, but I don't really see it as an eliminatory criterion.
I agree. Some comments:
1) This thread was not about deciding which DB to support. It was to define a
strategy to be more explicit in the versions that we support for the various
already supported DBs.
2) I also started this thread because the goal is to automate the tests. If the
idea is to add more work for manual tests then the answer is no, we don’t want
to increase the # of DBs we support since we don’t have the manpower to do
that. At least I would be against it simply because we can’t do it for
practical purposes.
3) MariaDB support in TC is not a big deal, as I mentioned already (there are
several ways to fix it).
BTW on this point, the issue I had was fixed in
https://github.com/testcontainers/testcontainers-java/pull/950 (just need to
wait for the next release to get it now, shouldn’t be too long).
Thanks
-Vincent
4) As I said on this thread, there are only 2 questions to answer from my POV:
* Should we add support for MariaDB? And if so which versions.
* Should we drop support for MySQL?
Thanks
-Vincent
Thanks,
Eduard
Thanks
-Vincent
* Should we drop support for MySQL?
Thanks
-Vincent
On 13 Nov 2018, at 11:50, Guillaume Delhumeau <
guillaume.delhum...@xwiki.com> wrote:
Hello,
We are in a weird situation where we don't say we support MariaDB but
"the latest
MySQL version of stable Debian repository", which is currently...
MariaDB
[1]
So we need to update our strategy about this fact. I am currently
setting
up a server with debian 9 (stable) and I don't know if I should install
MySQL from the Oracle repository our continue with the standard debian
package (MariaDB).
On my side, I am not against aligning ourself to debian. Basically, all
users installing XWiki with our Debian packages are using MariaDB for a
year now [2], and we never encounter any problem so far.
Thanks,
[1] https://packages.debian.org/stretch/default-mysql-server (dep:
mariadb-server-10.1)
[2] https://www.debian.org/News/2017/20170617.en.html
Le lun. 12 nov. 2018 à 18:54, Thomas Mortagne <
thomas.morta...@xwiki.com> a
écrit :
Indeed mysql-server package (version 5.5.) leads to
mariadb-server-10.1 in current stretch repository.
What is surprising is that this is not the case for sid which is more
or less supposed to be the future. It's also not the case in Ubuntu
which is doing the same thing as sid.
On Mon, Nov 12, 2018 at 6:22 PM Eduard Moraru
wrote:
I am not up to date on the topic, but I would like to add the fact
that
Debian 9 ("stretch") has actually dropped MySQL and moved officially
to
MariaDB, forcefully migrating existing MySQL
Re: [xwiki-devs] [Proposal] Update database support strategy
> On 14 Nov 2018, at 16:08, Vincent Massol wrote:
>
>
>
>> On 14 Nov 2018, at 15:58, Eduard Moraru wrote:
>>
>> On Tue, Nov 13, 2018 at 3:21 PM Vincent Massol wrote:
>>
>>>
>>>
On 13 Nov 2018, at 11:58, Vincent Massol wrote:
There are 2 questions here:
* Should we add support for MariaDB? And if so which versions. Just
>>> found that there’s an official docker image for it so it should be
>>> relatively easy to support MariaDB in our docker-based testing framework:
>>> https://hub.docker.com/_/mariadb/ (TestContainers also has a wrapper now
>>> for MariaDB:
>>> https://github.com/testcontainers/testcontainers-java/tree/master/modules/mariadb).
>>> Note that the MariaDB versions don’t match the MySQL versions.
>>>
>>> FTR, I’ve tried adding support for MariaDB and it’s currently not working,
>>> because of
>>> https://github.com/testcontainers/testcontainers-java/issues/949. But we
>>> could provide a PR to them with not so big efforts or using a
>>> GenericContainer (less nice).
>>>
>>
>> Maybe I'm misunderstanding, but it looks like we're mixing XWiki's support
>> of the MariaDB database itself with XWiki's test infrastructure's
>> capability to support a MariaDB database container, which looks a bit
>> off-topic to me. I get that we need it integrated in our tests to detect
>> anomalies, but I don't really see it as an eliminatory criterion.
>
> I agree. Some comments:
>
> 1) This thread was not about deciding which DB to support. It was to define a
> strategy to be more explicit in the versions that we support for the various
> already supported DBs.
> 2) I also started this thread because the goal is to automate the tests. If
> the idea is to add more work for manual tests then the answer is no, we don’t
> want to increase the # of DBs we support since we don’t have the manpower to
> do that. At least I would be against it simply because we can’t do it for
> practical purposes.
> 3) MariaDB support in TC is not a big deal, as I mentioned already (there are
> several ways to fix it).
BTW on this point, the issue I had was fixed in
https://github.com/testcontainers/testcontainers-java/pull/950 (just need to
wait for the next release to get it now, shouldn’t be too long).
Thanks
-Vincent
> 4) As I said on this thread, there are only 2 questions to answer from my POV:
> * Should we add support for MariaDB? And if so which versions.
> * Should we drop support for MySQL?
>
> Thanks
> -Vincent
>
>> Thanks,
>> Eduard
>>
>>
>>>
>>> Thanks
>>> -Vincent
>>>
* Should we drop support for MySQL?
Thanks
-Vincent
> On 13 Nov 2018, at 11:50, Guillaume Delhumeau <
>>> guillaume.delhum...@xwiki.com> wrote:
>
> Hello,
>
> We are in a weird situation where we don't say we support MariaDB but
> "the latest
> MySQL version of stable Debian repository", which is currently...
>>> MariaDB
> [1]
>
> So we need to update our strategy about this fact. I am currently
>>> setting
> up a server with debian 9 (stable) and I don't know if I should install
> MySQL from the Oracle repository our continue with the standard debian
> package (MariaDB).
>
> On my side, I am not against aligning ourself to debian. Basically, all
> users installing XWiki with our Debian packages are using MariaDB for a
> year now [2], and we never encounter any problem so far.
>
> Thanks,
>
> [1] https://packages.debian.org/stretch/default-mysql-server (dep:
> mariadb-server-10.1)
> [2] https://www.debian.org/News/2017/20170617.en.html
>
> Le lun. 12 nov. 2018 à 18:54, Thomas Mortagne <
>>> thomas.morta...@xwiki.com> a
> écrit :
>
>> Indeed mysql-server package (version 5.5.) leads to
>> mariadb-server-10.1 in current stretch repository.
>>
>> What is surprising is that this is not the case for sid which is more
>> or less supposed to be the future. It's also not the case in Ubuntu
>> which is doing the same thing as sid.
>> On Mon, Nov 12, 2018 at 6:22 PM Eduard Moraru
>> wrote:
>>>
>>> I am not up to date on the topic, but I would like to add the fact
>>> that
>>> Debian 9 ("stretch") has actually dropped MySQL and moved officially
>>> to
>>> MariaDB, forcefully migrating existing MySQL installed versions to
>> MariaDB.
>>>
>>>
>>
>>> https://www.debian.org/releases/stable/amd64/release-notes/ch-whats-new.en.html#mariadb-replaces-mysql
>>>
>>> The default mysql-server package now redirects to MariaDB instead.
>>>
>>> If we are going to follow Debian's lead, we might want to at least
>> consider
>>> this move.
>>>
>>> Thanks,
>>> Eduard
>>>
>>> On Mon, Nov 12, 2018 at 6:38 PM Vincent Massol
>> wrote:
>>>
> On 12 Nov 2018, at 16:52, Vincent Massol
>>> wrote:
>
> So we need to conclude on
Re: [xwiki-devs] [Proposal] Update database support strategy
> On 14 Nov 2018, at 15:58, Eduard Moraru wrote:
>
> On Tue, Nov 13, 2018 at 3:21 PM Vincent Massol wrote:
>
>>
>>
>>> On 13 Nov 2018, at 11:58, Vincent Massol wrote:
>>>
>>> There are 2 questions here:
>>> * Should we add support for MariaDB? And if so which versions. Just
>> found that there’s an official docker image for it so it should be
>> relatively easy to support MariaDB in our docker-based testing framework:
>> https://hub.docker.com/_/mariadb/ (TestContainers also has a wrapper now
>> for MariaDB:
>> https://github.com/testcontainers/testcontainers-java/tree/master/modules/mariadb).
>> Note that the MariaDB versions don’t match the MySQL versions.
>>
>> FTR, I’ve tried adding support for MariaDB and it’s currently not working,
>> because of
>> https://github.com/testcontainers/testcontainers-java/issues/949. But we
>> could provide a PR to them with not so big efforts or using a
>> GenericContainer (less nice).
>>
>
> Maybe I'm misunderstanding, but it looks like we're mixing XWiki's support
> of the MariaDB database itself with XWiki's test infrastructure's
> capability to support a MariaDB database container, which looks a bit
> off-topic to me. I get that we need it integrated in our tests to detect
> anomalies, but I don't really see it as an eliminatory criterion.
I agree. Some comments:
1) This thread was not about deciding which DB to support. It was to define a
strategy to be more explicit in the versions that we support for the various
already supported DBs.
2) I also started this thread because the goal is to automate the tests. If the
idea is to add more work for manual tests then the answer is no, we don’t want
to increase the # of DBs we support since we don’t have the manpower to do
that. At least I would be against it simply because we can’t do it for
practical purposes.
3) MariaDB support in TC is not a big deal, as I mentioned already (there are
several ways to fix it).
4) As I said on this thread, there are only 2 questions to answer from my POV:
* Should we add support for MariaDB? And if so which versions.
* Should we drop support for MySQL?
Thanks
-Vincent
> Thanks,
> Eduard
>
>
>>
>> Thanks
>> -Vincent
>>
>>> * Should we drop support for MySQL?
>>>
>>> Thanks
>>> -Vincent
>>>
On 13 Nov 2018, at 11:50, Guillaume Delhumeau <
>> guillaume.delhum...@xwiki.com> wrote:
Hello,
We are in a weird situation where we don't say we support MariaDB but
"the latest
MySQL version of stable Debian repository", which is currently...
>> MariaDB
[1]
So we need to update our strategy about this fact. I am currently
>> setting
up a server with debian 9 (stable) and I don't know if I should install
MySQL from the Oracle repository our continue with the standard debian
package (MariaDB).
On my side, I am not against aligning ourself to debian. Basically, all
users installing XWiki with our Debian packages are using MariaDB for a
year now [2], and we never encounter any problem so far.
Thanks,
[1] https://packages.debian.org/stretch/default-mysql-server (dep:
mariadb-server-10.1)
[2] https://www.debian.org/News/2017/20170617.en.html
Le lun. 12 nov. 2018 à 18:54, Thomas Mortagne <
>> thomas.morta...@xwiki.com> a
écrit :
> Indeed mysql-server package (version 5.5.) leads to
> mariadb-server-10.1 in current stretch repository.
>
> What is surprising is that this is not the case for sid which is more
> or less supposed to be the future. It's also not the case in Ubuntu
> which is doing the same thing as sid.
> On Mon, Nov 12, 2018 at 6:22 PM Eduard Moraru
> wrote:
>>
>> I am not up to date on the topic, but I would like to add the fact
>> that
>> Debian 9 ("stretch") has actually dropped MySQL and moved officially
>> to
>> MariaDB, forcefully migrating existing MySQL installed versions to
> MariaDB.
>>
>>
>
>> https://www.debian.org/releases/stable/amd64/release-notes/ch-whats-new.en.html#mariadb-replaces-mysql
>>
>> The default mysql-server package now redirects to MariaDB instead.
>>
>> If we are going to follow Debian's lead, we might want to at least
> consider
>> this move.
>>
>> Thanks,
>> Eduard
>>
>> On Mon, Nov 12, 2018 at 6:38 PM Vincent Massol
> wrote:
>>
>>>
>>>
On 12 Nov 2018, at 16:52, Vincent Massol
>> wrote:
So we need to conclude on this thread. I’m proposing to update the
> page
>>> with:
* HSQLDB - Latest only
* MySQL - latest of oldstable/stable/unstable from
>>>
>
>> https://packages.debian.org/search?keywords=mysql-server=names=1
>>> (i.e. latest of 5.5.x and 5.7.x today)
* PostgreSQL - latest of oldstable/stable/unstable fromhttps://
>>>
>>
Re: [xwiki-devs] [Proposal] Update database support strategy
On Tue, Nov 13, 2018 at 3:21 PM Vincent Massol wrote:
>
>
> > On 13 Nov 2018, at 11:58, Vincent Massol wrote:
> >
> > There are 2 questions here:
> > * Should we add support for MariaDB? And if so which versions. Just
> found that there’s an official docker image for it so it should be
> relatively easy to support MariaDB in our docker-based testing framework:
> https://hub.docker.com/_/mariadb/ (TestContainers also has a wrapper now
> for MariaDB:
> https://github.com/testcontainers/testcontainers-java/tree/master/modules/mariadb).
> Note that the MariaDB versions don’t match the MySQL versions.
>
> FTR, I’ve tried adding support for MariaDB and it’s currently not working,
> because of
> https://github.com/testcontainers/testcontainers-java/issues/949. But we
> could provide a PR to them with not so big efforts or using a
> GenericContainer (less nice).
>
Maybe I'm misunderstanding, but it looks like we're mixing XWiki's support
of the MariaDB database itself with XWiki's test infrastructure's
capability to support a MariaDB database container, which looks a bit
off-topic to me. I get that we need it integrated in our tests to detect
anomalies, but I don't really see it as an eliminatory criterion.
Thanks,
Eduard
>
> Thanks
> -Vincent
>
> > * Should we drop support for MySQL?
> >
> > Thanks
> > -Vincent
> >
> >> On 13 Nov 2018, at 11:50, Guillaume Delhumeau <
> guillaume.delhum...@xwiki.com> wrote:
> >>
> >> Hello,
> >>
> >> We are in a weird situation where we don't say we support MariaDB but
> >> "the latest
> >> MySQL version of stable Debian repository", which is currently...
> MariaDB
> >> [1]
> >>
> >> So we need to update our strategy about this fact. I am currently
> setting
> >> up a server with debian 9 (stable) and I don't know if I should install
> >> MySQL from the Oracle repository our continue with the standard debian
> >> package (MariaDB).
> >>
> >> On my side, I am not against aligning ourself to debian. Basically, all
> >> users installing XWiki with our Debian packages are using MariaDB for a
> >> year now [2], and we never encounter any problem so far.
> >>
> >> Thanks,
> >>
> >> [1] https://packages.debian.org/stretch/default-mysql-server (dep:
> >> mariadb-server-10.1)
> >> [2] https://www.debian.org/News/2017/20170617.en.html
> >>
> >> Le lun. 12 nov. 2018 à 18:54, Thomas Mortagne <
> thomas.morta...@xwiki.com> a
> >> écrit :
> >>
> >>> Indeed mysql-server package (version 5.5.) leads to
> >>> mariadb-server-10.1 in current stretch repository.
> >>>
> >>> What is surprising is that this is not the case for sid which is more
> >>> or less supposed to be the future. It's also not the case in Ubuntu
> >>> which is doing the same thing as sid.
> >>> On Mon, Nov 12, 2018 at 6:22 PM Eduard Moraru
> >>> wrote:
>
> I am not up to date on the topic, but I would like to add the fact
> that
> Debian 9 ("stretch") has actually dropped MySQL and moved officially
> to
> MariaDB, forcefully migrating existing MySQL installed versions to
> >>> MariaDB.
>
>
> >>>
> https://www.debian.org/releases/stable/amd64/release-notes/ch-whats-new.en.html#mariadb-replaces-mysql
>
> The default mysql-server package now redirects to MariaDB instead.
>
> If we are going to follow Debian's lead, we might want to at least
> >>> consider
> this move.
>
> Thanks,
> Eduard
>
> On Mon, Nov 12, 2018 at 6:38 PM Vincent Massol
> >>> wrote:
>
> >
> >
> >> On 12 Nov 2018, at 16:52, Vincent Massol
> wrote:
> >>
> >> So we need to conclude on this thread. I’m proposing to update the
> >>> page
> > with:
> >>
> >> * HSQLDB - Latest only
> >> * MySQL - latest of oldstable/stable/unstable from
> >
> >>>
> https://packages.debian.org/search?keywords=mysql-server=names=1
> > (i.e. latest of 5.5.x and 5.7.x today)
> >> * PostgreSQL - latest of oldstable/stable/unstable fromhttps://
> >
> packages.debian.org/search?keywords=postgresql=names=1
> > (i.e. latest of 9.4.x, 9.6.x and 11.x today)
> >> * Oracle - latest of 12.x (we currently test on 11.x AFAIK so we
> >>> need to
> > start testing on 12.x from now on)
> >>
> >> Note that by “support" we mean test on. And it’s not because a
> >>> version
> > is not supported that it doesn’t work nor that we won’t fix it if a
> >>> problem
> > happens.
> >>
> >> I hesitated a long time for the mysql/pgsql versions since I wanted
> >>> only
> > a single version supported, but since we provide a debian packaging
> it
> > makes sense to test the versions defined by the debian repos, and now
> >>> that
> > we have automated functional tests on various configurations, we can
> >>> test
> > on them. BTW I suggest we run all tests on the latest version only
> >>> (i.e.
> > 5.7.x for mysql and 11.x for postgresql, and move to mysql 8.x when
> we
> >>> fix
> > the bug on it) and then we do
Re: [xwiki-devs] [Proposal] Update database support strategy
> On 13 Nov 2018, at 11:58, Vincent Massol wrote:
>
> There are 2 questions here:
> * Should we add support for MariaDB? And if so which versions. Just found
> that there’s an official docker image for it so it should be relatively easy
> to support MariaDB in our docker-based testing framework:
> https://hub.docker.com/_/mariadb/ (TestContainers also has a wrapper now for
> MariaDB:
> https://github.com/testcontainers/testcontainers-java/tree/master/modules/mariadb).
> Note that the MariaDB versions don’t match the MySQL versions.
FTR, I’ve tried adding support for MariaDB and it’s currently not working,
because of https://github.com/testcontainers/testcontainers-java/issues/949.
But we could provide a PR to them with not so big efforts or using a
GenericContainer (less nice).
Thanks
-Vincent
> * Should we drop support for MySQL?
>
> Thanks
> -Vincent
>
>> On 13 Nov 2018, at 11:50, Guillaume Delhumeau
>> wrote:
>>
>> Hello,
>>
>> We are in a weird situation where we don't say we support MariaDB but
>> "the latest
>> MySQL version of stable Debian repository", which is currently... MariaDB
>> [1]
>>
>> So we need to update our strategy about this fact. I am currently setting
>> up a server with debian 9 (stable) and I don't know if I should install
>> MySQL from the Oracle repository our continue with the standard debian
>> package (MariaDB).
>>
>> On my side, I am not against aligning ourself to debian. Basically, all
>> users installing XWiki with our Debian packages are using MariaDB for a
>> year now [2], and we never encounter any problem so far.
>>
>> Thanks,
>>
>> [1] https://packages.debian.org/stretch/default-mysql-server (dep:
>> mariadb-server-10.1)
>> [2] https://www.debian.org/News/2017/20170617.en.html
>>
>> Le lun. 12 nov. 2018 à 18:54, Thomas Mortagne a
>> écrit :
>>
>>> Indeed mysql-server package (version 5.5.) leads to
>>> mariadb-server-10.1 in current stretch repository.
>>>
>>> What is surprising is that this is not the case for sid which is more
>>> or less supposed to be the future. It's also not the case in Ubuntu
>>> which is doing the same thing as sid.
>>> On Mon, Nov 12, 2018 at 6:22 PM Eduard Moraru
>>> wrote:
I am not up to date on the topic, but I would like to add the fact that
Debian 9 ("stretch") has actually dropped MySQL and moved officially to
MariaDB, forcefully migrating existing MySQL installed versions to
>>> MariaDB.
>>> https://www.debian.org/releases/stable/amd64/release-notes/ch-whats-new.en.html#mariadb-replaces-mysql
The default mysql-server package now redirects to MariaDB instead.
If we are going to follow Debian's lead, we might want to at least
>>> consider
this move.
Thanks,
Eduard
On Mon, Nov 12, 2018 at 6:38 PM Vincent Massol
>>> wrote:
>
>
>> On 12 Nov 2018, at 16:52, Vincent Massol wrote:
>>
>> So we need to conclude on this thread. I’m proposing to update the
>>> page
> with:
>>
>> * HSQLDB - Latest only
>> * MySQL - latest of oldstable/stable/unstable from
>
>>> https://packages.debian.org/search?keywords=mysql-server=names=1
> (i.e. latest of 5.5.x and 5.7.x today)
>> * PostgreSQL - latest of oldstable/stable/unstable fromhttps://
> packages.debian.org/search?keywords=postgresql=names=1
> (i.e. latest of 9.4.x, 9.6.x and 11.x today)
>> * Oracle - latest of 12.x (we currently test on 11.x AFAIK so we
>>> need to
> start testing on 12.x from now on)
>>
>> Note that by “support" we mean test on. And it’s not because a
>>> version
> is not supported that it doesn’t work nor that we won’t fix it if a
>>> problem
> happens.
>>
>> I hesitated a long time for the mysql/pgsql versions since I wanted
>>> only
> a single version supported, but since we provide a debian packaging it
> makes sense to test the versions defined by the debian repos, and now
>>> that
> we have automated functional tests on various configurations, we can
>>> test
> on them. BTW I suggest we run all tests on the latest version only
>>> (i.e.
> 5.7.x for mysql and 11.x for postgresql, and move to mysql 8.x when we
>>> fix
> the bug on it) and then we do smoke tests on the other versions.
>>
>> Let me know quickly if you have a problem with this strategy since
>>> I’d
> like to update the page + add the configs in our CI tests.
>
> FYI, I’ve now updated the page at
> https://dev.xwiki.org/xwiki/bin/view/Community/DatabaseSupportStrategy
> (but I can update/revert if need be).
>
> Thanks
> -Vincent
>
>>
>> Thanks
>> -Vincent
>>
>>
>>> On 31 Oct 2018, at 09:06, Vincent Massol
>>> wrote:
>>>
>>> Hi devs,
>>>
>>> We currently have
> https://dev.xwiki.org/xwiki/bin/view/Community/DatabaseSupportStrategy
>>>
>>> However, it doesn’t say
Re: [xwiki-devs] [Proposal] Update database support strategy
There are 2 questions here:
* Should we add support for MariaDB? And if so which versions. Just found that
there’s an official docker image for it so it should be relatively easy to
support MariaDB in our docker-based testing framework:
https://hub.docker.com/_/mariadb/ (TestContainers also has a wrapper now for
MariaDB:
https://github.com/testcontainers/testcontainers-java/tree/master/modules/mariadb).
Note that the MariaDB versions don’t match the MySQL versions.
* Should we drop support for MySQL?
Thanks
-Vincent
> On 13 Nov 2018, at 11:50, Guillaume Delhumeau
> wrote:
>
> Hello,
>
> We are in a weird situation where we don't say we support MariaDB but
> "the latest
> MySQL version of stable Debian repository", which is currently... MariaDB
> [1]
>
> So we need to update our strategy about this fact. I am currently setting
> up a server with debian 9 (stable) and I don't know if I should install
> MySQL from the Oracle repository our continue with the standard debian
> package (MariaDB).
>
> On my side, I am not against aligning ourself to debian. Basically, all
> users installing XWiki with our Debian packages are using MariaDB for a
> year now [2], and we never encounter any problem so far.
>
> Thanks,
>
> [1] https://packages.debian.org/stretch/default-mysql-server (dep:
> mariadb-server-10.1)
> [2] https://www.debian.org/News/2017/20170617.en.html
>
> Le lun. 12 nov. 2018 à 18:54, Thomas Mortagne a
> écrit :
>
>> Indeed mysql-server package (version 5.5.) leads to
>> mariadb-server-10.1 in current stretch repository.
>>
>> What is surprising is that this is not the case for sid which is more
>> or less supposed to be the future. It's also not the case in Ubuntu
>> which is doing the same thing as sid.
>> On Mon, Nov 12, 2018 at 6:22 PM Eduard Moraru
>> wrote:
>>>
>>> I am not up to date on the topic, but I would like to add the fact that
>>> Debian 9 ("stretch") has actually dropped MySQL and moved officially to
>>> MariaDB, forcefully migrating existing MySQL installed versions to
>> MariaDB.
>>>
>>>
>> https://www.debian.org/releases/stable/amd64/release-notes/ch-whats-new.en.html#mariadb-replaces-mysql
>>>
>>> The default mysql-server package now redirects to MariaDB instead.
>>>
>>> If we are going to follow Debian's lead, we might want to at least
>> consider
>>> this move.
>>>
>>> Thanks,
>>> Eduard
>>>
>>> On Mon, Nov 12, 2018 at 6:38 PM Vincent Massol
>> wrote:
>>>
> On 12 Nov 2018, at 16:52, Vincent Massol wrote:
>
> So we need to conclude on this thread. I’m proposing to update the
>> page
with:
>
> * HSQLDB - Latest only
> * MySQL - latest of oldstable/stable/unstable from
>> https://packages.debian.org/search?keywords=mysql-server=names=1
(i.e. latest of 5.5.x and 5.7.x today)
> * PostgreSQL - latest of oldstable/stable/unstable fromhttps://
packages.debian.org/search?keywords=postgresql=names=1
(i.e. latest of 9.4.x, 9.6.x and 11.x today)
> * Oracle - latest of 12.x (we currently test on 11.x AFAIK so we
>> need to
start testing on 12.x from now on)
>
> Note that by “support" we mean test on. And it’s not because a
>> version
is not supported that it doesn’t work nor that we won’t fix it if a
>> problem
happens.
>
> I hesitated a long time for the mysql/pgsql versions since I wanted
>> only
a single version supported, but since we provide a debian packaging it
makes sense to test the versions defined by the debian repos, and now
>> that
we have automated functional tests on various configurations, we can
>> test
on them. BTW I suggest we run all tests on the latest version only
>> (i.e.
5.7.x for mysql and 11.x for postgresql, and move to mysql 8.x when we
>> fix
the bug on it) and then we do smoke tests on the other versions.
>
> Let me know quickly if you have a problem with this strategy since
>> I’d
like to update the page + add the configs in our CI tests.
FYI, I’ve now updated the page at
https://dev.xwiki.org/xwiki/bin/view/Community/DatabaseSupportStrategy
(but I can update/revert if need be).
Thanks
-Vincent
>
> Thanks
> -Vincent
>
>
>> On 31 Oct 2018, at 09:06, Vincent Massol
>> wrote:
>>
>> Hi devs,
>>
>> We currently have
https://dev.xwiki.org/xwiki/bin/view/Community/DatabaseSupportStrategy
>>
>> However, it doesn’t say explicitly which versions we officially
>> support:
>> * For HSQLDB it says 2.3.3 which is wrong since the latest version
>> is
2.4.1
>> * For MySQL it says 5.x but doesn’t specify which specific
>> version(s)
>> * Same for other DBs
>>
>> We cannot really support every versions since supporting means
>> testing
too.
>>
>> So what I propose:
>>
>> Question 1: definition
>>
>> * We say we support the latest stable
Re: [xwiki-devs] [Proposal] Update database support strategy
Hello,
We are in a weird situation where we don't say we support MariaDB but
"the latest
MySQL version of stable Debian repository", which is currently... MariaDB
[1]
So we need to update our strategy about this fact. I am currently setting
up a server with debian 9 (stable) and I don't know if I should install
MySQL from the Oracle repository our continue with the standard debian
package (MariaDB).
On my side, I am not against aligning ourself to debian. Basically, all
users installing XWiki with our Debian packages are using MariaDB for a
year now [2], and we never encounter any problem so far.
Thanks,
[1] https://packages.debian.org/stretch/default-mysql-server (dep:
mariadb-server-10.1)
[2] https://www.debian.org/News/2017/20170617.en.html
Le lun. 12 nov. 2018 à 18:54, Thomas Mortagne a
écrit :
> Indeed mysql-server package (version 5.5.) leads to
> mariadb-server-10.1 in current stretch repository.
>
> What is surprising is that this is not the case for sid which is more
> or less supposed to be the future. It's also not the case in Ubuntu
> which is doing the same thing as sid.
> On Mon, Nov 12, 2018 at 6:22 PM Eduard Moraru
> wrote:
> >
> > I am not up to date on the topic, but I would like to add the fact that
> > Debian 9 ("stretch") has actually dropped MySQL and moved officially to
> > MariaDB, forcefully migrating existing MySQL installed versions to
> MariaDB.
> >
> >
> https://www.debian.org/releases/stable/amd64/release-notes/ch-whats-new.en.html#mariadb-replaces-mysql
> >
> > The default mysql-server package now redirects to MariaDB instead.
> >
> > If we are going to follow Debian's lead, we might want to at least
> consider
> > this move.
> >
> > Thanks,
> > Eduard
> >
> > On Mon, Nov 12, 2018 at 6:38 PM Vincent Massol
> wrote:
> >
> > >
> > >
> > > > On 12 Nov 2018, at 16:52, Vincent Massol wrote:
> > > >
> > > > So we need to conclude on this thread. I’m proposing to update the
> page
> > > with:
> > > >
> > > > * HSQLDB - Latest only
> > > > * MySQL - latest of oldstable/stable/unstable from
> > >
> https://packages.debian.org/search?keywords=mysql-server=names=1
> > > (i.e. latest of 5.5.x and 5.7.x today)
> > > > * PostgreSQL - latest of oldstable/stable/unstable fromhttps://
> > > packages.debian.org/search?keywords=postgresql=names=1
> > > (i.e. latest of 9.4.x, 9.6.x and 11.x today)
> > > > * Oracle - latest of 12.x (we currently test on 11.x AFAIK so we
> need to
> > > start testing on 12.x from now on)
> > > >
> > > > Note that by “support" we mean test on. And it’s not because a
> version
> > > is not supported that it doesn’t work nor that we won’t fix it if a
> problem
> > > happens.
> > > >
> > > > I hesitated a long time for the mysql/pgsql versions since I wanted
> only
> > > a single version supported, but since we provide a debian packaging it
> > > makes sense to test the versions defined by the debian repos, and now
> that
> > > we have automated functional tests on various configurations, we can
> test
> > > on them. BTW I suggest we run all tests on the latest version only
> (i.e.
> > > 5.7.x for mysql and 11.x for postgresql, and move to mysql 8.x when we
> fix
> > > the bug on it) and then we do smoke tests on the other versions.
> > > >
> > > > Let me know quickly if you have a problem with this strategy since
> I’d
> > > like to update the page + add the configs in our CI tests.
> > >
> > > FYI, I’ve now updated the page at
> > > https://dev.xwiki.org/xwiki/bin/view/Community/DatabaseSupportStrategy
> > > (but I can update/revert if need be).
> > >
> > > Thanks
> > > -Vincent
> > >
> > > >
> > > > Thanks
> > > > -Vincent
> > > >
> > > >
> > > >> On 31 Oct 2018, at 09:06, Vincent Massol
> wrote:
> > > >>
> > > >> Hi devs,
> > > >>
> > > >> We currently have
> > > https://dev.xwiki.org/xwiki/bin/view/Community/DatabaseSupportStrategy
> > > >>
> > > >> However, it doesn’t say explicitly which versions we officially
> support:
> > > >> * For HSQLDB it says 2.3.3 which is wrong since the latest version
> is
> > > 2.4.1
> > > >> * For MySQL it says 5.x but doesn’t specify which specific
> version(s)
> > > >> * Same for other DBs
> > > >>
> > > >> We cannot really support every versions since supporting means
> testing
> > > too.
> > > >>
> > > >> So what I propose:
> > > >>
> > > >> Question 1: definition
> > > >>
> > > >> * We say we support the latest stable version of the databases for a
> > > given version cycle
> > > >> ** For MySQL, it’s the latest of the 5.x cycle, which is 5.7.24 as
> of
> > > today (see https://hub.docker.com/_/mysql/)
> > > >> ** For PostgreSQL, it’s the latest of the 9.x cycle, which is
> 9.6.10
> > > as of today (see https://hub.docker.com/_/postgres/)
> > > >> ** For Oracle, it’s the latest of the 11.x cycle, which is
> 11.2.0.4.0
> > > as of today (see
> > >
> https://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html
> > > )
> > > >>
> > > >> Question 2: review what we support
> > > >>
> > > >>
Re: [xwiki-devs] [Proposal] Update database support strategy
Indeed mysql-server package (version 5.5.) leads to
mariadb-server-10.1 in current stretch repository.
What is surprising is that this is not the case for sid which is more
or less supposed to be the future. It's also not the case in Ubuntu
which is doing the same thing as sid.
On Mon, Nov 12, 2018 at 6:22 PM Eduard Moraru wrote:
>
> I am not up to date on the topic, but I would like to add the fact that
> Debian 9 ("stretch") has actually dropped MySQL and moved officially to
> MariaDB, forcefully migrating existing MySQL installed versions to MariaDB.
>
> https://www.debian.org/releases/stable/amd64/release-notes/ch-whats-new.en.html#mariadb-replaces-mysql
>
> The default mysql-server package now redirects to MariaDB instead.
>
> If we are going to follow Debian's lead, we might want to at least consider
> this move.
>
> Thanks,
> Eduard
>
> On Mon, Nov 12, 2018 at 6:38 PM Vincent Massol wrote:
>
> >
> >
> > > On 12 Nov 2018, at 16:52, Vincent Massol wrote:
> > >
> > > So we need to conclude on this thread. I’m proposing to update the page
> > with:
> > >
> > > * HSQLDB - Latest only
> > > * MySQL - latest of oldstable/stable/unstable from
> > https://packages.debian.org/search?keywords=mysql-server=names=1
> > (i.e. latest of 5.5.x and 5.7.x today)
> > > * PostgreSQL - latest of oldstable/stable/unstable fromhttps://
> > packages.debian.org/search?keywords=postgresql=names=1
> > (i.e. latest of 9.4.x, 9.6.x and 11.x today)
> > > * Oracle - latest of 12.x (we currently test on 11.x AFAIK so we need to
> > start testing on 12.x from now on)
> > >
> > > Note that by “support" we mean test on. And it’s not because a version
> > is not supported that it doesn’t work nor that we won’t fix it if a problem
> > happens.
> > >
> > > I hesitated a long time for the mysql/pgsql versions since I wanted only
> > a single version supported, but since we provide a debian packaging it
> > makes sense to test the versions defined by the debian repos, and now that
> > we have automated functional tests on various configurations, we can test
> > on them. BTW I suggest we run all tests on the latest version only (i.e.
> > 5.7.x for mysql and 11.x for postgresql, and move to mysql 8.x when we fix
> > the bug on it) and then we do smoke tests on the other versions.
> > >
> > > Let me know quickly if you have a problem with this strategy since I’d
> > like to update the page + add the configs in our CI tests.
> >
> > FYI, I’ve now updated the page at
> > https://dev.xwiki.org/xwiki/bin/view/Community/DatabaseSupportStrategy
> > (but I can update/revert if need be).
> >
> > Thanks
> > -Vincent
> >
> > >
> > > Thanks
> > > -Vincent
> > >
> > >
> > >> On 31 Oct 2018, at 09:06, Vincent Massol wrote:
> > >>
> > >> Hi devs,
> > >>
> > >> We currently have
> > https://dev.xwiki.org/xwiki/bin/view/Community/DatabaseSupportStrategy
> > >>
> > >> However, it doesn’t say explicitly which versions we officially support:
> > >> * For HSQLDB it says 2.3.3 which is wrong since the latest version is
> > 2.4.1
> > >> * For MySQL it says 5.x but doesn’t specify which specific version(s)
> > >> * Same for other DBs
> > >>
> > >> We cannot really support every versions since supporting means testing
> > too.
> > >>
> > >> So what I propose:
> > >>
> > >> Question 1: definition
> > >>
> > >> * We say we support the latest stable version of the databases for a
> > given version cycle
> > >> ** For MySQL, it’s the latest of the 5.x cycle, which is 5.7.24 as of
> > today (see https://hub.docker.com/_/mysql/)
> > >> ** For PostgreSQL, it’s the latest of the 9.x cycle, which is 9.6.10
> > as of today (see https://hub.docker.com/_/postgres/)
> > >> ** For Oracle, it’s the latest of the 11.x cycle, which is 11.2.0.4.0
> > as of today (see
> > https://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html
> > )
> > >>
> > >> Question 2: review what we support
> > >>
> > >> * For MySQL I think we could also start supporting MySQL 8.x (ie the
> > latest version of that cycle). We have an issue open for it currently:
> > https://jira.xwiki.org/browse/XWIKI-15215
> > >> * For PostgreSQL we could also start supporting versions 11.x (ie the
> > latest version of that cycle)
> > >> * For Oracle, we could also start supporting versions 12.x (ie the
> > latest version of that cycle)
> > >>
> > >> Question 3: decide if we drop some support
> > >>
> > >> * Is there any cycle that we should support for? Right now I think that
> > MySQL 5.x is still heavily used, same for postgreSQL 9.x I guess. Don’t
> > know for Oracle.
> > >> * Any idea?
> > >>
> > >> So WDYT about the 3 questions?
> > >>
> > >> Thanks
> > >> -Vincent
> > >
> >
> >
--
Thomas Mortagne
Re: [xwiki-devs] [Proposal] Update database support strategy
I am not up to date on the topic, but I would like to add the fact that
Debian 9 ("stretch") has actually dropped MySQL and moved officially to
MariaDB, forcefully migrating existing MySQL installed versions to MariaDB.
https://www.debian.org/releases/stable/amd64/release-notes/ch-whats-new.en.html#mariadb-replaces-mysql
The default mysql-server package now redirects to MariaDB instead.
If we are going to follow Debian's lead, we might want to at least consider
this move.
Thanks,
Eduard
On Mon, Nov 12, 2018 at 6:38 PM Vincent Massol wrote:
>
>
> > On 12 Nov 2018, at 16:52, Vincent Massol wrote:
> >
> > So we need to conclude on this thread. I’m proposing to update the page
> with:
> >
> > * HSQLDB - Latest only
> > * MySQL - latest of oldstable/stable/unstable from
> https://packages.debian.org/search?keywords=mysql-server=names=1
> (i.e. latest of 5.5.x and 5.7.x today)
> > * PostgreSQL - latest of oldstable/stable/unstable fromhttps://
> packages.debian.org/search?keywords=postgresql=names=1
> (i.e. latest of 9.4.x, 9.6.x and 11.x today)
> > * Oracle - latest of 12.x (we currently test on 11.x AFAIK so we need to
> start testing on 12.x from now on)
> >
> > Note that by “support" we mean test on. And it’s not because a version
> is not supported that it doesn’t work nor that we won’t fix it if a problem
> happens.
> >
> > I hesitated a long time for the mysql/pgsql versions since I wanted only
> a single version supported, but since we provide a debian packaging it
> makes sense to test the versions defined by the debian repos, and now that
> we have automated functional tests on various configurations, we can test
> on them. BTW I suggest we run all tests on the latest version only (i.e.
> 5.7.x for mysql and 11.x for postgresql, and move to mysql 8.x when we fix
> the bug on it) and then we do smoke tests on the other versions.
> >
> > Let me know quickly if you have a problem with this strategy since I’d
> like to update the page + add the configs in our CI tests.
>
> FYI, I’ve now updated the page at
> https://dev.xwiki.org/xwiki/bin/view/Community/DatabaseSupportStrategy
> (but I can update/revert if need be).
>
> Thanks
> -Vincent
>
> >
> > Thanks
> > -Vincent
> >
> >
> >> On 31 Oct 2018, at 09:06, Vincent Massol wrote:
> >>
> >> Hi devs,
> >>
> >> We currently have
> https://dev.xwiki.org/xwiki/bin/view/Community/DatabaseSupportStrategy
> >>
> >> However, it doesn’t say explicitly which versions we officially support:
> >> * For HSQLDB it says 2.3.3 which is wrong since the latest version is
> 2.4.1
> >> * For MySQL it says 5.x but doesn’t specify which specific version(s)
> >> * Same for other DBs
> >>
> >> We cannot really support every versions since supporting means testing
> too.
> >>
> >> So what I propose:
> >>
> >> Question 1: definition
> >>
> >> * We say we support the latest stable version of the databases for a
> given version cycle
> >> ** For MySQL, it’s the latest of the 5.x cycle, which is 5.7.24 as of
> today (see https://hub.docker.com/_/mysql/)
> >> ** For PostgreSQL, it’s the latest of the 9.x cycle, which is 9.6.10
> as of today (see https://hub.docker.com/_/postgres/)
> >> ** For Oracle, it’s the latest of the 11.x cycle, which is 11.2.0.4.0
> as of today (see
> https://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html
> )
> >>
> >> Question 2: review what we support
> >>
> >> * For MySQL I think we could also start supporting MySQL 8.x (ie the
> latest version of that cycle). We have an issue open for it currently:
> https://jira.xwiki.org/browse/XWIKI-15215
> >> * For PostgreSQL we could also start supporting versions 11.x (ie the
> latest version of that cycle)
> >> * For Oracle, we could also start supporting versions 12.x (ie the
> latest version of that cycle)
> >>
> >> Question 3: decide if we drop some support
> >>
> >> * Is there any cycle that we should support for? Right now I think that
> MySQL 5.x is still heavily used, same for postgreSQL 9.x I guess. Don’t
> know for Oracle.
> >> * Any idea?
> >>
> >> So WDYT about the 3 questions?
> >>
> >> Thanks
> >> -Vincent
> >
>
>
Re: [xwiki-devs] [Proposal] Update database support strategy
Looking good. And it's fine to take the Debian version. On Mon, Nov 12, 2018 at 6:37 PM Vincent Massol wrote: > > > > On 12 Nov 2018, at 16:52, Vincent Massol wrote: > > > > So we need to conclude on this thread. I’m proposing to update the page > with: > > > > * HSQLDB - Latest only > > * MySQL - latest of oldstable/stable/unstable from > https://packages.debian.org/search?keywords=mysql-server=names=1 > (i.e. latest of 5.5.x and 5.7.x today) > > * PostgreSQL - latest of oldstable/stable/unstable fromhttps:// > packages.debian.org/search?keywords=postgresql=names=1 > (i.e. latest of 9.4.x, 9.6.x and 11.x today) > > * Oracle - latest of 12.x (we currently test on 11.x AFAIK so we need to > start testing on 12.x from now on) > > > > Note that by “support" we mean test on. And it’s not because a version > is not supported that it doesn’t work nor that we won’t fix it if a problem > happens. > > > > I hesitated a long time for the mysql/pgsql versions since I wanted only > a single version supported, but since we provide a debian packaging it > makes sense to test the versions defined by the debian repos, and now that > we have automated functional tests on various configurations, we can test > on them. BTW I suggest we run all tests on the latest version only (i.e. > 5.7.x for mysql and 11.x for postgresql, and move to mysql 8.x when we fix > the bug on it) and then we do smoke tests on the other versions. > > > > Let me know quickly if you have a problem with this strategy since I’d > like to update the page + add the configs in our CI tests. > > FYI, I’ve now updated the page at > https://dev.xwiki.org/xwiki/bin/view/Community/DatabaseSupportStrategy > (but I can update/revert if need be). > > Thanks > -Vincent > > > > > Thanks > > -Vincent > > > > > >> On 31 Oct 2018, at 09:06, Vincent Massol wrote: > >> > >> Hi devs, > >> > >> We currently have > https://dev.xwiki.org/xwiki/bin/view/Community/DatabaseSupportStrategy > >> > >> However, it doesn’t say explicitly which versions we officially support: > >> * For HSQLDB it says 2.3.3 which is wrong since the latest version is > 2.4.1 > >> * For MySQL it says 5.x but doesn’t specify which specific version(s) > >> * Same for other DBs > >> > >> We cannot really support every versions since supporting means testing > too. > >> > >> So what I propose: > >> > >> Question 1: definition > >> > >> * We say we support the latest stable version of the databases for a > given version cycle > >> ** For MySQL, it’s the latest of the 5.x cycle, which is 5.7.24 as of > today (see https://hub.docker.com/_/mysql/) > >> ** For PostgreSQL, it’s the latest of the 9.x cycle, which is 9.6.10 > as of today (see https://hub.docker.com/_/postgres/) > >> ** For Oracle, it’s the latest of the 11.x cycle, which is 11.2.0.4.0 > as of today (see > https://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html > ) > >> > >> Question 2: review what we support > >> > >> * For MySQL I think we could also start supporting MySQL 8.x (ie the > latest version of that cycle). We have an issue open for it currently: > https://jira.xwiki.org/browse/XWIKI-15215 > >> * For PostgreSQL we could also start supporting versions 11.x (ie the > latest version of that cycle) > >> * For Oracle, we could also start supporting versions 12.x (ie the > latest version of that cycle) > >> > >> Question 3: decide if we drop some support > >> > >> * Is there any cycle that we should support for? Right now I think that > MySQL 5.x is still heavily used, same for postgreSQL 9.x I guess. Don’t > know for Oracle. > >> * Any idea? > >> > >> So WDYT about the 3 questions? > >> > >> Thanks > >> -Vincent > > > >
Re: [xwiki-devs] [Proposal] Update database support strategy
+1 On Mon, Nov 12, 2018 at 5:37 PM Vincent Massol wrote: > > > > > On 12 Nov 2018, at 16:52, Vincent Massol wrote: > > > > So we need to conclude on this thread. I’m proposing to update the page > > with: > > > > * HSQLDB - Latest only > > * MySQL - latest of oldstable/stable/unstable from > > https://packages.debian.org/search?keywords=mysql-server=names=1 > > (i.e. latest of 5.5.x and 5.7.x today) > > * PostgreSQL - latest of oldstable/stable/unstable > > fromhttps://packages.debian.org/search?keywords=postgresql=names=1 > > (i.e. latest of 9.4.x, 9.6.x and 11.x today) > > * Oracle - latest of 12.x (we currently test on 11.x AFAIK so we need to > > start testing on 12.x from now on) > > > > Note that by “support" we mean test on. And it’s not because a version is > > not supported that it doesn’t work nor that we won’t fix it if a problem > > happens. > > > > I hesitated a long time for the mysql/pgsql versions since I wanted only a > > single version supported, but since we provide a debian packaging it makes > > sense to test the versions defined by the debian repos, and now that we > > have automated functional tests on various configurations, we can test on > > them. BTW I suggest we run all tests on the latest version only (i.e. 5.7.x > > for mysql and 11.x for postgresql, and move to mysql 8.x when we fix the > > bug on it) and then we do smoke tests on the other versions. > > > > Let me know quickly if you have a problem with this strategy since I’d like > > to update the page + add the configs in our CI tests. > > FYI, I’ve now updated the page at > https://dev.xwiki.org/xwiki/bin/view/Community/DatabaseSupportStrategy (but I > can update/revert if need be). > > Thanks > -Vincent > > > > > Thanks > > -Vincent > > > > > >> On 31 Oct 2018, at 09:06, Vincent Massol wrote: > >> > >> Hi devs, > >> > >> We currently have > >> https://dev.xwiki.org/xwiki/bin/view/Community/DatabaseSupportStrategy > >> > >> However, it doesn’t say explicitly which versions we officially support: > >> * For HSQLDB it says 2.3.3 which is wrong since the latest version is 2.4.1 > >> * For MySQL it says 5.x but doesn’t specify which specific version(s) > >> * Same for other DBs > >> > >> We cannot really support every versions since supporting means testing too. > >> > >> So what I propose: > >> > >> Question 1: definition > >> > >> * We say we support the latest stable version of the databases for a given > >> version cycle > >> ** For MySQL, it’s the latest of the 5.x cycle, which is 5.7.24 as of > >> today (see https://hub.docker.com/_/mysql/) > >> ** For PostgreSQL, it’s the latest of the 9.x cycle, which is 9.6.10 as > >> of today (see https://hub.docker.com/_/postgres/) > >> ** For Oracle, it’s the latest of the 11.x cycle, which is 11.2.0.4.0 as > >> of today (see > >> https://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html) > >> > >> Question 2: review what we support > >> > >> * For MySQL I think we could also start supporting MySQL 8.x (ie the > >> latest version of that cycle). We have an issue open for it currently: > >> https://jira.xwiki.org/browse/XWIKI-15215 > >> * For PostgreSQL we could also start supporting versions 11.x (ie the > >> latest version of that cycle) > >> * For Oracle, we could also start supporting versions 12.x (ie the latest > >> version of that cycle) > >> > >> Question 3: decide if we drop some support > >> > >> * Is there any cycle that we should support for? Right now I think that > >> MySQL 5.x is still heavily used, same for postgreSQL 9.x I guess. Don’t > >> know for Oracle. > >> * Any idea? > >> > >> So WDYT about the 3 questions? > >> > >> Thanks > >> -Vincent > > > -- Thomas Mortagne
Re: [xwiki-devs] [Proposal] Update database support strategy
> On 12 Nov 2018, at 16:52, Vincent Massol wrote: > > So we need to conclude on this thread. I’m proposing to update the page with: > > * HSQLDB - Latest only > * MySQL - latest of oldstable/stable/unstable from > https://packages.debian.org/search?keywords=mysql-server=names=1 > (i.e. latest of 5.5.x and 5.7.x today) > * PostgreSQL - latest of oldstable/stable/unstable > fromhttps://packages.debian.org/search?keywords=postgresql=names=1 > (i.e. latest of 9.4.x, 9.6.x and 11.x today) > * Oracle - latest of 12.x (we currently test on 11.x AFAIK so we need to > start testing on 12.x from now on) > > Note that by “support" we mean test on. And it’s not because a version is not > supported that it doesn’t work nor that we won’t fix it if a problem happens. > > I hesitated a long time for the mysql/pgsql versions since I wanted only a > single version supported, but since we provide a debian packaging it makes > sense to test the versions defined by the debian repos, and now that we have > automated functional tests on various configurations, we can test on them. > BTW I suggest we run all tests on the latest version only (i.e. 5.7.x for > mysql and 11.x for postgresql, and move to mysql 8.x when we fix the bug on > it) and then we do smoke tests on the other versions. > > Let me know quickly if you have a problem with this strategy since I’d like > to update the page + add the configs in our CI tests. FYI, I’ve now updated the page at https://dev.xwiki.org/xwiki/bin/view/Community/DatabaseSupportStrategy (but I can update/revert if need be). Thanks -Vincent > > Thanks > -Vincent > > >> On 31 Oct 2018, at 09:06, Vincent Massol wrote: >> >> Hi devs, >> >> We currently have >> https://dev.xwiki.org/xwiki/bin/view/Community/DatabaseSupportStrategy >> >> However, it doesn’t say explicitly which versions we officially support: >> * For HSQLDB it says 2.3.3 which is wrong since the latest version is 2.4.1 >> * For MySQL it says 5.x but doesn’t specify which specific version(s) >> * Same for other DBs >> >> We cannot really support every versions since supporting means testing too. >> >> So what I propose: >> >> Question 1: definition >> >> * We say we support the latest stable version of the databases for a given >> version cycle >> ** For MySQL, it’s the latest of the 5.x cycle, which is 5.7.24 as of today >> (see https://hub.docker.com/_/mysql/) >> ** For PostgreSQL, it’s the latest of the 9.x cycle, which is 9.6.10 as of >> today (see https://hub.docker.com/_/postgres/) >> ** For Oracle, it’s the latest of the 11.x cycle, which is 11.2.0.4.0 as of >> today (see >> https://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html) >> >> Question 2: review what we support >> >> * For MySQL I think we could also start supporting MySQL 8.x (ie the latest >> version of that cycle). We have an issue open for it currently: >> https://jira.xwiki.org/browse/XWIKI-15215 >> * For PostgreSQL we could also start supporting versions 11.x (ie the latest >> version of that cycle) >> * For Oracle, we could also start supporting versions 12.x (ie the latest >> version of that cycle) >> >> Question 3: decide if we drop some support >> >> * Is there any cycle that we should support for? Right now I think that >> MySQL 5.x is still heavily used, same for postgreSQL 9.x I guess. Don’t know >> for Oracle. >> * Any idea? >> >> So WDYT about the 3 questions? >> >> Thanks >> -Vincent >
Re: [xwiki-devs] [Proposal] Update database support strategy
So we need to conclude on this thread. I’m proposing to update the page with: * HSQLDB - Latest only * MySQL - latest of oldstable/stable/unstable from https://packages.debian.org/search?keywords=mysql-server=names=1 (i.e. latest of 5.5.x and 5.7.x today) * PostgreSQL - latest of oldstable/stable/unstable fromhttps://packages.debian.org/search?keywords=postgresql=names=1 (i.e. latest of 9.4.x, 9.6.x and 11.x today) * Oracle - latest of 12.x (we currently test on 11.x AFAIK so we need to start testing on 12.x from now on) Note that by “support" we mean test on. And it’s not because a version is not supported that it doesn’t work nor that we won’t fix it if a problem happens. I hesitated a long time for the mysql/pgsql versions since I wanted only a single version supported, but since we provide a debian packaging it makes sense to test the versions defined by the debian repos, and now that we have automated functional tests on various configurations, we can test on them. BTW I suggest we run all tests on the latest version only (i.e. 5.7.x for mysql and 11.x for postgresql, and move to mysql 8.x when we fix the bug on it) and then we do smoke tests on the other versions. Let me know quickly if you have a problem with this strategy since I’d like to update the page + add the configs in our CI tests. Thanks -Vincent > On 31 Oct 2018, at 09:06, Vincent Massol wrote: > > Hi devs, > > We currently have > https://dev.xwiki.org/xwiki/bin/view/Community/DatabaseSupportStrategy > > However, it doesn’t say explicitly which versions we officially support: > * For HSQLDB it says 2.3.3 which is wrong since the latest version is 2.4.1 > * For MySQL it says 5.x but doesn’t specify which specific version(s) > * Same for other DBs > > We cannot really support every versions since supporting means testing too. > > So what I propose: > > Question 1: definition > > * We say we support the latest stable version of the databases for a given > version cycle > ** For MySQL, it’s the latest of the 5.x cycle, which is 5.7.24 as of today > (see https://hub.docker.com/_/mysql/) > ** For PostgreSQL, it’s the latest of the 9.x cycle, which is 9.6.10 as of > today (see https://hub.docker.com/_/postgres/) > ** For Oracle, it’s the latest of the 11.x cycle, which is 11.2.0.4.0 as of > today (see > https://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html) > > Question 2: review what we support > > * For MySQL I think we could also start supporting MySQL 8.x (ie the latest > version of that cycle). We have an issue open for it currently: > https://jira.xwiki.org/browse/XWIKI-15215 > * For PostgreSQL we could also start supporting versions 11.x (ie the latest > version of that cycle) > * For Oracle, we could also start supporting versions 12.x (ie the latest > version of that cycle) > > Question 3: decide if we drop some support > > * Is there any cycle that we should support for? Right now I think that MySQL > 5.x is still heavily used, same for postgreSQL 9.x I guess. Don’t know for > Oracle. > * Any idea? > > So WDYT about the 3 questions? > > Thanks > -Vincent
Re: [xwiki-devs] [Proposal] Update database support strategy
> On 6 Nov 2018, at 10:14, Thomas Mortagne wrote: > > On Wed, Oct 31, 2018 at 4:30 PM Vincent Massol wrote: >> >> >> >>> On 31 Oct 2018, at 16:27, Vincent Massol wrote: >>> >>> >>> On 31 Oct 2018, at 16:19, Ecaterina Moraru (Valica) wrote: On Wed, Oct 31, 2018 at 5:12 PM Vincent Massol wrote: > Hi Caty, > > Thanks but I think we should focus on the databases that our users use for > XWiki. We have that info already with the active installs. > https://www.xwiki.org/xwiki/bin/view/ActiveInstalls/ k, I understand, with the note that those graphs are influenced by what we support. In the case of Active Install, would be nice to display also the DB versions. >>> >>> Yes. However we can’t support all versions and people usually lag behind. >>> So I don’t think we should support more than the latest one. Already hard >>> to do. >>> >>> BTW we do have the versions, we just don’t display them. >>> See http://activeinstalls.xwiki.org/#/dashboard >>> >>> I did a quick pie chart for mysql: >>> https://www.evernote.com/l/AHe-MYCE-09Nuoyau9jFQf45OgtIZKmaqk0 >> >> What’s interesting is that version 8 is not used yet. So we could keep >> staying on 5.x for now probably. > > XWiki does not start at all on MySQL 8 so not sure it's a good criteria :) Good point :) Thanks -Vincent > >> >> Thanks >> -Vincent >> >>> Thanks >>> -Vincent >>> Thanks, Caty > > It’s already a lot of work :) > > My goal with this thread was not fully review the list of supported > databses, just to make it more clear the versions of them we want to > support. > > Thanks > -Vincent > >> On 31 Oct 2018, at 15:57, Ecaterina Moraru (Valica) > wrote: >> >> Another top >> > https://www.eversql.com/most-popular-databases-in-2018-according-to-stackoverflow-survey/ >> >> On Wed, Oct 31, 2018 at 4:45 PM Ecaterina Moraru (Valica) < > vali...@gmail.com> >> wrote: >> >>> >>> >>> On Wed, Oct 31, 2018 at 3:53 PM Vincent Massol > wrote: >>> Hi Caty, > On 31 Oct 2018, at 14:43, Ecaterina Moraru (Valica) < > vali...@gmail.com> wrote: > > IMO we should just write we support: > * HyperSQL 2.x Latest > * MySQL 5.x Latest > * PostgreSQL 9.x Latest > * Oracle 11.x Latest > not sure what help would do to have the explicit 2.4.1, 5.7.24, > 9.6.10, > 11.2.0.4.0 versions. Yes, this is what I proposed. > > Also I'm sure we won't keep up with the versions, so they won't mean > latest. > When we do the tests we should always fix and test on the latest one. > And this 'latest' behavior is consistent with what we do for Browsers, with > the exception that we are a bit more descriptive by giving the DB > cycle. Sure. Note that there’s more in this thread, for example: 1) What does latest mean? 2) What about the other 2 questions I asked? >>> >>> See >>> >>> > https://trends.google.com/trends/explore?cat=13=today%205-y=%2Fm%2F01vw9z,%2Fm%2F04y3k,%2Fm%2F0120vr,%2Fm%2F05ynw,Hyper%20SQL >>> and >>> >>> > https://www.statista.com/statistics/809750/worldwide-popularity-ranking-database-management-systems/ >>> >>> According to those pages my questions are: >>> * Why are we supporting "Hypersonic DB" ? - but hey, apparently it's in >>> the jetty thing. k :) Here we should just say latest, without any > version >>> to it. This DB is anyway only recommended for the demo version. >>> * Why don't we support Microsoft SQL Server? >>> >>> Another reference: >>> https://db-engines.com/en/ranking >>> >>> * MongoDB also is in the top 5 for 2018 in multiple resources. Should / >>> could we also support that? In the Relational Databases section, DB2 is >>> listed, see https://db-engines.com/en/ranking/relational+dbms >>> >>> Anyway, I think it would be enough if we support the top 3 DB for the >>> latest versions. This would mean just MySQL 8.x instead of MySQL 5.x. > Could >>> not find any relevant comparison for DB versions. Found a graph from > 2015 >>> in https://plumbr.io/blog/io/most-popular-relational-databases where >>> MySQL 5.6 was most popular (long time ago), so not sure what we could > use >>> as a reference. On the other hand MySQL 8.0 launched 6 month ago. So >>> indeed, we should support the latest 5.7.x (5.7.24) and also 8.0.x >>> (8.0.13), see https://en.wikipedia.org/wiki/MySQL#Release_history >>> >>> Regarding PostgreSQL, IMO we should support (10.5 || 9.6.10) and 11.0, > see >>>
Re: [xwiki-devs] [Proposal] Update database support strategy
On Wed, Oct 31, 2018 at 4:30 PM Vincent Massol wrote: > > > > > On 31 Oct 2018, at 16:27, Vincent Massol wrote: > > > > > > > >> On 31 Oct 2018, at 16:19, Ecaterina Moraru (Valica) > >> wrote: > >> > >> On Wed, Oct 31, 2018 at 5:12 PM Vincent Massol wrote: > >> > >>> Hi Caty, > >>> > >>> Thanks but I think we should focus on the databases that our users use for > >>> XWiki. We have that info already with the active installs. > >>> > >> > >> https://www.xwiki.org/xwiki/bin/view/ActiveInstalls/ > >> k, I understand, with the note that those graphs are influenced by what we > >> support. > >> In the case of Active Install, would be nice to display also the DB > >> versions. > > > > Yes. However we can’t support all versions and people usually lag behind. > > So I don’t think we should support more than the latest one. Already hard > > to do. > > > > BTW we do have the versions, we just don’t display them. > > See http://activeinstalls.xwiki.org/#/dashboard > > > > I did a quick pie chart for mysql: > > https://www.evernote.com/l/AHe-MYCE-09Nuoyau9jFQf45OgtIZKmaqk0 > > What’s interesting is that version 8 is not used yet. So we could keep > staying on 5.x for now probably. XWiki does not start at all on MySQL 8 so not sure it's a good criteria :) > > Thanks > -Vincent > > > Thanks > > -Vincent > > > >> > >> Thanks, > >> Caty > >> > >> > >>> > >>> It’s already a lot of work :) > >>> > >>> My goal with this thread was not fully review the list of supported > >>> databses, just to make it more clear the versions of them we want to > >>> support. > >>> > >>> Thanks > >>> -Vincent > >>> > On 31 Oct 2018, at 15:57, Ecaterina Moraru (Valica) > >>> wrote: > > Another top > > >>> https://www.eversql.com/most-popular-databases-in-2018-according-to-stackoverflow-survey/ > > On Wed, Oct 31, 2018 at 4:45 PM Ecaterina Moraru (Valica) < > >>> vali...@gmail.com> > wrote: > > > > > > > On Wed, Oct 31, 2018 at 3:53 PM Vincent Massol > >>> wrote: > > > >> Hi Caty, > >> > >>> On 31 Oct 2018, at 14:43, Ecaterina Moraru (Valica) < > >>> vali...@gmail.com> > >> wrote: > >>> > >>> IMO we should just write we support: > >>> * HyperSQL 2.x Latest > >>> * MySQL 5.x Latest > >>> * PostgreSQL 9.x Latest > >>> * Oracle 11.x Latest > >>> not sure what help would do to have the explicit 2.4.1, 5.7.24, > >>> 9.6.10, > >>> 11.2.0.4.0 versions. > >> > >> Yes, this is what I proposed. > >> > >>> > >>> Also I'm sure we won't keep up with the versions, so they won't mean > >>> latest. > >>> When we do the tests we should always fix and test on the latest one. > >>> And this 'latest' behavior is consistent with what we do for Browsers, > >> with > >>> the exception that we are a bit more descriptive by giving the DB > >>> cycle. > >> > >> Sure. Note that there’s more in this thread, for example: > >> > >> 1) What does latest mean? > >> 2) What about the other 2 questions I asked? > >> > > > > See > > > > > >>> https://trends.google.com/trends/explore?cat=13=today%205-y=%2Fm%2F01vw9z,%2Fm%2F04y3k,%2Fm%2F0120vr,%2Fm%2F05ynw,Hyper%20SQL > > and > > > > > >>> https://www.statista.com/statistics/809750/worldwide-popularity-ranking-database-management-systems/ > > > > According to those pages my questions are: > > * Why are we supporting "Hypersonic DB" ? - but hey, apparently it's in > > the jetty thing. k :) Here we should just say latest, without any > >>> version > > to it. This DB is anyway only recommended for the demo version. > > * Why don't we support Microsoft SQL Server? > > > > Another reference: > > https://db-engines.com/en/ranking > > > > * MongoDB also is in the top 5 for 2018 in multiple resources. Should / > > could we also support that? In the Relational Databases section, DB2 is > > listed, see https://db-engines.com/en/ranking/relational+dbms > > > > Anyway, I think it would be enough if we support the top 3 DB for the > > latest versions. This would mean just MySQL 8.x instead of MySQL 5.x. > >>> Could > > not find any relevant comparison for DB versions. Found a graph from > >>> 2015 > > in https://plumbr.io/blog/io/most-popular-relational-databases where > > MySQL 5.6 was most popular (long time ago), so not sure what we could > >>> use > > as a reference. On the other hand MySQL 8.0 launched 6 month ago. So > > indeed, we should support the latest 5.7.x (5.7.24) and also 8.0.x > > (8.0.13), see https://en.wikipedia.org/wiki/MySQL#Release_history > > > > Regarding PostgreSQL, IMO we should support (10.5 || 9.6.10) and 11.0, > >>> see > > https://en.wikipedia.org/wiki/PostgreSQL#Release_history > > > > Regarding Oracle Database, we should support 12.2.0.1 and 18.1.0, see > >
Re: [xwiki-devs] [Proposal] Update database support strategy
On Wed, Oct 31, 2018 at 5:28 PM Vincent Massol wrote: > > > > On 31 Oct 2018, at 16:19, Ecaterina Moraru (Valica) > wrote: > > > > On Wed, Oct 31, 2018 at 5:12 PM Vincent Massol > wrote: > > > >> Hi Caty, > >> > >> Thanks but I think we should focus on the databases that our users use > for > >> XWiki. We have that info already with the active installs. > >> > > > > https://www.xwiki.org/xwiki/bin/view/ActiveInstalls/ > > k, I understand, with the note that those graphs are influenced by what > we > > support. > > In the case of Active Install, would be nice to display also the DB > > versions. > > Yes. However we can’t support all versions and people usually lag behind. > So I don’t think we should support more than the latest one. Already hard > to do. > > BTW we do have the versions, we just don’t display them. > See http://activeinstalls.xwiki.org/#/dashboard > > I did a quick pie chart for mysql: > https://www.evernote.com/l/AHe-MYCE-09Nuoyau9jFQf45OgtIZKmaqk0 Thanks > > > Thanks > -Vincent > > > > > Thanks, > > Caty > > > > > >> > >> It’s already a lot of work :) > >> > >> My goal with this thread was not fully review the list of supported > >> databses, just to make it more clear the versions of them we want to > >> support. > >> > >> Thanks > >> -Vincent > >> > >>> On 31 Oct 2018, at 15:57, Ecaterina Moraru (Valica) > > >> wrote: > >>> > >>> Another top > >>> > >> > https://www.eversql.com/most-popular-databases-in-2018-according-to-stackoverflow-survey/ > >>> > >>> On Wed, Oct 31, 2018 at 4:45 PM Ecaterina Moraru (Valica) < > >> vali...@gmail.com> > >>> wrote: > >>> > > > On Wed, Oct 31, 2018 at 3:53 PM Vincent Massol > >> wrote: > > > Hi Caty, > > > >> On 31 Oct 2018, at 14:43, Ecaterina Moraru (Valica) < > >> vali...@gmail.com> > > wrote: > >> > >> IMO we should just write we support: > >> * HyperSQL 2.x Latest > >> * MySQL 5.x Latest > >> * PostgreSQL 9.x Latest > >> * Oracle 11.x Latest > >> not sure what help would do to have the explicit 2.4.1, 5.7.24, > >> 9.6.10, > >> 11.2.0.4.0 versions. > > > > Yes, this is what I proposed. > > > >> > >> Also I'm sure we won't keep up with the versions, so they won't mean > >> latest. > >> When we do the tests we should always fix and test on the latest > one. > >> And this 'latest' behavior is consistent with what we do for > Browsers, > > with > >> the exception that we are a bit more descriptive by giving the DB > >> cycle. > > > > Sure. Note that there’s more in this thread, for example: > > > > 1) What does latest mean? > > 2) What about the other 2 questions I asked? > > > > See > > > >> > https://trends.google.com/trends/explore?cat=13=today%205-y=%2Fm%2F01vw9z,%2Fm%2F04y3k,%2Fm%2F0120vr,%2Fm%2F05ynw,Hyper%20SQL > and > > > >> > https://www.statista.com/statistics/809750/worldwide-popularity-ranking-database-management-systems/ > > According to those pages my questions are: > * Why are we supporting "Hypersonic DB" ? - but hey, apparently it's > in > the jetty thing. k :) Here we should just say latest, without any > >> version > to it. This DB is anyway only recommended for the demo version. > * Why don't we support Microsoft SQL Server? > > Another reference: > https://db-engines.com/en/ranking > > * MongoDB also is in the top 5 for 2018 in multiple resources. Should > / > could we also support that? In the Relational Databases section, DB2 > is > listed, see https://db-engines.com/en/ranking/relational+dbms > > Anyway, I think it would be enough if we support the top 3 DB for the > latest versions. This would mean just MySQL 8.x instead of MySQL 5.x. > >> Could > not find any relevant comparison for DB versions. Found a graph from > >> 2015 > in https://plumbr.io/blog/io/most-popular-relational-databases where > MySQL 5.6 was most popular (long time ago), so not sure what we could > >> use > as a reference. On the other hand MySQL 8.0 launched 6 month ago. So > indeed, we should support the latest 5.7.x (5.7.24) and also 8.0.x > (8.0.13), see https://en.wikipedia.org/wiki/MySQL#Release_history > > Regarding PostgreSQL, IMO we should support (10.5 || 9.6.10) and 11.0, > >> see > https://en.wikipedia.org/wiki/PostgreSQL#Release_history > > Regarding Oracle Database, we should support 12.2.0.1 and 18.1.0, see > https://en.wikipedia.org/wiki/Oracle_Database#Releases_and_versions > > Regarding Microsoft SQL Server it should be (in case we decide it) SQL > Server 2017, see > https://en.wikipedia.org/wiki/Microsoft_SQL_Server#Currently > > My rule was: latest/latest + the latest stable/previous version. > > Thanks, > Caty > > > > > > WDYT about that? > > > > Thanks >
Re: [xwiki-devs] [Proposal] Update database support strategy
> On 31 Oct 2018, at 16:27, Vincent Massol wrote: > > > >> On 31 Oct 2018, at 16:19, Ecaterina Moraru (Valica) >> wrote: >> >> On Wed, Oct 31, 2018 at 5:12 PM Vincent Massol wrote: >> >>> Hi Caty, >>> >>> Thanks but I think we should focus on the databases that our users use for >>> XWiki. We have that info already with the active installs. >>> >> >> https://www.xwiki.org/xwiki/bin/view/ActiveInstalls/ >> k, I understand, with the note that those graphs are influenced by what we >> support. >> In the case of Active Install, would be nice to display also the DB >> versions. > > Yes. However we can’t support all versions and people usually lag behind. So > I don’t think we should support more than the latest one. Already hard to do. > > BTW we do have the versions, we just don’t display them. > See http://activeinstalls.xwiki.org/#/dashboard > > I did a quick pie chart for mysql: > https://www.evernote.com/l/AHe-MYCE-09Nuoyau9jFQf45OgtIZKmaqk0 What’s interesting is that version 8 is not used yet. So we could keep staying on 5.x for now probably. Thanks -Vincent > Thanks > -Vincent > >> >> Thanks, >> Caty >> >> >>> >>> It’s already a lot of work :) >>> >>> My goal with this thread was not fully review the list of supported >>> databses, just to make it more clear the versions of them we want to >>> support. >>> >>> Thanks >>> -Vincent >>> On 31 Oct 2018, at 15:57, Ecaterina Moraru (Valica) >>> wrote: Another top >>> https://www.eversql.com/most-popular-databases-in-2018-according-to-stackoverflow-survey/ On Wed, Oct 31, 2018 at 4:45 PM Ecaterina Moraru (Valica) < >>> vali...@gmail.com> wrote: > > > On Wed, Oct 31, 2018 at 3:53 PM Vincent Massol >>> wrote: > >> Hi Caty, >> >>> On 31 Oct 2018, at 14:43, Ecaterina Moraru (Valica) < >>> vali...@gmail.com> >> wrote: >>> >>> IMO we should just write we support: >>> * HyperSQL 2.x Latest >>> * MySQL 5.x Latest >>> * PostgreSQL 9.x Latest >>> * Oracle 11.x Latest >>> not sure what help would do to have the explicit 2.4.1, 5.7.24, >>> 9.6.10, >>> 11.2.0.4.0 versions. >> >> Yes, this is what I proposed. >> >>> >>> Also I'm sure we won't keep up with the versions, so they won't mean >>> latest. >>> When we do the tests we should always fix and test on the latest one. >>> And this 'latest' behavior is consistent with what we do for Browsers, >> with >>> the exception that we are a bit more descriptive by giving the DB >>> cycle. >> >> Sure. Note that there’s more in this thread, for example: >> >> 1) What does latest mean? >> 2) What about the other 2 questions I asked? >> > > See > > >>> https://trends.google.com/trends/explore?cat=13=today%205-y=%2Fm%2F01vw9z,%2Fm%2F04y3k,%2Fm%2F0120vr,%2Fm%2F05ynw,Hyper%20SQL > and > > >>> https://www.statista.com/statistics/809750/worldwide-popularity-ranking-database-management-systems/ > > According to those pages my questions are: > * Why are we supporting "Hypersonic DB" ? - but hey, apparently it's in > the jetty thing. k :) Here we should just say latest, without any >>> version > to it. This DB is anyway only recommended for the demo version. > * Why don't we support Microsoft SQL Server? > > Another reference: > https://db-engines.com/en/ranking > > * MongoDB also is in the top 5 for 2018 in multiple resources. Should / > could we also support that? In the Relational Databases section, DB2 is > listed, see https://db-engines.com/en/ranking/relational+dbms > > Anyway, I think it would be enough if we support the top 3 DB for the > latest versions. This would mean just MySQL 8.x instead of MySQL 5.x. >>> Could > not find any relevant comparison for DB versions. Found a graph from >>> 2015 > in https://plumbr.io/blog/io/most-popular-relational-databases where > MySQL 5.6 was most popular (long time ago), so not sure what we could >>> use > as a reference. On the other hand MySQL 8.0 launched 6 month ago. So > indeed, we should support the latest 5.7.x (5.7.24) and also 8.0.x > (8.0.13), see https://en.wikipedia.org/wiki/MySQL#Release_history > > Regarding PostgreSQL, IMO we should support (10.5 || 9.6.10) and 11.0, >>> see > https://en.wikipedia.org/wiki/PostgreSQL#Release_history > > Regarding Oracle Database, we should support 12.2.0.1 and 18.1.0, see > https://en.wikipedia.org/wiki/Oracle_Database#Releases_and_versions > > Regarding Microsoft SQL Server it should be (in case we decide it) SQL > Server 2017, see > https://en.wikipedia.org/wiki/Microsoft_SQL_Server#Currently > > My rule was: latest/latest + the latest stable/previous version. > > Thanks, > Caty > > >> >> WDYT about that? >> >> Thanks
Re: [xwiki-devs] [Proposal] Update database support strategy
> On 31 Oct 2018, at 16:19, Ecaterina Moraru (Valica) wrote: > > On Wed, Oct 31, 2018 at 5:12 PM Vincent Massol wrote: > >> Hi Caty, >> >> Thanks but I think we should focus on the databases that our users use for >> XWiki. We have that info already with the active installs. >> > > https://www.xwiki.org/xwiki/bin/view/ActiveInstalls/ > k, I understand, with the note that those graphs are influenced by what we > support. > In the case of Active Install, would be nice to display also the DB > versions. Yes. However we can’t support all versions and people usually lag behind. So I don’t think we should support more than the latest one. Already hard to do. BTW we do have the versions, we just don’t display them. See http://activeinstalls.xwiki.org/#/dashboard I did a quick pie chart for mysql: https://www.evernote.com/l/AHe-MYCE-09Nuoyau9jFQf45OgtIZKmaqk0 Thanks -Vincent > > Thanks, > Caty > > >> >> It’s already a lot of work :) >> >> My goal with this thread was not fully review the list of supported >> databses, just to make it more clear the versions of them we want to >> support. >> >> Thanks >> -Vincent >> >>> On 31 Oct 2018, at 15:57, Ecaterina Moraru (Valica) >> wrote: >>> >>> Another top >>> >> https://www.eversql.com/most-popular-databases-in-2018-according-to-stackoverflow-survey/ >>> >>> On Wed, Oct 31, 2018 at 4:45 PM Ecaterina Moraru (Valica) < >> vali...@gmail.com> >>> wrote: >>> On Wed, Oct 31, 2018 at 3:53 PM Vincent Massol >> wrote: > Hi Caty, > >> On 31 Oct 2018, at 14:43, Ecaterina Moraru (Valica) < >> vali...@gmail.com> > wrote: >> >> IMO we should just write we support: >> * HyperSQL 2.x Latest >> * MySQL 5.x Latest >> * PostgreSQL 9.x Latest >> * Oracle 11.x Latest >> not sure what help would do to have the explicit 2.4.1, 5.7.24, >> 9.6.10, >> 11.2.0.4.0 versions. > > Yes, this is what I proposed. > >> >> Also I'm sure we won't keep up with the versions, so they won't mean >> latest. >> When we do the tests we should always fix and test on the latest one. >> And this 'latest' behavior is consistent with what we do for Browsers, > with >> the exception that we are a bit more descriptive by giving the DB >> cycle. > > Sure. Note that there’s more in this thread, for example: > > 1) What does latest mean? > 2) What about the other 2 questions I asked? > See >> https://trends.google.com/trends/explore?cat=13=today%205-y=%2Fm%2F01vw9z,%2Fm%2F04y3k,%2Fm%2F0120vr,%2Fm%2F05ynw,Hyper%20SQL and >> https://www.statista.com/statistics/809750/worldwide-popularity-ranking-database-management-systems/ According to those pages my questions are: * Why are we supporting "Hypersonic DB" ? - but hey, apparently it's in the jetty thing. k :) Here we should just say latest, without any >> version to it. This DB is anyway only recommended for the demo version. * Why don't we support Microsoft SQL Server? Another reference: https://db-engines.com/en/ranking * MongoDB also is in the top 5 for 2018 in multiple resources. Should / could we also support that? In the Relational Databases section, DB2 is listed, see https://db-engines.com/en/ranking/relational+dbms Anyway, I think it would be enough if we support the top 3 DB for the latest versions. This would mean just MySQL 8.x instead of MySQL 5.x. >> Could not find any relevant comparison for DB versions. Found a graph from >> 2015 in https://plumbr.io/blog/io/most-popular-relational-databases where MySQL 5.6 was most popular (long time ago), so not sure what we could >> use as a reference. On the other hand MySQL 8.0 launched 6 month ago. So indeed, we should support the latest 5.7.x (5.7.24) and also 8.0.x (8.0.13), see https://en.wikipedia.org/wiki/MySQL#Release_history Regarding PostgreSQL, IMO we should support (10.5 || 9.6.10) and 11.0, >> see https://en.wikipedia.org/wiki/PostgreSQL#Release_history Regarding Oracle Database, we should support 12.2.0.1 and 18.1.0, see https://en.wikipedia.org/wiki/Oracle_Database#Releases_and_versions Regarding Microsoft SQL Server it should be (in case we decide it) SQL Server 2017, see https://en.wikipedia.org/wiki/Microsoft_SQL_Server#Currently My rule was: latest/latest + the latest stable/previous version. Thanks, Caty > > WDYT about that? > > Thanks > -Vincent > > >> >> Thanks, >> Caty >> >> >> On Wed, Oct 31, 2018 at 12:11 PM Simon Urli > wrote: >> >>> >>> >>> On 31/10/2018 10:52, Thomas Mortagne wrote: On Wed, Oct 31, 2018 at 10:28 AM Vincent Massol >> >>> wrote: > > > >>
Re: [xwiki-devs] [Proposal] Update database support strategy
On Wed, Oct 31, 2018 at 5:12 PM Vincent Massol wrote: > Hi Caty, > > Thanks but I think we should focus on the databases that our users use for > XWiki. We have that info already with the active installs. > https://www.xwiki.org/xwiki/bin/view/ActiveInstalls/ k, I understand, with the note that those graphs are influenced by what we support. In the case of Active Install, would be nice to display also the DB versions. Thanks, Caty > > It’s already a lot of work :) > > My goal with this thread was not fully review the list of supported > databses, just to make it more clear the versions of them we want to > support. > > Thanks > -Vincent > > > On 31 Oct 2018, at 15:57, Ecaterina Moraru (Valica) > wrote: > > > > Another top > > > https://www.eversql.com/most-popular-databases-in-2018-according-to-stackoverflow-survey/ > > > > On Wed, Oct 31, 2018 at 4:45 PM Ecaterina Moraru (Valica) < > vali...@gmail.com> > > wrote: > > > >> > >> > >> On Wed, Oct 31, 2018 at 3:53 PM Vincent Massol > wrote: > >> > >>> Hi Caty, > >>> > On 31 Oct 2018, at 14:43, Ecaterina Moraru (Valica) < > vali...@gmail.com> > >>> wrote: > > IMO we should just write we support: > * HyperSQL 2.x Latest > * MySQL 5.x Latest > * PostgreSQL 9.x Latest > * Oracle 11.x Latest > not sure what help would do to have the explicit 2.4.1, 5.7.24, > 9.6.10, > 11.2.0.4.0 versions. > >>> > >>> Yes, this is what I proposed. > >>> > > Also I'm sure we won't keep up with the versions, so they won't mean > latest. > When we do the tests we should always fix and test on the latest one. > And this 'latest' behavior is consistent with what we do for Browsers, > >>> with > the exception that we are a bit more descriptive by giving the DB > cycle. > >>> > >>> Sure. Note that there’s more in this thread, for example: > >>> > >>> 1) What does latest mean? > >>> 2) What about the other 2 questions I asked? > >>> > >> > >> See > >> > >> > https://trends.google.com/trends/explore?cat=13=today%205-y=%2Fm%2F01vw9z,%2Fm%2F04y3k,%2Fm%2F0120vr,%2Fm%2F05ynw,Hyper%20SQL > >> and > >> > >> > https://www.statista.com/statistics/809750/worldwide-popularity-ranking-database-management-systems/ > >> > >> According to those pages my questions are: > >> * Why are we supporting "Hypersonic DB" ? - but hey, apparently it's in > >> the jetty thing. k :) Here we should just say latest, without any > version > >> to it. This DB is anyway only recommended for the demo version. > >> * Why don't we support Microsoft SQL Server? > >> > >> Another reference: > >> https://db-engines.com/en/ranking > >> > >> * MongoDB also is in the top 5 for 2018 in multiple resources. Should / > >> could we also support that? In the Relational Databases section, DB2 is > >> listed, see https://db-engines.com/en/ranking/relational+dbms > >> > >> Anyway, I think it would be enough if we support the top 3 DB for the > >> latest versions. This would mean just MySQL 8.x instead of MySQL 5.x. > Could > >> not find any relevant comparison for DB versions. Found a graph from > 2015 > >> in https://plumbr.io/blog/io/most-popular-relational-databases where > >> MySQL 5.6 was most popular (long time ago), so not sure what we could > use > >> as a reference. On the other hand MySQL 8.0 launched 6 month ago. So > >> indeed, we should support the latest 5.7.x (5.7.24) and also 8.0.x > >> (8.0.13), see https://en.wikipedia.org/wiki/MySQL#Release_history > >> > >> Regarding PostgreSQL, IMO we should support (10.5 || 9.6.10) and 11.0, > see > >> https://en.wikipedia.org/wiki/PostgreSQL#Release_history > >> > >> Regarding Oracle Database, we should support 12.2.0.1 and 18.1.0, see > >> https://en.wikipedia.org/wiki/Oracle_Database#Releases_and_versions > >> > >> Regarding Microsoft SQL Server it should be (in case we decide it) SQL > >> Server 2017, see > >> https://en.wikipedia.org/wiki/Microsoft_SQL_Server#Currently > >> > >> My rule was: latest/latest + the latest stable/previous version. > >> > >> Thanks, > >> Caty > >> > >> > >>> > >>> WDYT about that? > >>> > >>> Thanks > >>> -Vincent > >>> > >>> > > Thanks, > Caty > > > On Wed, Oct 31, 2018 at 12:11 PM Simon Urli > >>> wrote: > > > > > > > On 31/10/2018 10:52, Thomas Mortagne wrote: > >> On Wed, Oct 31, 2018 at 10:28 AM Vincent Massol > > > wrote: > >>> > >>> > >>> > On 31 Oct 2018, at 10:15, Simon Urli > wrote: > > Hi, > > On 31/10/2018 09:06, Vincent Massol wrote: > > Hi devs, > > We currently have > > > https://dev.xwiki.org/xwiki/bin/view/Community/DatabaseSupportStrategy > > However, it doesn’t say explicitly which versions we officially > > support: > > * For HSQLDB it says 2.3.3 which is wrong since the latest > version > >>> is > > 2.4.1 > > * For MySQL it says 5.x but doesn’t specify which specific > >>> version(s)
Re: [xwiki-devs] [Proposal] Update database support strategy
Hi Caty, Thanks but I think we should focus on the databases that our users use for XWiki. We have that info already with the active installs. It’s already a lot of work :) My goal with this thread was not fully review the list of supported databses, just to make it more clear the versions of them we want to support. Thanks -Vincent > On 31 Oct 2018, at 15:57, Ecaterina Moraru (Valica) wrote: > > Another top > https://www.eversql.com/most-popular-databases-in-2018-according-to-stackoverflow-survey/ > > On Wed, Oct 31, 2018 at 4:45 PM Ecaterina Moraru (Valica) > wrote: > >> >> >> On Wed, Oct 31, 2018 at 3:53 PM Vincent Massol wrote: >> >>> Hi Caty, >>> On 31 Oct 2018, at 14:43, Ecaterina Moraru (Valica) >>> wrote: IMO we should just write we support: * HyperSQL 2.x Latest * MySQL 5.x Latest * PostgreSQL 9.x Latest * Oracle 11.x Latest not sure what help would do to have the explicit 2.4.1, 5.7.24, 9.6.10, 11.2.0.4.0 versions. >>> >>> Yes, this is what I proposed. >>> Also I'm sure we won't keep up with the versions, so they won't mean latest. When we do the tests we should always fix and test on the latest one. And this 'latest' behavior is consistent with what we do for Browsers, >>> with the exception that we are a bit more descriptive by giving the DB cycle. >>> >>> Sure. Note that there’s more in this thread, for example: >>> >>> 1) What does latest mean? >>> 2) What about the other 2 questions I asked? >>> >> >> See >> >> https://trends.google.com/trends/explore?cat=13=today%205-y=%2Fm%2F01vw9z,%2Fm%2F04y3k,%2Fm%2F0120vr,%2Fm%2F05ynw,Hyper%20SQL >> and >> >> https://www.statista.com/statistics/809750/worldwide-popularity-ranking-database-management-systems/ >> >> According to those pages my questions are: >> * Why are we supporting "Hypersonic DB" ? - but hey, apparently it's in >> the jetty thing. k :) Here we should just say latest, without any version >> to it. This DB is anyway only recommended for the demo version. >> * Why don't we support Microsoft SQL Server? >> >> Another reference: >> https://db-engines.com/en/ranking >> >> * MongoDB also is in the top 5 for 2018 in multiple resources. Should / >> could we also support that? In the Relational Databases section, DB2 is >> listed, see https://db-engines.com/en/ranking/relational+dbms >> >> Anyway, I think it would be enough if we support the top 3 DB for the >> latest versions. This would mean just MySQL 8.x instead of MySQL 5.x. Could >> not find any relevant comparison for DB versions. Found a graph from 2015 >> in https://plumbr.io/blog/io/most-popular-relational-databases where >> MySQL 5.6 was most popular (long time ago), so not sure what we could use >> as a reference. On the other hand MySQL 8.0 launched 6 month ago. So >> indeed, we should support the latest 5.7.x (5.7.24) and also 8.0.x >> (8.0.13), see https://en.wikipedia.org/wiki/MySQL#Release_history >> >> Regarding PostgreSQL, IMO we should support (10.5 || 9.6.10) and 11.0, see >> https://en.wikipedia.org/wiki/PostgreSQL#Release_history >> >> Regarding Oracle Database, we should support 12.2.0.1 and 18.1.0, see >> https://en.wikipedia.org/wiki/Oracle_Database#Releases_and_versions >> >> Regarding Microsoft SQL Server it should be (in case we decide it) SQL >> Server 2017, see >> https://en.wikipedia.org/wiki/Microsoft_SQL_Server#Currently >> >> My rule was: latest/latest + the latest stable/previous version. >> >> Thanks, >> Caty >> >> >>> >>> WDYT about that? >>> >>> Thanks >>> -Vincent >>> >>> Thanks, Caty On Wed, Oct 31, 2018 at 12:11 PM Simon Urli >>> wrote: > > > On 31/10/2018 10:52, Thomas Mortagne wrote: >> On Wed, Oct 31, 2018 at 10:28 AM Vincent Massol > wrote: >>> >>> >>> On 31 Oct 2018, at 10:15, Simon Urli wrote: Hi, On 31/10/2018 09:06, Vincent Massol wrote: > Hi devs, > We currently have > https://dev.xwiki.org/xwiki/bin/view/Community/DatabaseSupportStrategy > However, it doesn’t say explicitly which versions we officially > support: > * For HSQLDB it says 2.3.3 which is wrong since the latest version >>> is > 2.4.1 > * For MySQL it says 5.x but doesn’t specify which specific >>> version(s) > * Same for other DBs > We cannot really support every versions since supporting means > testing too. > So what I propose: > Question 1: definition > * We say we support the latest stable version of the databases for >>> a > given version cycle > ** For MySQL, it’s the latest of the 5.x cycle, which is 5.7.24 as >>> of > today (see https://hub.docker.com/_/mysql/) > ** For PostgreSQL, it’s the latest of the 9.x cycle, which is >>> 9.6.10 > as of today (see https://hub.docker.com/_/postgres/) > ** For
Re: [xwiki-devs] [Proposal] Update database support strategy
Another top https://www.eversql.com/most-popular-databases-in-2018-according-to-stackoverflow-survey/ On Wed, Oct 31, 2018 at 4:45 PM Ecaterina Moraru (Valica) wrote: > > > On Wed, Oct 31, 2018 at 3:53 PM Vincent Massol wrote: > >> Hi Caty, >> >> > On 31 Oct 2018, at 14:43, Ecaterina Moraru (Valica) >> wrote: >> > >> > IMO we should just write we support: >> > * HyperSQL 2.x Latest >> > * MySQL 5.x Latest >> > * PostgreSQL 9.x Latest >> > * Oracle 11.x Latest >> > not sure what help would do to have the explicit 2.4.1, 5.7.24, 9.6.10, >> > 11.2.0.4.0 versions. >> >> Yes, this is what I proposed. >> >> > >> > Also I'm sure we won't keep up with the versions, so they won't mean >> > latest. >> > When we do the tests we should always fix and test on the latest one. >> > And this 'latest' behavior is consistent with what we do for Browsers, >> with >> > the exception that we are a bit more descriptive by giving the DB cycle. >> >> Sure. Note that there’s more in this thread, for example: >> >> 1) What does latest mean? >> 2) What about the other 2 questions I asked? >> > > See > > https://trends.google.com/trends/explore?cat=13=today%205-y=%2Fm%2F01vw9z,%2Fm%2F04y3k,%2Fm%2F0120vr,%2Fm%2F05ynw,Hyper%20SQL > and > > https://www.statista.com/statistics/809750/worldwide-popularity-ranking-database-management-systems/ > > According to those pages my questions are: > * Why are we supporting "Hypersonic DB" ? - but hey, apparently it's in > the jetty thing. k :) Here we should just say latest, without any version > to it. This DB is anyway only recommended for the demo version. > * Why don't we support Microsoft SQL Server? > > Another reference: > https://db-engines.com/en/ranking > > * MongoDB also is in the top 5 for 2018 in multiple resources. Should / > could we also support that? In the Relational Databases section, DB2 is > listed, see https://db-engines.com/en/ranking/relational+dbms > > Anyway, I think it would be enough if we support the top 3 DB for the > latest versions. This would mean just MySQL 8.x instead of MySQL 5.x. Could > not find any relevant comparison for DB versions. Found a graph from 2015 > in https://plumbr.io/blog/io/most-popular-relational-databases where > MySQL 5.6 was most popular (long time ago), so not sure what we could use > as a reference. On the other hand MySQL 8.0 launched 6 month ago. So > indeed, we should support the latest 5.7.x (5.7.24) and also 8.0.x > (8.0.13), see https://en.wikipedia.org/wiki/MySQL#Release_history > > Regarding PostgreSQL, IMO we should support (10.5 || 9.6.10) and 11.0, see > https://en.wikipedia.org/wiki/PostgreSQL#Release_history > > Regarding Oracle Database, we should support 12.2.0.1 and 18.1.0, see > https://en.wikipedia.org/wiki/Oracle_Database#Releases_and_versions > > Regarding Microsoft SQL Server it should be (in case we decide it) SQL > Server 2017, see > https://en.wikipedia.org/wiki/Microsoft_SQL_Server#Currently > > My rule was: latest/latest + the latest stable/previous version. > > Thanks, > Caty > > >> >> WDYT about that? >> >> Thanks >> -Vincent >> >> >> > >> > Thanks, >> > Caty >> > >> > >> > On Wed, Oct 31, 2018 at 12:11 PM Simon Urli >> wrote: >> > >> >> >> >> >> >> On 31/10/2018 10:52, Thomas Mortagne wrote: >> >>> On Wed, Oct 31, 2018 at 10:28 AM Vincent Massol >> >> wrote: >> >> >> >> > On 31 Oct 2018, at 10:15, Simon Urli wrote: >> > >> > Hi, >> > >> > On 31/10/2018 09:06, Vincent Massol wrote: >> >> Hi devs, >> >> We currently have >> >> https://dev.xwiki.org/xwiki/bin/view/Community/DatabaseSupportStrategy >> >> However, it doesn’t say explicitly which versions we officially >> >> support: >> >> * For HSQLDB it says 2.3.3 which is wrong since the latest version >> is >> >> 2.4.1 >> >> * For MySQL it says 5.x but doesn’t specify which specific >> version(s) >> >> * Same for other DBs >> >> We cannot really support every versions since supporting means >> >> testing too. >> >> So what I propose: >> >> Question 1: definition >> >> * We say we support the latest stable version of the databases for >> a >> >> given version cycle >> >> ** For MySQL, it’s the latest of the 5.x cycle, which is 5.7.24 as >> of >> >> today (see https://hub.docker.com/_/mysql/) >> >> ** For PostgreSQL, it’s the latest of the 9.x cycle, which is >> 9.6.10 >> >> as of today (see https://hub.docker.com/_/postgres/) >> >> ** For Oracle, it’s the latest of the 11.x cycle, which is >> 11.2.0.4.0 >> >> as of today (see >> >> >> https://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html >> >> ) >> > >> > +1 >> > >> >> Question 2: review what we support >> >> * For MySQL I think we could also start supporting MySQL 8.x (ie >> the >> >> latest version of that cycle). We have an issue open for it currently: >> >> https://jira.xwiki.org/browse/XWIKI-15215 >> >> * For PostgreSQL we could also start supporting versions
Re: [xwiki-devs] [Proposal] Update database support strategy
On Wed, Oct 31, 2018 at 3:53 PM Vincent Massol wrote: > Hi Caty, > > > On 31 Oct 2018, at 14:43, Ecaterina Moraru (Valica) > wrote: > > > > IMO we should just write we support: > > * HyperSQL 2.x Latest > > * MySQL 5.x Latest > > * PostgreSQL 9.x Latest > > * Oracle 11.x Latest > > not sure what help would do to have the explicit 2.4.1, 5.7.24, 9.6.10, > > 11.2.0.4.0 versions. > > Yes, this is what I proposed. > > > > > Also I'm sure we won't keep up with the versions, so they won't mean > > latest. > > When we do the tests we should always fix and test on the latest one. > > And this 'latest' behavior is consistent with what we do for Browsers, > with > > the exception that we are a bit more descriptive by giving the DB cycle. > > Sure. Note that there’s more in this thread, for example: > > 1) What does latest mean? > 2) What about the other 2 questions I asked? > See https://trends.google.com/trends/explore?cat=13=today%205-y=%2Fm%2F01vw9z,%2Fm%2F04y3k,%2Fm%2F0120vr,%2Fm%2F05ynw,Hyper%20SQL and https://www.statista.com/statistics/809750/worldwide-popularity-ranking-database-management-systems/ According to those pages my questions are: * Why are we supporting "Hypersonic DB" ? - but hey, apparently it's in the jetty thing. k :) Here we should just say latest, without any version to it. This DB is anyway only recommended for the demo version. * Why don't we support Microsoft SQL Server? Another reference: https://db-engines.com/en/ranking * MongoDB also is in the top 5 for 2018 in multiple resources. Should / could we also support that? In the Relational Databases section, DB2 is listed, see https://db-engines.com/en/ranking/relational+dbms Anyway, I think it would be enough if we support the top 3 DB for the latest versions. This would mean just MySQL 8.x instead of MySQL 5.x. Could not find any relevant comparison for DB versions. Found a graph from 2015 in https://plumbr.io/blog/io/most-popular-relational-databases where MySQL 5.6 was most popular (long time ago), so not sure what we could use as a reference. On the other hand MySQL 8.0 launched 6 month ago. So indeed, we should support the latest 5.7.x (5.7.24) and also 8.0.x (8.0.13), see https://en.wikipedia.org/wiki/MySQL#Release_history Regarding PostgreSQL, IMO we should support (10.5 || 9.6.10) and 11.0, see https://en.wikipedia.org/wiki/PostgreSQL#Release_history Regarding Oracle Database, we should support 12.2.0.1 and 18.1.0, see https://en.wikipedia.org/wiki/Oracle_Database#Releases_and_versions Regarding Microsoft SQL Server it should be (in case we decide it) SQL Server 2017, see https://en.wikipedia.org/wiki/Microsoft_SQL_Server#Currently My rule was: latest/latest + the latest stable/previous version. Thanks, Caty > > WDYT about that? > > Thanks > -Vincent > > > > > > Thanks, > > Caty > > > > > > On Wed, Oct 31, 2018 at 12:11 PM Simon Urli > wrote: > > > >> > >> > >> On 31/10/2018 10:52, Thomas Mortagne wrote: > >>> On Wed, Oct 31, 2018 at 10:28 AM Vincent Massol > >> wrote: > > > > > On 31 Oct 2018, at 10:15, Simon Urli wrote: > > > > Hi, > > > > On 31/10/2018 09:06, Vincent Massol wrote: > >> Hi devs, > >> We currently have > >> https://dev.xwiki.org/xwiki/bin/view/Community/DatabaseSupportStrategy > >> However, it doesn’t say explicitly which versions we officially > >> support: > >> * For HSQLDB it says 2.3.3 which is wrong since the latest version > is > >> 2.4.1 > >> * For MySQL it says 5.x but doesn’t specify which specific > version(s) > >> * Same for other DBs > >> We cannot really support every versions since supporting means > >> testing too. > >> So what I propose: > >> Question 1: definition > >> * We say we support the latest stable version of the databases for a > >> given version cycle > >> ** For MySQL, it’s the latest of the 5.x cycle, which is 5.7.24 as > of > >> today (see https://hub.docker.com/_/mysql/) > >> ** For PostgreSQL, it’s the latest of the 9.x cycle, which is > 9.6.10 > >> as of today (see https://hub.docker.com/_/postgres/) > >> ** For Oracle, it’s the latest of the 11.x cycle, which is > 11.2.0.4.0 > >> as of today (see > >> > https://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html > >> ) > > > > +1 > > > >> Question 2: review what we support > >> * For MySQL I think we could also start supporting MySQL 8.x (ie the > >> latest version of that cycle). We have an issue open for it currently: > >> https://jira.xwiki.org/browse/XWIKI-15215 > >> * For PostgreSQL we could also start supporting versions 11.x (ie > the > >> latest version of that cycle) > >> * For Oracle, we could also start supporting versions 12.x (ie the > >> latest version of that cycle) > > > > +0 I don't really know how much effort it involves to ensure the > >> support of the latest version of each database and to fix the bugs > >> accordingly. > > > >>
Re: [xwiki-devs] [Proposal] Update database support strategy
Hi Caty, > On 31 Oct 2018, at 14:43, Ecaterina Moraru (Valica) wrote: > > IMO we should just write we support: > * HyperSQL 2.x Latest > * MySQL 5.x Latest > * PostgreSQL 9.x Latest > * Oracle 11.x Latest > not sure what help would do to have the explicit 2.4.1, 5.7.24, 9.6.10, > 11.2.0.4.0 versions. Yes, this is what I proposed. > > Also I'm sure we won't keep up with the versions, so they won't mean > latest. > When we do the tests we should always fix and test on the latest one. > And this 'latest' behavior is consistent with what we do for Browsers, with > the exception that we are a bit more descriptive by giving the DB cycle. Sure. Note that there’s more in this thread, for example: 1) What does latest mean? 2) What about the other 2 questions I asked? WDYT about that? Thanks -Vincent > > Thanks, > Caty > > > On Wed, Oct 31, 2018 at 12:11 PM Simon Urli wrote: > >> >> >> On 31/10/2018 10:52, Thomas Mortagne wrote: >>> On Wed, Oct 31, 2018 at 10:28 AM Vincent Massol >> wrote: > On 31 Oct 2018, at 10:15, Simon Urli wrote: > > Hi, > > On 31/10/2018 09:06, Vincent Massol wrote: >> Hi devs, >> We currently have >> https://dev.xwiki.org/xwiki/bin/view/Community/DatabaseSupportStrategy >> However, it doesn’t say explicitly which versions we officially >> support: >> * For HSQLDB it says 2.3.3 which is wrong since the latest version is >> 2.4.1 >> * For MySQL it says 5.x but doesn’t specify which specific version(s) >> * Same for other DBs >> We cannot really support every versions since supporting means >> testing too. >> So what I propose: >> Question 1: definition >> * We say we support the latest stable version of the databases for a >> given version cycle >> ** For MySQL, it’s the latest of the 5.x cycle, which is 5.7.24 as of >> today (see https://hub.docker.com/_/mysql/) >> ** For PostgreSQL, it’s the latest of the 9.x cycle, which is 9.6.10 >> as of today (see https://hub.docker.com/_/postgres/) >> ** For Oracle, it’s the latest of the 11.x cycle, which is 11.2.0.4.0 >> as of today (see >> https://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html >> ) > > +1 > >> Question 2: review what we support >> * For MySQL I think we could also start supporting MySQL 8.x (ie the >> latest version of that cycle). We have an issue open for it currently: >> https://jira.xwiki.org/browse/XWIKI-15215 >> * For PostgreSQL we could also start supporting versions 11.x (ie the >> latest version of that cycle) >> * For Oracle, we could also start supporting versions 12.x (ie the >> latest version of that cycle) > > +0 I don't really know how much effort it involves to ensure the >> support of the latest version of each database and to fix the bugs >> accordingly. > >> Question 3: decide if we drop some support >> * Is there any cycle that we should support for? Right now I think >> that MySQL 5.x is still heavily used, same for postgreSQL 9.x I guess. >> Don’t know for Oracle. >> * Any idea? > > What about the cycles that are bundled in major LTS distributions? You mean the versions from apt-get for ex (when using the default >> repos)? Indeed the idea could to follow one of them. Any suggestion for which >> one to follow and where the info is? >>> >>> Since we provide Debian package one good reference to know which >>> version of MySQL to support IMO would be >>> >>> >> https://packages.debian.org/search?keywords=mysql-server=names=1 >>> >>> So it would be good to support 5.5 and 5.7 >> >> Maybe it worth it to also look on Ubuntu packages for the LTS, as they >> don't follow the same cycle: >> https://packages.ubuntu.com/search?keywords=mysql-server >> >> Apparently for now version are the same than for Debian. >>> >>> Here is the one for postgresql (since we also have a pgsql based Debian >> package) >>> >>> >> https://packages.debian.org/search?keywords=postgresql=names=1 >> >> >> https://packages.ubuntu.com/search?suite=default=all=any=postgresql=names >> >> So here I see 9.3, 9.5, 10.5 >> >>> >>> So 9.4, 9.6 and 11 >>> Thanks -Vinent > > Simon > >> So WDYT about the 3 questions? >> Thanks >> -Vincent > > -- > Simon Urli > Software Engineer at XWiki SAS > simon.u...@xwiki.com > More about us at http://www.xwiki.com >>> >>> >> >> -- >> Simon Urli >> Software Engineer at XWiki SAS >> simon.u...@xwiki.com >> More about us at http://www.xwiki.com >>
Re: [xwiki-devs] [Proposal] Update database support strategy
IMO we should just write we support: * HyperSQL 2.x Latest * MySQL 5.x Latest * PostgreSQL 9.x Latest * Oracle 11.x Latest not sure what help would do to have the explicit 2.4.1, 5.7.24, 9.6.10, 11.2.0.4.0 versions. Also I'm sure we won't keep up with the versions, so they won't mean latest. When we do the tests we should always fix and test on the latest one. And this 'latest' behavior is consistent with what we do for Browsers, with the exception that we are a bit more descriptive by giving the DB cycle. Thanks, Caty On Wed, Oct 31, 2018 at 12:11 PM Simon Urli wrote: > > > On 31/10/2018 10:52, Thomas Mortagne wrote: > > On Wed, Oct 31, 2018 at 10:28 AM Vincent Massol > wrote: > >> > >> > >> > >>> On 31 Oct 2018, at 10:15, Simon Urli wrote: > >>> > >>> Hi, > >>> > >>> On 31/10/2018 09:06, Vincent Massol wrote: > Hi devs, > We currently have > https://dev.xwiki.org/xwiki/bin/view/Community/DatabaseSupportStrategy > However, it doesn’t say explicitly which versions we officially > support: > * For HSQLDB it says 2.3.3 which is wrong since the latest version is > 2.4.1 > * For MySQL it says 5.x but doesn’t specify which specific version(s) > * Same for other DBs > We cannot really support every versions since supporting means > testing too. > So what I propose: > Question 1: definition > * We say we support the latest stable version of the databases for a > given version cycle > ** For MySQL, it’s the latest of the 5.x cycle, which is 5.7.24 as of > today (see https://hub.docker.com/_/mysql/) > ** For PostgreSQL, it’s the latest of the 9.x cycle, which is 9.6.10 > as of today (see https://hub.docker.com/_/postgres/) > ** For Oracle, it’s the latest of the 11.x cycle, which is 11.2.0.4.0 > as of today (see > https://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html > ) > >>> > >>> +1 > >>> > Question 2: review what we support > * For MySQL I think we could also start supporting MySQL 8.x (ie the > latest version of that cycle). We have an issue open for it currently: > https://jira.xwiki.org/browse/XWIKI-15215 > * For PostgreSQL we could also start supporting versions 11.x (ie the > latest version of that cycle) > * For Oracle, we could also start supporting versions 12.x (ie the > latest version of that cycle) > >>> > >>> +0 I don't really know how much effort it involves to ensure the > support of the latest version of each database and to fix the bugs > accordingly. > >>> > Question 3: decide if we drop some support > * Is there any cycle that we should support for? Right now I think > that MySQL 5.x is still heavily used, same for postgreSQL 9.x I guess. > Don’t know for Oracle. > * Any idea? > >>> > >>> What about the cycles that are bundled in major LTS distributions? > >> > >> You mean the versions from apt-get for ex (when using the default > repos)? > >> > >> Indeed the idea could to follow one of them. Any suggestion for which > one to follow and where the info is? > > > > Since we provide Debian package one good reference to know which > > version of MySQL to support IMO would be > > > > > https://packages.debian.org/search?keywords=mysql-server=names=1 > > > > So it would be good to support 5.5 and 5.7 > > Maybe it worth it to also look on Ubuntu packages for the LTS, as they > don't follow the same cycle: > https://packages.ubuntu.com/search?keywords=mysql-server > > Apparently for now version are the same than for Debian. > > > > Here is the one for postgresql (since we also have a pgsql based Debian > package) > > > > > https://packages.debian.org/search?keywords=postgresql=names=1 > > > https://packages.ubuntu.com/search?suite=default=all=any=postgresql=names > > So here I see 9.3, 9.5, 10.5 > > > > > So 9.4, 9.6 and 11 > > > >> > >> Thanks > >> -Vinent > >> > >>> > >>> Simon > >>> > So WDYT about the 3 questions? > Thanks > -Vincent > >>> > >>> -- > >>> Simon Urli > >>> Software Engineer at XWiki SAS > >>> simon.u...@xwiki.com > >>> More about us at http://www.xwiki.com > >> > > > > > > -- > Simon Urli > Software Engineer at XWiki SAS > simon.u...@xwiki.com > More about us at http://www.xwiki.com >
Re: [xwiki-devs] [Proposal] Update database support strategy
On 31/10/2018 10:52, Thomas Mortagne wrote: On Wed, Oct 31, 2018 at 10:28 AM Vincent Massol wrote: On 31 Oct 2018, at 10:15, Simon Urli wrote: Hi, On 31/10/2018 09:06, Vincent Massol wrote: Hi devs, We currently have https://dev.xwiki.org/xwiki/bin/view/Community/DatabaseSupportStrategy However, it doesn’t say explicitly which versions we officially support: * For HSQLDB it says 2.3.3 which is wrong since the latest version is 2.4.1 * For MySQL it says 5.x but doesn’t specify which specific version(s) * Same for other DBs We cannot really support every versions since supporting means testing too. So what I propose: Question 1: definition * We say we support the latest stable version of the databases for a given version cycle ** For MySQL, it’s the latest of the 5.x cycle, which is 5.7.24 as of today (see https://hub.docker.com/_/mysql/) ** For PostgreSQL, it’s the latest of the 9.x cycle, which is 9.6.10 as of today (see https://hub.docker.com/_/postgres/) ** For Oracle, it’s the latest of the 11.x cycle, which is 11.2.0.4.0 as of today (see https://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html) +1 Question 2: review what we support * For MySQL I think we could also start supporting MySQL 8.x (ie the latest version of that cycle). We have an issue open for it currently: https://jira.xwiki.org/browse/XWIKI-15215 * For PostgreSQL we could also start supporting versions 11.x (ie the latest version of that cycle) * For Oracle, we could also start supporting versions 12.x (ie the latest version of that cycle) +0 I don't really know how much effort it involves to ensure the support of the latest version of each database and to fix the bugs accordingly. Question 3: decide if we drop some support * Is there any cycle that we should support for? Right now I think that MySQL 5.x is still heavily used, same for postgreSQL 9.x I guess. Don’t know for Oracle. * Any idea? What about the cycles that are bundled in major LTS distributions? You mean the versions from apt-get for ex (when using the default repos)? Indeed the idea could to follow one of them. Any suggestion for which one to follow and where the info is? Since we provide Debian package one good reference to know which version of MySQL to support IMO would be https://packages.debian.org/search?keywords=mysql-server=names=1 So it would be good to support 5.5 and 5.7 Maybe it worth it to also look on Ubuntu packages for the LTS, as they don't follow the same cycle: https://packages.ubuntu.com/search?keywords=mysql-server Apparently for now version are the same than for Debian. Here is the one for postgresql (since we also have a pgsql based Debian package) https://packages.debian.org/search?keywords=postgresql=names=1 https://packages.ubuntu.com/search?suite=default=all=any=postgresql=names So here I see 9.3, 9.5, 10.5 So 9.4, 9.6 and 11 Thanks -Vinent Simon So WDYT about the 3 questions? Thanks -Vincent -- Simon Urli Software Engineer at XWiki SAS simon.u...@xwiki.com More about us at http://www.xwiki.com -- Simon Urli Software Engineer at XWiki SAS simon.u...@xwiki.com More about us at http://www.xwiki.com
Re: [xwiki-devs] [Proposal] Update database support strategy
On Wed, Oct 31, 2018 at 10:28 AM Vincent Massol wrote: > > > > > On 31 Oct 2018, at 10:15, Simon Urli wrote: > > > > Hi, > > > > On 31/10/2018 09:06, Vincent Massol wrote: > >> Hi devs, > >> We currently have > >> https://dev.xwiki.org/xwiki/bin/view/Community/DatabaseSupportStrategy > >> However, it doesn’t say explicitly which versions we officially support: > >> * For HSQLDB it says 2.3.3 which is wrong since the latest version is 2.4.1 > >> * For MySQL it says 5.x but doesn’t specify which specific version(s) > >> * Same for other DBs > >> We cannot really support every versions since supporting means testing too. > >> So what I propose: > >> Question 1: definition > >> * We say we support the latest stable version of the databases for a given > >> version cycle > >> ** For MySQL, it’s the latest of the 5.x cycle, which is 5.7.24 as of > >> today (see https://hub.docker.com/_/mysql/) > >> ** For PostgreSQL, it’s the latest of the 9.x cycle, which is 9.6.10 as > >> of today (see https://hub.docker.com/_/postgres/) > >> ** For Oracle, it’s the latest of the 11.x cycle, which is 11.2.0.4.0 as > >> of today (see > >> https://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html) > > > > +1 > > > >> Question 2: review what we support > >> * For MySQL I think we could also start supporting MySQL 8.x (ie the > >> latest version of that cycle). We have an issue open for it currently: > >> https://jira.xwiki.org/browse/XWIKI-15215 > >> * For PostgreSQL we could also start supporting versions 11.x (ie the > >> latest version of that cycle) > >> * For Oracle, we could also start supporting versions 12.x (ie the latest > >> version of that cycle) > > > > +0 I don't really know how much effort it involves to ensure the support of > > the latest version of each database and to fix the bugs accordingly. > > > >> Question 3: decide if we drop some support > >> * Is there any cycle that we should support for? Right now I think that > >> MySQL 5.x is still heavily used, same for postgreSQL 9.x I guess. Don’t > >> know for Oracle. > >> * Any idea? > > > > What about the cycles that are bundled in major LTS distributions? > > You mean the versions from apt-get for ex (when using the default repos)? > > Indeed the idea could to follow one of them. Any suggestion for which one to > follow and where the info is? Since we provide Debian package one good reference to know which version of MySQL to support IMO would be https://packages.debian.org/search?keywords=mysql-server=names=1 So it would be good to support 5.5 and 5.7 Here is the one for postgresql (since we also have a pgsql based Debian package) https://packages.debian.org/search?keywords=postgresql=names=1 So 9.4, 9.6 and 11 > > Thanks > -Vinent > > > > > Simon > > > >> So WDYT about the 3 questions? > >> Thanks > >> -Vincent > > > > -- > > Simon Urli > > Software Engineer at XWiki SAS > > simon.u...@xwiki.com > > More about us at http://www.xwiki.com > -- Thomas Mortagne
Re: [xwiki-devs] [Proposal] Update database support strategy
> On 31 Oct 2018, at 10:28, Vincent Massol wrote: > > > >> On 31 Oct 2018, at 10:15, Simon Urli wrote: >> >> Hi, >> >> On 31/10/2018 09:06, Vincent Massol wrote: >>> Hi devs, >>> We currently have >>> https://dev.xwiki.org/xwiki/bin/view/Community/DatabaseSupportStrategy >>> However, it doesn’t say explicitly which versions we officially support: >>> * For HSQLDB it says 2.3.3 which is wrong since the latest version is 2.4.1 >>> * For MySQL it says 5.x but doesn’t specify which specific version(s) >>> * Same for other DBs >>> We cannot really support every versions since supporting means testing too. >>> So what I propose: >>> Question 1: definition >>> * We say we support the latest stable version of the databases for a given >>> version cycle >>> ** For MySQL, it’s the latest of the 5.x cycle, which is 5.7.24 as of today >>> (see https://hub.docker.com/_/mysql/) >>> ** For PostgreSQL, it’s the latest of the 9.x cycle, which is 9.6.10 as of >>> today (see https://hub.docker.com/_/postgres/) >>> ** For Oracle, it’s the latest of the 11.x cycle, which is 11.2.0.4.0 as of >>> today (see >>> https://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html) >> >> +1 >> >>> Question 2: review what we support >>> * For MySQL I think we could also start supporting MySQL 8.x (ie the latest >>> version of that cycle). We have an issue open for it currently: >>> https://jira.xwiki.org/browse/XWIKI-15215 >>> * For PostgreSQL we could also start supporting versions 11.x (ie the >>> latest version of that cycle) >>> * For Oracle, we could also start supporting versions 12.x (ie the latest >>> version of that cycle) >> >> +0 I don't really know how much effort it involves to ensure the support of >> the latest version of each database and to fix the bugs accordingly. >> >>> Question 3: decide if we drop some support >>> * Is there any cycle that we should support for? Right now I think that >>> MySQL 5.x is still heavily used, same for postgreSQL 9.x I guess. Don’t >>> know for Oracle. >>> * Any idea? >> >> What about the cycles that are bundled in major LTS distributions? > > You mean the versions from apt-get for ex (when using the default repos)? > > Indeed the idea could to follow one of them. Any suggestion for which one to > follow and where the info is? Actually what I did is try to follow the “latest” tag on the official docker images. Since we need some docker images anyway. Sometime the “latest” tag is really recent though. For postgresql for ex, it’s 11.0, see https://hub.docker.com/_/postgres/ So I suggest as a general rule to follow the dockerhub official image “latest” tags. WDYT? Thanks -Vincent > > Thanks > -Vinent > >> >> Simon >> >>> So WDYT about the 3 questions? >>> Thanks >>> -Vincent >> >> -- >> Simon Urli >> Software Engineer at XWiki SAS >> simon.u...@xwiki.com >> More about us at http://www.xwiki.com
Re: [xwiki-devs] [Proposal] Update database support strategy
> On 31 Oct 2018, at 10:28, Adel Atallah wrote: > > Hello, > > On Wed, Oct 31, 2018 at 9:07 AM Vincent Massol wrote: >> >> Hi devs, >> >> We currently have >> https://dev.xwiki.org/xwiki/bin/view/Community/DatabaseSupportStrategy >> >> However, it doesn’t say explicitly which versions we officially support: >> * For HSQLDB it says 2.3.3 which is wrong since the latest version is 2.4.1 >> * For MySQL it says 5.x but doesn’t specify which specific version(s) >> * Same for other DBs >> >> We cannot really support every versions since supporting means testing too. >> >> So what I propose: >> >> Question 1: definition >> >> * We say we support the latest stable version of the databases for a given >> version cycle >> ** For MySQL, it’s the latest of the 5.x cycle, which is 5.7.24 as of today >> (see https://hub.docker.com/_/mysql/) >> ** For PostgreSQL, it’s the latest of the 9.x cycle, which is 9.6.10 as of >> today (see https://hub.docker.com/_/postgres/) >> ** For Oracle, it’s the latest of the 11.x cycle, which is 11.2.0.4.0 as of >> today (see >> https://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html) >> > > Does it also mean that we will have to add a step in the release > process to update these versions? Two things here: * We already update the versions from time to time but yes we should monitor this better. Note sure it should be in the release process though. * On the testing side, if we use the “latest” tag then we’ll use automatically the latest version from the official docker image. > >> Question 2: review what we support >> >> * For MySQL I think we could also start supporting MySQL 8.x (ie the latest >> version of that cycle). We have an issue open for it currently: >> https://jira.xwiki.org/browse/XWIKI-15215 >> * For PostgreSQL we could also start supporting versions 11.x (ie the latest >> version of that cycle) >> * For Oracle, we could also start supporting versions 12.x (ie the latest >> version of that cycle) >> > > This will probably require more effort to support these versions but > it might be a good reason to update Hibernate :). Note: The new automatic testing will make it simpler to support them (at least to test them). > >> Question 3: decide if we drop some support >> >> * Is there any cycle that we should support for? Right now I think that >> MySQL 5.x is still heavily used, same for postgreSQL 9.x I guess. Don’t know >> for Oracle. >> * Any idea? >> > > I don't think we should drop support for older database versions as it > would require some users to upgrade their database. Sure but that’s normal ;) We can’t support all past versions so we need to draw the line somewhere… It doesn’t mean it’s not going to work with old versions, it means we don’t test for them and don’t do extra effort to make XWiki work on them (if contributors submit PRs we will apply them). Thanks -Vincent > >> So WDYT about the 3 questions? >> >> Thanks >> -Vincent > > Thanks, > Adel
Re: [xwiki-devs] [Proposal] Update database support strategy
Hello, On Wed, Oct 31, 2018 at 9:07 AM Vincent Massol wrote: > > Hi devs, > > We currently have > https://dev.xwiki.org/xwiki/bin/view/Community/DatabaseSupportStrategy > > However, it doesn’t say explicitly which versions we officially support: > * For HSQLDB it says 2.3.3 which is wrong since the latest version is 2.4.1 > * For MySQL it says 5.x but doesn’t specify which specific version(s) > * Same for other DBs > > We cannot really support every versions since supporting means testing too. > > So what I propose: > > Question 1: definition > > * We say we support the latest stable version of the databases for a given > version cycle > ** For MySQL, it’s the latest of the 5.x cycle, which is 5.7.24 as of today > (see https://hub.docker.com/_/mysql/) > ** For PostgreSQL, it’s the latest of the 9.x cycle, which is 9.6.10 as of > today (see https://hub.docker.com/_/postgres/) > ** For Oracle, it’s the latest of the 11.x cycle, which is 11.2.0.4.0 as of > today (see > https://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html) > Does it also mean that we will have to add a step in the release process to update these versions? > Question 2: review what we support > > * For MySQL I think we could also start supporting MySQL 8.x (ie the latest > version of that cycle). We have an issue open for it currently: > https://jira.xwiki.org/browse/XWIKI-15215 > * For PostgreSQL we could also start supporting versions 11.x (ie the latest > version of that cycle) > * For Oracle, we could also start supporting versions 12.x (ie the latest > version of that cycle) > This will probably require more effort to support these versions but it might be a good reason to update Hibernate :). > Question 3: decide if we drop some support > > * Is there any cycle that we should support for? Right now I think that MySQL > 5.x is still heavily used, same for postgreSQL 9.x I guess. Don’t know for > Oracle. > * Any idea? > I don't think we should drop support for older database versions as it would require some users to upgrade their database. > So WDYT about the 3 questions? > > Thanks > -Vincent Thanks, Adel
Re: [xwiki-devs] [Proposal] Update database support strategy
> On 31 Oct 2018, at 10:15, Simon Urli wrote: > > Hi, > > On 31/10/2018 09:06, Vincent Massol wrote: >> Hi devs, >> We currently have >> https://dev.xwiki.org/xwiki/bin/view/Community/DatabaseSupportStrategy >> However, it doesn’t say explicitly which versions we officially support: >> * For HSQLDB it says 2.3.3 which is wrong since the latest version is 2.4.1 >> * For MySQL it says 5.x but doesn’t specify which specific version(s) >> * Same for other DBs >> We cannot really support every versions since supporting means testing too. >> So what I propose: >> Question 1: definition >> * We say we support the latest stable version of the databases for a given >> version cycle >> ** For MySQL, it’s the latest of the 5.x cycle, which is 5.7.24 as of today >> (see https://hub.docker.com/_/mysql/) >> ** For PostgreSQL, it’s the latest of the 9.x cycle, which is 9.6.10 as of >> today (see https://hub.docker.com/_/postgres/) >> ** For Oracle, it’s the latest of the 11.x cycle, which is 11.2.0.4.0 as of >> today (see >> https://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html) > > +1 > >> Question 2: review what we support >> * For MySQL I think we could also start supporting MySQL 8.x (ie the latest >> version of that cycle). We have an issue open for it currently: >> https://jira.xwiki.org/browse/XWIKI-15215 >> * For PostgreSQL we could also start supporting versions 11.x (ie the latest >> version of that cycle) >> * For Oracle, we could also start supporting versions 12.x (ie the latest >> version of that cycle) > > +0 I don't really know how much effort it involves to ensure the support of > the latest version of each database and to fix the bugs accordingly. > >> Question 3: decide if we drop some support >> * Is there any cycle that we should support for? Right now I think that >> MySQL 5.x is still heavily used, same for postgreSQL 9.x I guess. Don’t know >> for Oracle. >> * Any idea? > > What about the cycles that are bundled in major LTS distributions? You mean the versions from apt-get for ex (when using the default repos)? Indeed the idea could to follow one of them. Any suggestion for which one to follow and where the info is? Thanks -Vinent > > Simon > >> So WDYT about the 3 questions? >> Thanks >> -Vincent > > -- > Simon Urli > Software Engineer at XWiki SAS > simon.u...@xwiki.com > More about us at http://www.xwiki.com
Re: [xwiki-devs] [Proposal] Update database support strategy
Hi, On 31/10/2018 09:06, Vincent Massol wrote: Hi devs, We currently have https://dev.xwiki.org/xwiki/bin/view/Community/DatabaseSupportStrategy However, it doesn’t say explicitly which versions we officially support: * For HSQLDB it says 2.3.3 which is wrong since the latest version is 2.4.1 * For MySQL it says 5.x but doesn’t specify which specific version(s) * Same for other DBs We cannot really support every versions since supporting means testing too. So what I propose: Question 1: definition * We say we support the latest stable version of the databases for a given version cycle ** For MySQL, it’s the latest of the 5.x cycle, which is 5.7.24 as of today (see https://hub.docker.com/_/mysql/) ** For PostgreSQL, it’s the latest of the 9.x cycle, which is 9.6.10 as of today (see https://hub.docker.com/_/postgres/) ** For Oracle, it’s the latest of the 11.x cycle, which is 11.2.0.4.0 as of today (see https://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html) +1 Question 2: review what we support * For MySQL I think we could also start supporting MySQL 8.x (ie the latest version of that cycle). We have an issue open for it currently: https://jira.xwiki.org/browse/XWIKI-15215 * For PostgreSQL we could also start supporting versions 11.x (ie the latest version of that cycle) * For Oracle, we could also start supporting versions 12.x (ie the latest version of that cycle) +0 I don't really know how much effort it involves to ensure the support of the latest version of each database and to fix the bugs accordingly. Question 3: decide if we drop some support * Is there any cycle that we should support for? Right now I think that MySQL 5.x is still heavily used, same for postgreSQL 9.x I guess. Don’t know for Oracle. * Any idea? What about the cycles that are bundled in major LTS distributions? Simon So WDYT about the 3 questions? Thanks -Vincent -- Simon Urli Software Engineer at XWiki SAS simon.u...@xwiki.com More about us at http://www.xwiki.com
