xwiki-devs

xwiki-devs@xwiki.org

9400 discussions

by Vincent Massol

Hi everyone, We need to organize JIRA for our 1.0 final release. As the 1.0 release manager I'm listing in this email my view on what 1.0 should container and the roadmap. Please let me know all your comments. Definition ========== * 1.0 means that the application can be used in production and does something useful. This is already the case as XWiki is used in lots of places in production. As a consequence 1.0 should be as close as possible to the current version in trunk but bugs fixed. * All usability improvements or new features should thus be moved to 1.1 or after. Timeline ======== * 1.0 beta 1 is going to be delivered today (19th of Dec 2006) * I'd like to allow for 2 weeks releases from now on till 1.0 final. Thus: - 1.0 beta 2 for the 6th of January 2007 (allowing for 1 week during Christmas) - 1.0 rc1 for the 20th of January 2007 and promoted to 1.0 final if stable after 2 weeks of users using it, i.e. for the 3rd of Feb. 2007 - If rc1 is not stable enough, then we do a rc2 for the 3rd of February and promote it to 1.0 final if stable after 2 weeks of users using it (i.e. 17th of Feb) What this means is that for 1.0 final we should add JIRA issues *only* for doing work till the 20th of January. Evyerthing else must be moved to 1.1 and beyond. As a technical aside, this means that we will create a 1.0 branch on the 6th of January 2007. Let me know if the dates are ok with you. Contents ======== * Known Bug fixes. * News bug fixes discovered when user start using 1.0 beta 1 * A few select features. I'm proposing: - Page Rename. Lots of wikis have this feature and I think that's the major feature we're lacking right now. - Email notification when pages are modified (watch feature). Only if we already have most of the code. Otherwise move to 1.1. * Documentation, documentation and documentation. This means finishing moving old.xwiki.org to xwiki.org and documenting new features like the new {image} macro, etc * More simple and quick wins macros so that there are less HTML in the pages. For example: {column} macro to display content on several columns, {panel} macro to display panels in pages. * Start packaging applications (blog, search, photos, etc) in XAR files. This will allow to releases new versions of these even if the core is not released again. Note: The number of bugs that we'll fix will only depend on the manpower that we have. In other words, we'll fix as many as possible but still release with outstanding bugs. Of course critical bugs needs to be addressed first. Let me know if you know of other tasks that you think must absolutely be done before 1.0 final. Next steps ========== Could everyone who's going to work on 1.0 final please review his tasks in JIRA and move them according to the strategy above, and assign them to himself/herself? When you do so please remember that you're committing to working on the issue in the timeframe allocated for the different releases. It's very important that everyone respects this so that we don't deviate from our release dates. Please all target to have a sorted out JIRA till 1.0 final by Friday. Thanks -Vincent ___________________________________________________________________________ Yahoo! Mail r�invente le mail ! D�couvrez le nouveau Yahoo! Mail et son interface r�volutionnaire. http://fr.mail.yahoo.com

18 years, 1 month

xwiki build.501 Build Successful

by ludovic＠xwiki.org

View results here -> http://build.xpertnet.biz/cc/buildresults/xwiki?log=log20061222033924Lbuild…

18 years, 1 month

[JIRA] Changed renderer configuration - Now using Wiki rendering

by Vincent Massol

Hi, I've configured JIRA on jira.xwiki.org to display the description field and the comments using the wiki rendering feature. See http://www.atlassian.com/software/jira/docs/latest/renderers_overview.html for details. In short, here are a few interesting macros: {code} : display code {noformat}: displays unformatted text (for example http://jira.xwiki.org/jira/browse/XWIKI-595) Let me know if you have some issue with this. Thanks -Vincent

18 years, 1 month

[xwiki-dev] 1.0 Roadmap

by Phung Nam

