Hi devs,
I'd like to rename the office-preview module to office-viewer since it
better matches the current provided functionality: view office
attachments (either inside a wiki page or standalone) without
downloading them.
Let me know if you are against this rename.
Thanks,
Marius
As planned i just pre-released XE/XEM 2.4.3 on maven and subversion.
I'm now waiting for as many testers as possible to try and validate
that it does not contains important regression.
You can download XE/XEM on:
- XE jetty+hsqldb:
http://maven.xwiki.org/releases/com/xpn/xwiki/products/xwiki-enterprise-jet…
- XE war: http://maven.xwiki.org/releases/com/xpn/xwiki/products/xwiki-enterprise-web…
- XE xar: http://maven.xwiki.org/releases/com/xpn/xwiki/products/xwiki-enterprise-wik…
- XEM war: http://maven.xwiki.org/releases/com/xpn/xwiki/products/xwiki-enterprise-man…
- XEM xar: http://maven.xwiki.org/releases/com/xpn/xwiki/products/xwiki-enterprise-man…
If nothing is found i will finish the release tomorrow morning (GMT).
Thanks
On Mon, Sep 27, 2010 at 09:34, Thomas Mortagne
<thomas.mortagne(a)xwiki.com> wrote:
> 5.5 for 2.4.3 and 1.5 for 2.4.2.1
>
> 2.4.3 it is. Starting now.
>
> On Fri, Sep 24, 2010 at 15:42, Thomas Mortagne
> <thomas.mortagne(a)xwiki.com> wrote:
>> Hi devs,
>>
>> 2.4 is a blessed branch, now the issue is that there is no parent
>> field anymore because XE has been release with the wrong version of
>> panels applications.
>>
>> This seems pretty blocker to me and deserve to be fixed ASAP, i can
>> see the following solutions:
>>
>> 1. complete new release of XE/XEM 2.4.3
>> 2. release of XE/XEM 2.4.2.1 with the existing core/web 2.4.2
>> 3. re-release XE 2.3.2
>>
>> 1: +1, probably the cleanest but if I don't have to release core i
>> would be more than glad...
>> 2: +0.5, probably the clean solutions that needs the less work IMO.
>> After all technically XE and core have different versions
>> 3: -1, it's already public and downloaded by some users
>>
>> Also whatever the chosen solution before announcing the release i will
>> as much people as possible to validate it.
>>
>> So WDYT ?
>>
>> --
>> Thomas Mortagne
>>
>
>
>
> --
> Thomas Mortagne
>
--
Thomas Mortagne
Hi devs,
I'd like to propose that we always go through Nexus staging from now on for our Main and Bugfix releases. The process would be:
1) Release to a staged repo (with the final version name)
2) Send a testing mail on devs and users lists to allow people to test the release. Note: we don't make the release avail on xwiki.org, just a mail is sent.
3) Wait for 48 hours
4) Promote the staged release to final and finish the release process (xwiki.org update, announcements, etc)
We could start with 2.5.
- Note 1: This means that in our release dates we should allow for 2 days more in order not to be late because of this.
- Note 2: This is not for milestones or RC. Just for final and bugfix releases.
WDYT?
Thanks
-Vincent
Hi devs,
We've been working on improving the editors (content, class, object),
and now I have some pretty important UI changes to commit, but not
everybody seems to agree with them, so I bring up a vote.
The whole improvements can be seen on
http://incubator.myxwiki.org/xwiki/bin/Improvements/ImprovedEdit
Here are the individual voted points:
0 Remove all panels in edit mode
1a Parent and title above the content in wiki/wysiwyg mode
1b The same style in edit mode as in view mode for the parent/title fields
1c AJAX Suggest for the parent field
2a New label for the content textarea ("Content")
2b List of included documents after the Content label
3a Syntax switcher in the top right corner of the content
3b Syntax help in the top right corner of the content
3c Syntax help and switcher only in the wiki editor
4 Better label for the version comment
5a Right float the Minor edit field
5b Put the Minor edit label after the checkbox
6 Move autosave in line with the submit buttons
7 Introduce new AJAX-powered Add Object
i) above the objects
ii) bellow the objects
8 Introduce new AJAX-powered Add Object from this class
i) at the top of the list of existing objects
ii) at the end of the list
9 Move the class switcher in the top right corner
9b Remove the class switcher
10 Introduce new AJAX-powered Add Property
i) at the top of the list of properties
ii) at the end of the list
I vote +1 for all of the above, except 9b (-0), and with options 7i),
8ii), and 10ii)
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
Hi devs,
2.4 is a blessed branch, now the issue is that there is no parent
field anymore because XE has been release with the wrong version of
panels applications.
This seems pretty blocker to me and deserve to be fixed ASAP, i can
see the following solutions:
1. complete new release of XE/XEM 2.4.3
2. release of XE/XEM 2.4.2.1 with the existing core/web 2.4.2
3. re-release XE 2.3.2
1: +1, probably the cleanest but if I don't have to release core i
would be more than glad...
2: +0.5, probably the clean solutions that needs the less work IMO.
After all technically XE and core have different versions
3: -1, it's already public and downloaded by some users
Also whatever the chosen solution before announcing the release i will
as much people as possible to validate it.
So WDYT ?
--
Thomas Mortagne
Hi!
Caleb and I have been chatting this afternoon about a solution to pass
the value of a variable to a query string. Thanks Caleb!
Something like this...
##$species is defined simply by...
#set($species = '%babo%')
##and the query string is constructed by using + to concatenate stubs
including the value of that variable...
#set($query = ", BaseObject as obj, StringProperty as prop where
doc.fullName = obj.name and obj.className='Users.PdrUserClass' and
obj.id=prop.id.id and prop.id.name='Species' and prop.value like '" +
$species + "' order by doc.fullName asc")
This works great with com.xpn.xwiki.objects.StringProperty properties,
but not with com.xpn.xwiki.objects.StringProperty ones.
Please, do you know why and what is required to filter by properties of
that type? Thanks!
Ricardo
--
Ricardo Rodríguez
CTO
eBioTIC.
Life Sciences, Data Modeling and Information Management Systems