Hi devs,
Our jabber chat experience has now been going on for several months. I
think it's working quite well and I'd like to propose that we make it
official. I'd also like to keep the IRC bridge since it's also working
quite well.
Once we agree about making the jabber chat official I'll document it
on http://dev.xwiki.org/
Here's my +1
Thanks
-Vincent
Hi Devs,
Since we have decided to move officeimporter wysiwyg integration from
wysiwyg toolbar to wysiwyg menu bar, it's important we decide the structure
of the new "Import" menu:
I can see two methods for structuring the Import menu:
[1]
Import
|-> Office Document
|-> Office Paste
[2]
Import->Office
|->Document (Upload)
|->Clipboard (Paste)
I'm not sure about the exact wording to be used (please help on that) and
I'm currently +1 for proposal [1].
WDYT?
Thanks.
Hi devs,
I propose we add the following method to DocumentModelBridge:
/**
* @return a string identifying the current version of this document
*/
String getVersion();
I need it for the WYSIWYG sync plug-in service. I'm refactoring the code
to use components and I want to drop the dependency on xwiki-core.
Getting the document version is the last thing that stops me.
Here my +1.
Thanks,
Marius
On 10/15/2009 12:05 PM, asiri (SVN) wrote:
> Author: asiri
> Date: 2009-10-15 12:05:22 +0200 (Thu, 15 Oct 2009)
> New Revision: 24508
>
> Modified:
> Log:
> [misc] Activated checkstyle for officeimporter code base.
>
> - Fixed 71/72 Checkstyles reported.
>
> - The remaining checkstyle issue (class fan-out ~ 22, max allowed is 20) is bit hard to fix without refactoring the officeimporter API a little.
You can fix it by removing the readStream utility method, which can be
replaced with something from commons-ioutils. This will remove all
usages of ByteArrayOutputStream and IOException and add one class from
ioutils.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
Hi,
We have 2 critical fixes in XE 2.0.3:
- The stats are broken (since 2.0.1)
- The object editor doesn't allow to add objects for which the user
doesn't have edit rights on the document holding the class definition
(since 2.0)
+ some other fixes:
http://jira.xwiki.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=10010…
Thus I'm proposing to release ASAP, which is next Tuesday (since
Thomas is on holidays till next Monday - That's unless someone else
want to do the release of course).
Here's my +1
Thanks
-Vincent
Hi,
We were supposed to release 2.1M1 yesterday according to our initial
roadmap. However we've all been working on 2.0.x releases and as a
consequence there isn't much in 2.1M1 that isn't in 2.0.x releases.
Namely there are 11 issues and most of them are not very important
(see http://tinycoke.com/_6rvPPs9pSbA/picture_1.png) and don't warrant
a release IMO.
I'm proposing to remove 2.1M2 and extend 2.1M1 till 16 Nov (ie the
date when 2.1M2 was supposed to be released). The other dates are kept
unchanged, see
http://enterprise.xwiki.org/xwiki/bin/view/Main/Roadmap
Here's my +1
Thanks
-Vincent