This is ok for me, I'll finish all bug for B2 , but I don't know whether the task Xwiki-292 for incomming email plugin is neccessary for this release version (I'm afraid it's delay) > Hi everyone, > > We need to organize JIRA for our 1.0 final release. As the 1.0 release > manager I'm listing in this email my view on what 1.0 should container > and the roadmap. Please let me know all your comments. > > Definition > ========== > > * 1.0 means that the application can be used in production and does > something useful. This is already the case as XWiki is used in lots of > places in production. As a consequence 1.0 should be as close as > possible to the current version in trunk but bugs fixed. > * All usability improvements or new features should thus be moved to > 1.1 or after. > > Timeline > ======== > > * 1.0 beta 1 is going to be delivered today (19th of Dec 2006) > * I'd like to allow for 2 weeks releases from now on till 1.0 final. > Thus: > - 1.0 beta 2 for the 6th of January 2007 (allowing for 1 week during > Christmas) > - 1.0 rc1 for the 20th of January 2007 and promoted to 1.0 final if > stable after 2 weeks of users using it, i.e. for the 3rd of Feb. 2007 > - If rc1 is not stable enough, then we do a rc2 for the 3rd of > February and promote it to 1.0 final if stable after 2 weeks of users > using it (i.e. > 17th of Feb) > > What this means is that for 1.0 final we should add JIRA issues *only* > for doing work till the 20th of January. Evyerthing else must be moved > to 1.1 and beyond. > > As a technical aside, this means that we will create a 1.0 branch on > the 6th of January 2007. > > Let me know if the dates are ok with you. > > Contents > ======== > > * Known Bug fixes. > * News bug fixes discovered when user start using 1.0 beta 1 > * A few select features. I'm proposing: > - Page Rename. Lots of wikis have this feature and I think that's the > major feature we're lacking right now. > - Email notification when pages are modified (watch feature). Only if > we already have most of the code. Otherwise move to 1.1. > * Documentation, documentation and documentation. This means finishing > moving old.xwiki.org to xwiki.org and documenting new features like the > new {image} macro, etc > * More simple and quick wins macros so that there are less HTML in the > pages. For example: {column} macro to display content on several > columns, {panel} macro to display panels in pages. > * Start packaging applications (blog, search, photos, etc) in XAR > files. > This will allow to releases new versions of these even if the core is > not released again. > > Note: The number of bugs that we'll fix will only depend on the > manpower that we have. In other words, we'll fix as many as possible > but still release with outstanding bugs. Of course critical bugs needs > to be addressed first. > > Let me know if you know of other tasks that you think must absolutely > be done before 1.0 final. > > Next steps > ========== > > Could everyone who's going to work on 1.0 final please review his tasks > in JIRA and move them according to the strategy above, and assign them > to himself/herself? When you do so please remember that you're > committing to working on the issue in the timeframe allocated for the > different releases. > It's very important that everyone respects this so that we don't > deviate from our release dates. > > Please all target to have a sorted out JIRA till 1.0 final by Friday. > > Thanks > -Vincent

18 years, 1 month

Big fix submission for problem with {rss} macro

by Trevor Cox

