23 Mar
2012
23 Mar
'12
11:47 a.m.
Hi devs,
In the same spirit as what we have done for Browsers (see
http://xwiki.markmail.org/thread/pn45a7qaefuplpye ) here's a proposal for Databases
since we don't have a clear strategy ATM.
I propose that by "supporting" we mean:
- issues created for these DBs in jira are not closed as won't fix and we make a best
effort to fix them
- we include these DBs in our tests (be them automated or manual)
- when we create new features or modify existing features we make a best effort to verify
that they work on the supported list of DBs
Proposal:
* HSQLDB: only support the version bundled in the standalone zip
* MySQL: We officially support the last major version, i.e. 5.0+ ATM
* PostgreSQL: We officially support the last major version, i.e. 9.0+ ATM
* Oracle: We officially support the last major version, i.e. 11g ATM
* DB2: We don't officially support it. This means that we don't test against it,
we don't ensure that new feature work on it but if someone raises an issue in jira and
it's easy to fix (or if someone provides a patch) then we fix it.
* Derby: Same as DB2
* Microsoft SQL Server: Same as DB2
* H2: Same as DB2 for the moment (it would change if we decide to replace HSQLDB by H2 one
day)
* Others: Same as DB2
I also propose that in the Release notes for each version of XWiki we mention the list of
DBs we have tested against and that we "support".
Here's my +1
Thanks
-Vincent
23 Mar
23 Mar
11:50 a.m.
Hello,
+1
Thanks,
Silvia
On Fri, Mar 23, 2012 at 12:47 PM, Vincent Massol <vincent(a)massol.net> wrote:
Hi devs,
In the same spirit as what we have done for Browsers (see
http://xwiki.markmail.org/thread/pn45a7qaefuplpye ) here's a proposal for Databases
since we don't have a clear strategy ATM.
I propose that by "supporting" we mean:
- issues created for these DBs in jira are not closed as won't fix and we make a best
effort to fix them
- we include these DBs in our tests (be them automated or manual)
- when we create new features or modify existing features we make a best effort to verify
that they work on the supported list of DBs
Proposal:
* HSQLDB: only support the version bundled in the standalone zip
* MySQL: We officially support the last major version, i.e. 5.0+ ATM
* PostgreSQL: We officially support the last major version, i.e. 9.0+ ATM
* Oracle: We officially support the last major version, i.e. 11g ATM
* DB2: We don't officially support it. This means that we don't test against it,
we don't ensure that new feature work on it but if someone raises an issue in jira and
it's easy to fix (or if someone provides a patch) then we fix it.
* Derby: Same as DB2
* Microsoft SQL Server: Same as DB2
* H2: Same as DB2 for the moment (it would change if we decide to replace HSQLDB by H2
one day)
* Others: Same as DB2
I also propose that in the Release notes for each version of XWiki we mention the list of
DBs we have tested against and that we "support".
Here's my +1
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
12:02 p.m.
Hello,
I am +1 for this also since it's my role in the community to make sure
databases work.
The testing procedure (which I already do) is "executed after the RC1
release of a version and consists in:
* setting up an XWiki instance on a vanilla database to test if the
database is correctly created from scratch and a few basic manual tests
* perform a migration from an older version (ATM using 2.7.2) to the latest
XWiki RC1 version to see if the migration works well. Mostly I check for
console errors and if there are none, I perform a few basic tests like
retrieving attachments that were inside the wiki before the migration, etc
After the vote finishes, I will update our documentation and create a page
about this according to the vote's result.
Regards,
Sorin B.
On Fri, Mar 23, 2012 at 12:47 PM, Vincent Massol <vincent(a)massol.net> wrote:
Hi devs,
In the same spirit as what we have done for Browsers (see
http://xwiki.markmail.org/thread/pn45a7qaefuplpye ) here's a proposal for
Databases since we don't have a clear strategy ATM.
I propose that by "supporting" we mean:
- issues created for these DBs in jira are not closed as won't fix and we
make a best effort to fix them
- we include these DBs in our tests (be them automated or manual)
- when we create new features or modify existing features we make a best
effort to verify that they work on the supported list of DBs
Proposal:
* HSQLDB: only support the version bundled in the standalone zip
* MySQL: We officially support the last major version, i.e. 5.0+ ATM
* PostgreSQL: We officially support the last major version, i.e. 9.0+ ATM
* Oracle: We officially support the last major version, i.e. 11g ATM
* DB2: We don't officially support it. This means that we don't test
against it, we don't ensure that new feature work on it but if someone
raises an issue in jira and it's easy to fix (or if someone provides a
patch) then we fix it.
* Derby: Same as DB2
* Microsoft SQL Server: Same as DB2
* H2: Same as DB2 for the moment (it would change if we decide to replace
HSQLDB by H2 one day)
* Others: Same as DB2
I also propose that in the Release notes for each version of XWiki we
mention the list of DBs we have tested against and that we "support".
Here's my +1
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
3:03 p.m.
+1, of course, it is really good to have this.
On Fri, Mar 23, 2012 at 12:02, Sorin Burjan <sorin.burjan(a)xwiki.com> wrote:
Hello,
I am +1 for this also since it's my role in the community to make sure
databases work.
The testing procedure (which I already do) is "executed after the RC1
release of a version and consists in:
* setting up an XWiki instance on a vanilla database to test if the
database is correctly created from scratch and a few basic manual tests
* perform a migration from an older version (ATM using 2.7.2) to the latest
XWiki RC1 version to see if the migration works well. Mostly I check for
console errors and if there are none, I perform a few basic tests like
retrieving attachments that were inside the wiki before the migration, etc
Maybe for the 4.0 it would be good to start some migration testing before
the RC, since what I have written is really heavy, and I am a little bit
worried on that point. I do not have the resources to do these test myself,
but Ludovic has kindly proposed to conduct them, I suppose that you are the
one who should do the real work ? I will assist has much as I can if there
is any issue.
After the vote finishes, I will update our documentation and create a page
about this according to the vote's result.
Regards,
Sorin B.
On Fri, Mar 23, 2012 at 12:47 PM, Vincent Massol <vincent(a)massol.net>
wrote:
--
Denis Gervalle
SOFTEC sa - CEO
eGuilde sarl - CTO
Hi devs,
In the same spirit as what we have done for Browsers (see
http://xwiki.markmail.org/thread/pn45a7qaefuplpye ) here's a proposal
for
Databases since we don't have a clear
strategy ATM.
I propose that by "supporting" we mean:
- issues created for these DBs in jira are not closed as won't fix and we
make a best effort to fix them
- we include these DBs in our tests (be them automated or manual)
- when we create new features or modify existing features we make a best
effort to verify that they work on the supported list of DBs
Proposal:
* HSQLDB: only support the version bundled in the standalone zip
* MySQL: We officially support the last major version, i.e. 5.0+ ATM
* PostgreSQL: We officially support the last major version, i.e. 9.0+
ATM
* Oracle: We officially support the last major
version, i.e. 11g ATM
* DB2: We don't officially support it. This means that we don't test
against it, we don't ensure that new feature work on it but if someone
raises an issue in jira and it's easy to fix (or if someone provides a
patch) then we fix it.
* Derby: Same as DB2
* Microsoft SQL Server: Same as DB2
* H2: Same as DB2 for the moment (it would change if we decide to replace
HSQLDB by H2 one day)
* Others: Same as DB2
I also propose that in the Release notes for each version of XWiki we
mention the list of DBs we have tested against and that we "support".
Here's my +1
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
29 Mar
29 Mar
2:55 p.m.
Hello Denis, read my comments below
On Fri, Mar 23, 2012 at 4:03 PM, Denis Gervalle <dgl(a)softec.lu> wrote:
replace
--
Denis Gervalle
SOFTEC sa - CEO
eGuilde sarl - CTO
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
+1, of course, it is really good to have this.
On Fri, Mar 23, 2012 at 12:02, Sorin Burjan <sorin.burjan(a)xwiki.com>
wrote:
Maybe for the 4.0 it would be good to start some migration testing before
the RC, since what I have written is really heavy, and I am a little bit
worried on that point. I do not have the resources to do these test myself,
but Ludovic has kindly proposed to conduct them, I suppose that you are the
one who should do the real work ? I will assist has much as I can if there
is any issue.
We can do the testing together after the M2 release, just ping me on IRC
and we'll talk about it. It's good since you know exactly where errors
should occur.
Regards,
Sorin B.
Hello,
I am +1 for this also since it's my role in the community to make sure
databases work.
The testing procedure (which I already do) is "executed after the RC1
release of a version and consists in:
* setting up an XWiki instance on a vanilla database to test if the
database is correctly created from scratch and a few basic manual tests
* perform a migration from an older version (ATM using 2.7.2) to the
latest
XWiki RC1 version to see if the migration works
well. Mostly I check for
console errors and if there are none, I perform a few basic tests like
retrieving attachments that were inside the wiki before the migration,
etc
After the vote finishes, I will update our documentation and create a
page
about this according to the vote's result.
Regards,
Sorin B.
On Fri, Mar 23, 2012 at 12:47 PM, Vincent Massol <vincent(a)massol.net>
wrote:
we
Hi devs,
In the same spirit as what we have done for Browsers (see
http://xwiki.markmail.org/thread/pn45a7qaefuplpye ) here's a proposal
for
> Databases since we don't have a clear strategy ATM.
>
> I propose that by "supporting" we mean:
> - issues created for these DBs in jira are not closed as won't fix and > make a best effort to fix them
> - we include these DBs in our tests (be them automated or manual)
> - when we create new features or modify existing features we make a
best
effort to
verify that they work on the supported list of DBs
Proposal:
* HSQLDB: only support the version bundled in the standalone zip
* MySQL: We officially support the last major version, i.e. 5.0+ ATM
* PostgreSQL: We officially support the last major version, i.e. 9.0+
ATM
> * Oracle: We officially support the last major version, i.e. 11g ATM
> * DB2: We don't officially support it. This means that we don't test
> against it, we don't ensure that new feature work on it but if someone
> raises an issue in jira and it's easy to fix (or if someone provides a
> patch) then we fix it.
> * Derby: Same as DB2
> * Microsoft SQL Server: Same as DB2
> * H2: Same as DB2 for the moment (it would change if we decide to HSQLDB by
H2 one day)
* Others: Same as DB2
I also propose that in the Release notes for each version of XWiki we
mention the list of DBs we have tested against and that we "support".
Here's my +1
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
23 Mar
23 Mar
12:08 p.m.
On Fri, Mar 23, 2012 at 11:47 AM, Vincent Massol <vincent(a)massol.net> wrote:
Hi devs,
In the same spirit as what we have done for Browsers (see
http://xwiki.markmail.org/thread/pn45a7qaefuplpye ) here's a proposal for Databases
since we don't have a clear strategy ATM.
I propose that by "supporting" we mean:
- issues created for these DBs in jira are not closed as won't fix and we make a best
effort to fix them
- we include these DBs in our tests (be them automated or manual)
- when we create new features or modify existing features we make a best effort to verify
that they work on the supported list of DBs
Proposal:
* HSQLDB: only support the version bundled in the standalone zip
* MySQL: We officially support the last major version, i.e. 5.0+ ATM
Do you mean all versions from the last major release cycle ? In which
case it means 5.0+, 5.1+, 5.5+ - or just the last version ? (5.5+).
The way you've written it, it sound like we support just one version,
but I don't think that's what we want.
Otherwise, +1 for the general strategy, it's good to put this on paper.
Jerome
* PostgreSQL: We officially support the last major
version, i.e. 9.0+ ATM
* Oracle: We officially support the last major version, i.e. 11g ATM
* DB2: We don't officially support it. This means that we don't test against it,
we don't ensure that new feature work on it but if someone raises an issue in jira and
it's easy to fix (or if someone provides a patch) then we fix it.
* Derby: Same as DB2
* Microsoft SQL Server: Same as DB2
* H2: Same as DB2 for the moment (it would change if we decide to replace HSQLDB by H2
one day)
* Others: Same as DB2
I also propose that in the Release notes for each version of XWiki we mention the list of
DBs we have tested against and that we "support".
Here's my +1
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Jérôme Velociter
Winesquare
http://www.winesquare.net/
12:20 p.m.
On Mar 23, 2012, at 12:08 PM, Jerome Velociter wrote:
On Fri, Mar 23, 2012 at 11:47 AM, Vincent Massol
<vincent(a)massol.net> wrote:
Yes I meant 5.x actually
For PostgreSQL it's 9.x
For Oracle it's 11.x
Thanks
-Vincent
Hi devs,
In the same spirit as what we have done for Browsers (see
http://xwiki.markmail.org/thread/pn45a7qaefuplpye ) here's a proposal for Databases
since we don't have a clear strategy ATM.
I propose that by "supporting" we mean:
- issues created for these DBs in jira are not closed as won't fix and we make a best
effort to fix them
- we include these DBs in our tests (be them automated or manual)
- when we create new features or modify existing features we make a best effort to verify
that they work on the supported list of DBs
Proposal:
* HSQLDB: only support the version bundled in the standalone zip
* MySQL: We officially support the last major version, i.e. 5.0+ ATM
Do you mean all versions from the last major release cycle ? In which
case it means 5.0+, 5.1+, 5.5+ - or just the last version ? (5.5+). The way you've written it, it sound like we
support just one version,
but I don't think that's what we want.
Otherwise, +1 for the general strategy, it's good to put this on paper.
Jerome
* PostgreSQL: We officially support the last
major version, i.e. 9.0+ ATM
* Oracle: We officially support the last major version, i.e. 11g ATM
* DB2: We don't officially support it. This means that we don't test against it,
we don't ensure that new feature work on it but if someone raises an issue in jira and
it's easy to fix (or if someone provides a patch) then we fix it.
* Derby: Same as DB2
* Microsoft SQL Server: Same as DB2
* H2: Same as DB2 for the moment (it would change if we decide to replace HSQLDB by H2
one day)
* Others: Same as DB2
I also propose that in the Release notes for each version of XWiki we mention the list of
DBs we have tested against and that we "support".
Here's my +1
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
--
Jérôme Velociter
Winesquare
http://www.winesquare.net/
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
12:23 p.m.
On Mar 23, 2012, at 12:20 PM, Vincent Massol wrote:
On Mar 23, 2012, at 12:08 PM, Jerome Velociter wrote:
That said it's not going to be easy to test all minor versions so we'll probably
only test some versions; hoping that they haven't made too many changes amongst minor
versions...
When I wrote the email I hesitated a bit by saying that we officially support only the
last released version (5.5.x for mysql for ex) but it's a bit limitating. OTOH saying
that we support 5.x is just not honest since it's not true. We're not going to
test all minor versions at all releases (which is what "supported" means, see
the definition above)...
Thanks
-Vincent
On Fri, Mar 23, 2012 at 11:47 AM, Vincent Massol
<vincent(a)massol.net> wrote:
Yes I meant 5.x actually
For PostgreSQL it's 9.x
For Oracle it's 11.x Hi devs,
In the same spirit as what we have done for Browsers (see
http://xwiki.markmail.org/thread/pn45a7qaefuplpye ) here's a proposal for Databases
since we don't have a clear strategy ATM.
I propose that by "supporting" we mean:
- issues created for these DBs in jira are not closed as won't fix and we make a best
effort to fix them
- we include these DBs in our tests (be them automated or manual)
- when we create new features or modify existing features we make a best effort to verify
that they work on the supported list of DBs
Proposal:
* HSQLDB: only support the version bundled in the standalone zip
* MySQL: We officially support the last major version, i.e. 5.0+ ATM
Do you mean all versions from the last major release cycle ? In which
case it means 5.0+, 5.1+, 5.5+ - or just the last version ? (5.5+). Thanks
-Vincent
> The way you've written it, it sound like we support just one version,
> but I don't think that's what we want.
>
> Otherwise, +1 for the general strategy, it's good to put this on paper.
>
> Jerome
>
>> * PostgreSQL: We officially support the last major version, i.e. 9.0+ ATM
>> * Oracle: We officially support the last major version, i.e. 11g ATM
>> * DB2: We don't officially support it. This means that we don't test
against it, we don't ensure that new feature work on it but if someone raises an issue
in jira and it's easy to fix (or if someone provides a patch) then we fix it.
>> * Derby: Same as DB2
>> * Microsoft SQL Server: Same as DB2
>> * H2: Same as DB2 for the moment (it would change if we decide to replace HSQLDB
by H2 one day)
>> * Others: Same as DB2
>>
>> I also propose that in the Release notes for each version of XWiki we mention the
list of DBs we have tested against and that we "support".
>>
>> Here's my +1
>>
>> Thanks
>> -Vincent
12:35 p.m.
I'm not sure for the version of the DB but +1 to write it down
somewhere whatever we choose.
On Fri, Mar 23, 2012 at 12:23 PM, Vincent Massol <vincent(a)massol.net> wrote:
On Mar 23, 2012, at 12:20 PM, Vincent Massol wrote:
I think saying 5.x is OK. I think it mean we test on the minimal 5.x
version and hope for retro-compatibility.
On Mar 23, 2012, at 12:08 PM, Jerome Velociter wrote:
That said it's not going to be+ easy to test all minor versions so we'll probably
only test some versions; hoping that they haven't made too many changes amongst minor
versions...
When I wrote the email I hesitated a bit by saying that we officially support only the
last released version (5.5.x for mysql for ex) but it's a bit limitating. OTOH saying
that we support 5.x is just not honest since it's not true. We're not going to
test all minor versions at all releases (which is what "supported" means, see
the definition above)... On Fri, Mar 23, 2012 at 11:47 AM, Vincent Massol
<vincent(a)massol.net> wrote:
Yes I meant 5.x actually
For PostgreSQL it's 9.x
For Oracle it's 11.x Hi devs,
In the same spirit as what we have done for Browsers (see
http://xwiki.markmail.org/thread/pn45a7qaefuplpye ) here's a proposal for Databases
since we don't have a clear strategy ATM.
I propose that by "supporting" we mean:
- issues created for these DBs in jira are not closed as won't fix and we make a best
effort to fix them
- we include these DBs in our tests (be them automated or manual)
- when we create new features or modify existing features we make a best effort to verify
that they work on the supported list of DBs
Proposal:
* HSQLDB: only support the version bundled in the standalone zip
* MySQL: We officially support the last major version, i.e. 5.0+ ATM
Do you mean all versions from the last major release cycle ? In which
case it means 5.0+, 5.1+, 5.5+ - or just the last version ? (5.5+).
Thanks
-Vincent
--
Thomas Mortagne
Thanks
-Vincent
> The way you've written it, it sound like we support just one version,
> but I don't think that's what we want.
>
> Otherwise, +1 for the general strategy, it's good to put this on paper.
>
> Jerome
>
>> * PostgreSQL: We officially support the last major version, i.e. 9.0+ ATM
>> * Oracle: We officially support the last major version, i.e. 11g ATM
>> * DB2: We don't officially support it. This means that we don't test
against it, we don't ensure that new feature work on it but if someone raises an issue
in jira and it's easy to fix (or if someone provides a patch) then we fix it.
>> * Derby: Same as DB2
>> * Microsoft SQL Server: Same as DB2
>> * H2: Same as DB2 for the moment (it would change if we decide to replace HSQLDB
by H2 one day)
>> * Others: Same as DB2
>>
>> I also propose that in the Release notes for each version of XWiki we mention the
list of DBs we have tested against and that we "support".
>>
>> Here's my +1
>>
>> Thanks
>> -Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs 
25 Mar
25 Mar
8:56 p.m.
+1
Thanks,
Marius
On Fri, Mar 23, 2012 at 12:47 PM, Vincent Massol <vincent(a)massol.net> wrote:
Hi devs,
In the same spirit as what we have done for Browsers (see
http://xwiki.markmail.org/thread/pn45a7qaefuplpye ) here's a proposal for Databases
since we don't have a clear strategy ATM.
I propose that by "supporting" we mean:
- issues created for these DBs in jira are not closed as won't fix and we make a best
effort to fix them
- we include these DBs in our tests (be them automated or manual)
- when we create new features or modify existing features we make a best effort to verify
that they work on the supported list of DBs
Proposal:
* HSQLDB: only support the version bundled in the standalone zip
* MySQL: We officially support the last major version, i.e. 5.0+ ATM
* PostgreSQL: We officially support the last major version, i.e. 9.0+ ATM
* Oracle: We officially support the last major version, i.e. 11g ATM
* DB2: We don't officially support it. This means that we don't test against it,
we don't ensure that new feature work on it but if someone raises an issue in jira and
it's easy to fix (or if someone provides a patch) then we fix it.
* Derby: Same as DB2
* Microsoft SQL Server: Same as DB2
* H2: Same as DB2 for the moment (it would change if we decide to replace HSQLDB by H2
one day)
* Others: Same as DB2
I also propose that in the Release notes for each version of XWiki we mention the list of
DBs we have tested against and that we "support".
Here's my +1
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
26 Mar
26 Mar
12:14 a.m.
On 03/23/2012 06:47 AM, Vincent Massol wrote:
Hi devs,
In the same spirit as what we have done for Browsers (see
http://xwiki.markmail.org/thread/pn45a7qaefuplpye ) here's a proposal for Databases
since we don't have a clear strategy ATM.
I propose that by "supporting" we mean:
- issues created for these DBs in jira are not closed as won't fix and we make a best
effort to fix them
- we include these DBs in our tests (be them automated or manual)
- when we create new features or modify existing features we make a best effort to verify
that they work on the supported list of DBs
Proposal:
* HSQLDB: only support the version bundled in the standalone zip
We should try to keep up to date with each release.
* MySQL: We officially support the last major version,
i.e. 5.0+ ATM
* PostgreSQL: We officially support the last major version, i.e. 9.0+ ATM
* Oracle: We officially support the last major version, i.e. 11g ATM
* DB2: We don't officially support it. This means that we don't test against it,
we don't ensure that new feature work on it but if someone raises an issue in jira and
it's easy to fix (or if someone provides a patch) then we fix it.
* Derby: Same as DB2
* Microsoft SQL Server: Same as DB2
* H2: Same as DB2 for the moment (it would change if we decide to replace HSQLDB by H2
one day)
* Others: Same as DB2
I also propose that in the Release notes for each version of XWiki we mention the list of
DBs we have tested against and that we "support".
Here's my +1
+1.
An important aspect is multiwiki. Currently only MySQL is fully tested
in virtual mode, while HSQLDB and PostgreSQL aren't supported at all,
and Oracle works but is not thoroughly tested. We should try to make
sure virtual mode works on Oracle, and try to provide support in the
near future for the other two supported databases.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
11:21 a.m.
Hi,
On Mon, Mar 26, 2012 at 00:14, Sergiu Dumitriu <sergiu(a)xwiki.com> wrote:
On 03/23/2012 06:47 AM, Vincent Massol wrote:
I know of a large installation (60+ wikis) running XEM 2.7.1 that works
well. I think XEM should be supported on PostgreSQL.
Guillaume
Hi devs,
In the same spirit as what we have done for Browsers (see
http://xwiki.markmail.org/**thread/pn45a7qaefuplpye<http://xwiki.markmai…)
here's a proposal for Databases since we don't have a clear strategy ATM.
I propose that by "supporting" we mean:
- issues created for these DBs in jira are not closed as won't fix and we
make a best effort to fix them
- we include these DBs in our tests (be them automated or manual)
- when we create new features or modify existing features we make a best
effort to verify that they work on the supported list of DBs
Proposal:
* HSQLDB: only support the version bundled in the standalone zip
We should try to keep up to date with each release.
* MySQL: We officially support the last major version, i.e. 5.0+ ATM
* PostgreSQL: We officially support the last
major version, i.e. 9.0+ ATM
* Oracle: We officially support the last major version, i.e. 11g ATM
* DB2: We don't officially support it. This means that we don't test
against it, we don't ensure that new feature work on it but if someone
raises an issue in jira and it's easy to fix (or if someone provides a
patch) then we fix it.
* Derby: Same as DB2
* Microsoft SQL Server: Same as DB2
* H2: Same as DB2 for the moment (it would change if we decide to replace
HSQLDB by H2 one day)
* Others: Same as DB2
I also propose that in the Release notes for each version of XWiki we
mention the list of DBs we have tested against and that we "support".
Here's my +1
+1.
An important aspect is multiwiki. Currently only MySQL is fully tested in
virtual mode, while HSQLDB and PostgreSQL aren't supported at all, and
Oracle works but is not thoroughly tested. We should try to make sure
virtual mode works on Oracle, and try to provide support in the near future
for the other two supported databases. --
Sergiu Dumitriu
http://purl.org/net/sergiu/
______________________________**_________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/**mailman/listinfo/devs<http://lists.xwiki.org/ma…
3 Apr
3 Apr
1:05 p.m.
New subject: [xwiki-devs] [Proposal] Supported Databases Strategy (SUMMARY)
This wasn't strictly a vote but everyone agreed with the proposal so it''s now
our official database support strategy! :)
Sorin is going to make it available at
http://dev.xwiki.org/xwiki/bin/view/Community/DatabaseSupportStrategy
Thanks everyone
-Vincent
On Mar 23, 2012, at 11:47 AM, Vincent Massol wrote:
Hi devs,
In the same spirit as what we have done for Browsers (see
http://xwiki.markmail.org/thread/pn45a7qaefuplpye ) here's a proposal for Databases
since we don't have a clear strategy ATM.
I propose that by "supporting" we mean:
- issues created for these DBs in jira are not closed as won't fix and we make a best
effort to fix them
- we include these DBs in our tests (be them automated or manual)
- when we create new features or modify existing features we make a best effort to verify
that they work on the supported list of DBs
Proposal:
* HSQLDB: only support the version bundled in the standalone zip
* MySQL: We officially support the last major version, i.e. 5.0+ ATM
* PostgreSQL: We officially support the last major version, i.e. 9.0+ ATM
* Oracle: We officially support the last major version, i.e. 11g ATM
* DB2: We don't officially support it. This means that we don't test against it,
we don't ensure that new feature work on it but if someone raises an issue in jira and
it's easy to fix (or if someone provides a patch) then we fix it.
* Derby: Same as DB2
* Microsoft SQL Server: Same as DB2
* H2: Same as DB2 for the moment (it would change if we decide to replace HSQLDB by H2
one day)
* Others: Same as DB2
I also propose that in the Release notes for each version of XWiki we mention the list of
DBs we have tested against and that we "support".
Here's my +1
Thanks
-Vincent
3:45 p.m.
New subject: [xwiki-devs] [Proposal] Supported Databases Strategy (SUMMARY)
We have now created
http://dev.xwiki.org/xwiki/bin/view/Community/SupportStrategy which will
hold our support strategies for Browsers and Databases, but more things can
be added if we agree upon.
Regards,
Sorin B.
On Tue, Apr 3, 2012 at 2:05 PM, Vincent Massol <vincent(a)massol.net> wrote:
This wasn't strictly a vote but everyone agreed
with the proposal so it''s
now our official database support strategy! :)
Sorin is going to make it available at
http://dev.xwiki.org/xwiki/bin/view/Community/DatabaseSupportStrategy
Thanks everyone
-Vincent
On Mar 23, 2012, at 11:47 AM, Vincent Massol wrote:
Hi devs,
In the same spirit as what we have done for Browsers (see
http://xwiki.markmail.org/thread/pn45a7qaefuplpye ) here's a proposal for
Databases since we don't have a clear strategy ATM.
I propose that by "supporting" we mean:
- issues created for these DBs in jira are not closed as won't fix and
we make
a best effort to fix them
- we include these DBs in our tests (be them
automated or manual)
- when we create new features or modify existing features we make a best
effort to
verify that they work on the supported list of DBs
Proposal:
* HSQLDB: only support the version bundled in the standalone zip
* MySQL: We officially support the last major version, i.e. 5.0+ ATM
* PostgreSQL: We officially support the last major version, i.e. 9.0+
ATM
* Oracle: We officially support the last major
version, i.e. 11g ATM
* DB2: We don't officially support it. This means that we don't test
against it, we don't ensure that new feature work on it but if someone
raises an issue in jira and it's easy to fix (or if someone provides a
patch) then we fix it.
* Derby: Same as DB2
* Microsoft SQL Server: Same as DB2
* H2: Same as DB2 for the moment (it would change if we decide to
replace HSQLDB
by H2 one day)
* Others: Same as DB2
I also propose that in the Release notes for each version of XWiki we
mention the
list of DBs we have tested against and that we "support".
Here's my +1
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
4 Apr
4 Apr
9:32 a.m.
New subject: [xwiki-devs] [Proposal] Supported Databases Strategy (SUMMARY)
Since we don't officially support it, shouldn't we remove derby
profile and database project from our Maven build ?
On Tue, Apr 3, 2012 at 3:45 PM, Sorin Burjan <sorin.burjan(a)xwiki.com> wrote:
We have now created
http://dev.xwiki.org/xwiki/bin/view/Community/SupportStrategy which will
hold our support strategies for Browsers and Databases, but more things can
be added if we agree upon.
Regards,
Sorin B.
On Tue, Apr 3, 2012 at 2:05 PM, Vincent Massol <vincent(a)massol.net> wrote:
--
Thomas Mortagne
This wasn't strictly a vote but everyone
agreed with the proposal so it''s
now our official database support strategy! :)
Sorin is going to make it available at
http://dev.xwiki.org/xwiki/bin/view/Community/DatabaseSupportStrategy
Thanks everyone
-Vincent
On Mar 23, 2012, at 11:47 AM, Vincent Massol wrote:
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs Hi devs,
In the same spirit as what we have done for Browsers (see
http://xwiki.markmail.org/thread/pn45a7qaefuplpye ) here's a proposal for
Databases since we don't have a clear strategy ATM.
I propose that by "supporting" we mean:
- issues created for these DBs in jira are not closed as won't fix and
we make
a best effort to fix them
- we include these DBs in our tests (be them
automated or manual)
- when we create new features or modify existing features we make a best
effort to
verify that they work on the supported list of DBs
Proposal:
* HSQLDB: only support the version bundled in the standalone zip
* MySQL: We officially support the last major version, i.e. 5.0+ ATM
* PostgreSQL: We officially support the last major version, i.e. 9.0+
ATM
* Oracle: We officially support the last major
version, i.e. 11g ATM
* DB2: We don't officially support it. This means that we don't test
against it, we don't ensure that new feature work on it but if someone
raises an issue in jira and it's easy to fix (or if someone provides a
patch) then we fix it.
* Derby: Same as DB2
* Microsoft SQL Server: Same as DB2
* H2: Same as DB2 for the moment (it would change if we decide to
replace HSQLDB
by H2 one day)
* Others: Same as DB2
I also propose that in the Release notes for each version of XWiki we
mention the
list of DBs we have tested against and that we "support".
Here's my +1
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
9:33 a.m.
New subject: [xwiki-devs] [Proposal] Supported Databases Strategy (SUMMARY)
On Wed, Apr 4, 2012 at 9:32 AM, Thomas Mortagne
<thomas.mortagne(a)xwiki.com> wrote:
Since we don't officially support it,
shouldn't we remove derby
profile and database project from our Maven build ?
And add one for Oracle.
On Tue, Apr 3, 2012 at 3:45 PM, Sorin Burjan <sorin.burjan(a)xwiki.com> wrote:
--
Thomas Mortagne
We have now created
http://dev.xwiki.org/xwiki/bin/view/Community/SupportStrategy which will
hold our support strategies for Browsers and Databases, but more things can
be added if we agree upon.
Regards,
Sorin B.
On Tue, Apr 3, 2012 at 2:05 PM, Vincent Massol <vincent(a)massol.net> wrote:
--
Thomas Mortagne This wasn't strictly a vote but everyone
agreed with the proposal so it''s
now our official database support strategy! :)
Sorin is going to make it available at
http://dev.xwiki.org/xwiki/bin/view/Community/DatabaseSupportStrategy
Thanks everyone
-Vincent
On Mar 23, 2012, at 11:47 AM, Vincent Massol wrote:
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs Hi devs,
In the same spirit as what we have done for Browsers (see
http://xwiki.markmail.org/thread/pn45a7qaefuplpye ) here's a proposal for
Databases since we don't have a clear strategy ATM.
I propose that by "supporting" we mean:
- issues created for these DBs in jira are not closed as won't fix and
we make
a best effort to fix them
- we include these DBs in our tests (be them
automated or manual)
- when we create new features or modify existing features we make a best
effort to
verify that they work on the supported list of DBs
Proposal:
* HSQLDB: only support the version bundled in the standalone zip
* MySQL: We officially support the last major version, i.e. 5.0+ ATM
* PostgreSQL: We officially support the last major version, i.e. 9.0+
ATM
* Oracle: We officially support the last major
version, i.e. 11g ATM
* DB2: We don't officially support it. This means that we don't test
against it, we don't ensure that new feature work on it but if someone
raises an issue in jira and it's easy to fix (or if someone provides a
patch) then we fix it.
* Derby: Same as DB2
* Microsoft SQL Server: Same as DB2
* H2: Same as DB2 for the moment (it would change if we decide to
replace HSQLDB
by H2 one day)
* Others: Same as DB2
I also propose that in the Release notes for each version of XWiki we
mention the
list of DBs we have tested against and that we "support".
Here's my +1
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
11:58 a.m.
New subject: [xwiki-devs] [Proposal] Supported Databases Strategy (SUMMARY)
On Apr 4, 2012, at 9:33 AM, Thomas Mortagne wrote:
On Wed, Apr 4, 2012 at 9:32 AM, Thomas Mortagne
<thomas.mortagne(a)xwiki.com> wrote:
AFAIK they're not doing anything at this point in time so we might as well remove all
the profiles we don't use FTM (it will change when we use VMs to run our functional
tests in some future…).
Thanks
-Vincent
Since we don't officially support it,
shouldn't we remove derby
profile and database project from our Maven build ?
And add one for Oracle. > On Tue, Apr 3, 2012 at 3:45 PM, Sorin Burjan
<sorin.burjan(a)xwiki.com> wrote:
>> We have now created
>> http://dev.xwiki.org/xwiki/bin/view/Community/SupportStrategy which will
>> hold our support strategies for Browsers and Databases, but more things can
>> be added if we agree upon.
>>
>> Regards,
>> Sorin B.
>>
>> On Tue, Apr 3, 2012 at 2:05 PM, Vincent Massol <vincent(a)massol.net> wrote:
>>
>>> This wasn't strictly a vote but everyone agreed with the proposal so
it''s
>>> now our official database support strategy! :)
>>>
>>> Sorin is going to make it available at
>>> http://dev.xwiki.org/xwiki/bin/view/Community/DatabaseSupportStrategy
>>>
>>> Thanks everyone
>>> -Vincent
>>>
>>> On Mar 23, 2012, at 11:47 AM, Vincent Massol wrote:
>>>
>>>> Hi devs,
>>>>
>>>> In the same spirit as what we have done for Browsers (see
>>> http://xwiki.markmail.org/thread/pn45a7qaefuplpye ) here's a proposal
for
>>> Databases since we don't have a clear strategy ATM.
>>>>
>>>> I propose that by "supporting" we mean:
>>>> - issues created for these DBs in jira are not closed as won't fix
and
>>> we make a best effort to fix them
>>>> - we include these DBs in our tests (be them automated or manual)
>>>> - when we create new features or modify existing features we make a best
>>> effort to verify that they work on the supported list of DBs
>>>>
>>>> Proposal:
>>>>
>>>> * HSQLDB: only support the version bundled in the standalone zip
>>>> * MySQL: We officially support the last major version, i.e. 5.0+ ATM
>>>> * PostgreSQL: We officially support the last major version, i.e. 9.0+
>>> ATM
>>>> * Oracle: We officially support the last major version, i.e. 11g ATM
>>>> * DB2: We don't officially support it. This means that we don't
test
>>> against it, we don't ensure that new feature work on it but if someone
>>> raises an issue in jira and it's easy to fix (or if someone provides a
>>> patch) then we fix it.
>>>> * Derby: Same as DB2
>>>> * Microsoft SQL Server: Same as DB2
>>>> * H2: Same as DB2 for the moment (it would change if we decide to
>>> replace HSQLDB by H2 one day)
>>>> * Others: Same as DB2
>>>>
>>>> I also propose that in the Release notes for each version of XWiki we
>>> mention the list of DBs we have tested against and that we
"support".
>>>>
>>>> Here's my +1
>>>>
>>>> Thanks
>>>> -Vincent
4645
days inactive
4657
days old
16 comments
9 participants
participants (9)
-
Denis Gervalle -
Guillaume Lerouge -
Jerome Velociter -
Marius Dumitru Florea -
Sergiu Dumitriu -
Silvia Rusu -
Sorin Burjan -
Thomas Mortagne -
Vincent Massol