20 Oct
2011
20 Oct
'11
10:07 a.m.
Hi Eugen,
Thanks for taking the time to share this.
I definitely agree with issues 1 and 2. They're really important. I also agree about
issue 3 although it's slightly less important than the other 2.
Listing tested DBs in the Release notes is a good idea. Actually what I would have liked
to do is to go further than this and have various agents on jenkins running on various DBs
(HSQLDB, PostgreSQL, MySQL and Oracle) to ensure that all our tests run fine on these DBs
all the time. I've been wanting to have this for a long time now but it's not
happened yet :(
Of course patches (even better: github pull requests!) are more welcome to help us fixing
these issues.
Thanks
-Vincent
On Oct 20, 2011, at 9:21 AM, Eugen Colesnicov wrote:
Hello developers!
I seen your thread about XE 3.3 Roadmap + Finishing the 3.x cycle. In this
post also described jira-requests, which you planned to resolve in a near
future.
All is great, the general strategy and each step are right, but also exists
some other important issues (I think that its are important) and I want to
put your attention on its. If is it possible, can you analyze possibility to
include these issues in your nearly plans?
1. XE-1032 - XWiki 3.2 totally cannot work on Oracle (upgrade & fresh
install failed). I think, it is important issue, because supporting of
Oracle are declared - but in realty XE 3.2 is not supporting Oracle.
To the future, maybe is good proposal, same as you wrote in a 3.2 release
notes - which browsers are tested & supporting - also will write witch DB
are tested & supporting. I can test new releases on Oracle.
2. XE-324 - allow special (russian and asian) characters in attachment names
- very old issue, but I think is important, because without it - you cannot
declare that XWiki have normal multi-language support. All modern
web-platforms & applications now have this possibility (wikis, web-mails,
social applications, etc.) only XWiki is lagging...
3. XWIKI-2870 - Ability to select query language in Database List property.
This is more for developers, and also very old issue. I think it is
important, because if you did something modern (in this case - XWQL) - need
to support this in all "parts" of platform... If you didn't do this - your
great work for modern features - looks like as "garbage" - I cannot use XWQL
in Database List property - as a result - I am not using XWQL at all,
because I don't want to write queries 2 times.
If is it possible, can you analyze possibility to include these issues in
your nearly plans?
PS. Maybe another users know some more important unresolved issues? I think,
user opinions will be interesting for developers!
Thanks beforehand!
Eugen Colesnicov