I've posted a fix for bug #XWIKI-283, and I hope someone can include it in the next release. When trying to show an RSS or RSS2 feed in a wiki page using the {rss} macro, you will see text like: "SyndContentImpl.value= ... {blog text} ... SyndContentImpl.type=text/plain" Here's the fix to java/com/xpn/xwiki/render/macro/rss/RSSMacro.java. It applies to xwiki 0.9.743 through subversion June 20, 2006. and to rome 0.6 through 0.8. 185c184 < .append(NEWLINE).append(entry.getDescription()) --- > .append(NEWLINE).append(entry.getDescription().getValue()) 218c217 < .append(NEWLINE).append(entry.getDescription()) --- > .append(NEWLINE).append(entry.getDescription().getValue()) Explanation: The following code appends the result of com.sun.syndication.feed.synd.SyndEntry.getDescription(). That would be fine if getDescription returned a String, but in fact it returns a feed.synd.SyndContent object. buf.append(NEWLINE).append("<div class='rssitemdescription'>") .append(NEWLINE).append(entry.getDescription()) .append(NEWLINE).append("</div>"); My test cases were: RSS: {rss:feed=http://gigazad.blogspot.com/rss.xml|count=4|full=true} RSS2: {rss:feed=http://www.mikegiesbrecht.com/Blog.php?feed_type=rss2|count=1|full=true} More details below. -- Trevor Cox skahasoftware.com Vancouver, Canada Ludovic Dubost wrote: > > Looks like I missed this one !! There is probably a bug with to little > encoding of what we get from the feeds. > You should report an issue in http://jira.xwiki.org > > Ludovic > > Trevor Cox a écrit : > >> Has anyone looked in to RSS2 feeds and the {rss} macro? As far as I >> can figure out, RSS2 is a new version of RSS. My {rss} macro works >> fine with RSS feeds that are not labelled RSS2 (although Google seems >> to block access somehow). >> >> I tried upgrading to the latest version of rome.jar, 0.7, but that >> didn't help. A Google search showed that many XWiki users are having >> the same problem I am. >> >> When I use {rss... |full=true} I see the following text. I've put in >> bold the text that I should be seeing. The rest is coming from the >> ROME code (not directly from the RSS source). >> >> SyndContentImpl.value=*Be sure to check out my November Newsletter >> for important tips for Buyers! Click on the Newsletter tab on my >> Home Page and read about 6 questions a Buyer should ask before making >> an offer. Read More <http://mikegiesbrecht.com/ViewBlog/14/>* >> SyndContentImpl.type=text/plain SyndContentImpl.interface=interface >> com.sun.syndication.feed.synd.SyndContent >> >> >> -Trevor Cox >> http://skahasoftware.com >> ------------------------------------------------------------------------ >

18 years, 1 month

xwiki build.500 Build Successful

by ludovic＠xwiki.org

View results here -> http://build.xpertnet.biz/cc/buildresults/xwiki?log=log20061221082022Lbuild…

18 years, 1 month

[ANN] XWiki 1.0 Beta 1 Released

by Vincent Massol

Hi everyone, The XWiki development team is proud to announce the release of XWiki 1.0 Beta 1. This is the first in a series of quick releases that will lead to XWiki 1.0 Final. Here are the main changes from the 0.9.x versions: * New Skin * Lots of usability improvements * Importer/Exporter to import and export sets of wiki pages * XWiki can now work with an empty database * Pages can be tagged (not documented yet) + basic UI for viewing the tag cloud * New WYSIWYG editor (using Tiny MCE v2) * New Rights editor * New web site and updated documentation * Improved programming APIs * Notion of Panels (porlet-like areas which can be added in menus) + Drag and drop Panel Wizard to easily customize the displayed Panels (experimental, works only in Firefox) * Standalone installer to get up to speed quickly (includes Jetty and HSQL already set up) * Attachments versioning * Section edits (ability to edit only sections of a page) See http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotes for more details on how to migrate your existing installations. Please note that we're sending this email to the dev list first so that we can work together on improving the installation and migration information on xwiki.org. Let us know about any issue you have. Thanks -XWiki Dev Team

18 years, 1 month

xwiki build.499 Build Successful

by ludovic＠xwiki.org

View results here -> http://build.xpertnet.biz/cc/buildresults/xwiki?log=log20061220122213Lbuild…

18 years, 2 months

XWiki build from source

by Gerwin Brunner

Hi, I'm trying to get XWiki build from source, but I guess I'm doing something wrong here. I checked out the following dir: svn://svn.forge.objectweb.org/svnroot/xwiki/trunk And tried to do a build via maven (2.0.4), but it fails mvn compile Compiling 487 source files to /Users/gerwinbrunner/Documents/ workspace3.2/xwiki/core/target/classes [INFO] ------------------------------------------------------------------------ [ERROR] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Compilation failure /Users/gerwinbrunner/Documents/workspace3.2/xwiki/core/src/main/java/ com/xpn/xwiki/plugin/lucene/IndexUpdater.java:[32,34] package org.apache.lucene.analysis does not exist /Users/gerwinbrunner/Documents/workspace3.2/xwiki/core/src/main/java/ com/xpn/xwiki/plugin/lucene/IndexUpdater.java:[33,31] package org.apache.lucene.index does not exist /Users/gerwinbrunner/Documents/workspace3.2/xwiki/core/src/main/java/ com/xpn/xwiki/plugin/lucene/IndexUpdater.java:[34,31] package org.apache.lucene.index does not exist /Users/gerwinbrunner/Documents/workspace3.2/xwiki/core/src/main/java/ com/xpn/xwiki/plugin/lucene/IndexUpdater.java:[35,32] package org.apache.lucene.search does not exist /Users/gerwinbrunner/Documents/workspace3.2/xwiki/core/src/main/java/ com/xpn/xwiki/plugin/lucene/IndexUpdater.java:[36,32] package org.apache.lucene.search does not exist /Users/gerwinbrunner/Documents/workspace3.2/xwiki/core/src/main/java/ com/xpn/xwiki/plugin/lucene/IndexUpdater.java:[37,32] package org.apache.lucene.search does not exist /Users/gerwinbrunner/Documents/workspace3.2/xwiki/core/src/main/java/ com/xpn/xwiki/plugin/lucene/IndexUpdater.java:[38,31] package org.apache.lucene.store does not exist Could someone give me a hint on what else I need to check out. I think I'm missing some modules? MfG Gerwin Brunner Bizzons eMarketing GmbH Nikolaiplatz 4 A-8020 Graz Tel: +43-1-890-3408-240 Mobile: +43-650-7720448

18 years, 2 months

[VOTE] Removing automatic assignment on JIRA

by Vincent Massol

Hi, I'm trying once more on this theme... For Xwiki issues are assigned by default to Jeremi. We know very well that Jeremi isn't going to work on them and he's busy on other stuff. I'd like to remove automatic assignments. For this we need to enable "Allow unassigned issues" to true in JIRA. I'd like to get help from the community for working on issues and also I don't have clear visibility on who's going to commit and work on what issue. I'd much rather see an issue that is unassigned and know that nobody is going to work on it if we don't find a taker than seeing all issues assigned which gives a false sense of security. Here's my +1 to remove automatic assignments, especially as we get to see the issues on the dev list now. Thanks -Vincent ___________________________________________________________________________ D�couvrez une nouvelle fa�on d'obtenir des r�ponses � toutes vos questions ! Profitez des connaissances, des opinions et des exp�riences des internautes sur Yahoo! Questions/R�ponses http://fr.answers.yahoo.com

18 years, 2 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs