Hi devs,
Here are some notes I took while releasing XWiki 4.3 on how to improve the release process:
* We need to automate the generation of the CLIRR report. This is what takes the longest when releasing (not overall time but manual time required). IMO this can be done relatively easily by creating a patch for the CLIRR maven plugin itself to:
** Add support for wildcards in the new <difference> syntax
** Ensure that their report generation takes into account the <justification> element
** Possibly add a text report generation that we'll be able to copy paste in our RN
* Remove PURL generation for Tweets
** Tweets are ephemeral so no need to have permanent URLs
** Tweet clients already do URL shortening
(It's complex to use the PURL UI too)
* Don't create RN summary for OW2, email and even blog post. This will win some more time. Instead just link to the RN page which contains a summary and all details. For example for the email it could be:
"
The XWiki development team is proud to announce the availability of XWiki Enterprise <version>.
You can download it here: http://www.xwiki.org/xwiki/bin/view/Main/Download
Make sure to review the release notes:
http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWiki<short version>
Thanks
-The XWiki dev team
"
* Put maven.xwiki.org:~/xwiki-release-scripts under Git and do a git reset before the ow2 step to be sure to have clean scripts
WDYT?
Thanks
-Vincent
Hi devs,
I've written some conventions for translation messages at
http://dev.xwiki.org/xwiki/bin/view/Community/L10N+Conventions
Please provide feedback, since we terribly lack some proper rules here,
and there aren't two applications that use the same conventions. Now
that we have support for modular translation documents, it's a good time
to clean up translations and move things out of ApplicationProperties
into each application.
--
Sergiu Dumitriu
http://purl.org/net/sergiu
The XWiki development team is proud to announce the availability of XWiki Enterprise 4.3.
This release brings several improvements in Workspaces, Extension Manager, Distribution Wizard, the REST API, new field pickers (Date, User and Groups), improved translation registration and new experimental Solr search.
You can download it here: http://www.xwiki.org/xwiki/bin/view/Main/Download
Make sure to review the release notes:
http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWiki43
Thanks
-The XWiki dev team
Hello,
Annoying problem :
- One wiki on production with 1 space with an eventlistener working on it,
sending email as soon as a page is created in the space.
- In dev, the same wiki : we add a new space with an other eventlistener,
sending email as soon as a page is created in the space (in summary because
the mail, the conditions of sending it are differents, etc...)
Everything is OK !
So we've decided to get it on production. On pre-production the second
listener doesn't send emails. In logs we have this error :
com.xpn.xwiki.XWikiException: Error number 2 in 0: The wiki xxx does not
exist
xxx is the name of our wiki and declared as an alias of the wiki. We are in
version 2.6.2.
I don't see what we are missing and so we cannot get it on productio.
Thanks for your help.
Patrice
--
View this message in context: http://xwiki.475771.n2.nabble.com/com-xpn-xwiki-XWikiException-Error-number…
Sent from the XWiki- Dev mailing list archive at Nabble.com.
Hi!
RalucaM and myself have been working on/reviewing French translations
for XWiki 4.3 and we've posted a report illustrating the issues we
found here http://www.xwiki.org/xwiki/bin/view/TestReports/TranslationsReport43
Sorin will be reviewing each entry to see whether translations or keys
are missing and will probably ping you on IRC for help :)
It would be very useful however if you could look at the reported
issues and make some of the needed fixes, especially if you're a
native French speaker.
Edi has already helped us with the Workspaces App keys. Thanks a lot!
Please reply to the current thread and specify the fixes you've made,
or edit the document directly and write [fixed] in front of the entry
you handled. We won't be able to include the translations in the 4.3
final release, but it would be wonderful if we could have a 4.3.1, or
even include them in 4.4.
Here is the link again:
http://www.xwiki.org/xwiki/bin/view/TestReports/TranslationsReport43
Translation wiki: http://l10n.xwiki.org/xwiki/bin/view/L10N/
Thanks,
Silvia
Hi devs,
I'd like to deprecate Util.getResourceAsStream():
public static InputStream getResourceAsStream(String resource)
{
File file = new File(resource);
try {
if (file.exists()) {
return new FileInputStream(file);
}
} catch (Exception e) {
// Probably running under -security, which prevents calling File.exists()
LOGGER.debug("Failed load resource [" + resource + "] using a file path");
}
try {
Environment environment = Utils.getComponent(Environment.class);
InputStream res = environment.getResourceAsStream(resource);
if (res != null) {
return res;
}
} catch (Exception e) {
LOGGER.debug("Failed to load resource [" + resource + "] using the application context");
}
return Thread.currentThread().getContextClassLoader().getResourceAsStream(resource);
}
Instead I'd like to propose to use the new Environment.getResourceAsStream(). However I'd also like to modify the ServletEnvironment.getResourceAsStream() implementation so that it also looks in the classloader if not found in the resources directory (defaulting to the current thread context class loader for the classloader to use since this is set in a servlet container).
Thanks
-Vincent
Hello,
Is it possible to use Sencha JS as a front-end resource to build in-wiki applications ?
Nweike Onwuyali
.............................
excuse my typos & brevity. Sent from a mobile device
Hello all, I am new to xwiki
Can I use xwiki to build a social networking site like elgg
Nweike Onwuyali
.............................
excuse my typos & brevity. Sent from a mobile device
Hi devs,
I'd like to rename the "Release Plans" app (http://dev.xwiki.org/xwiki/bin/view/ReleasePlans/WebHome) into "Releases" (i.e. remove the "plan" part) and then commit in platform as an application.
Here's my +1
Thanks
-Vincent
PS: This action goes in the direction of creating a list of useful applications/extensions for a Project Development Flavor (see other mail).