Hi developers,
Our planning suggests that we release beta 3 tomorrow. It seems
everyone was busy and not much work has been done for beta 3. Here's
what we have done so far: http://tinyurl.com/yutdw7
Thus we have 28 issues fixed in Beta 3.
There are 61 remaining and planned in Beta 3, 28 in Beta 4 and 9 in
RC1. Total = 97 before 1.0
Seen our manpower I think we can assume we can do 25 issues per 2
weeks releases (Marta is not going to be available much in Feb 2007
as she'll be working on other stuff).
97 / 25 == 4 releases. We have 2 currently planned (Beta 4 and RC1).
Thus we have 2 questions to answer:
1) Do we release Beta 3 today?
2) How do we fix all issues for 1.0 final?
Do we release Beta 3 today
-----------------------------------
My personal preference is to continue doing bi-weekly releases as:
1) It trains us to do releases and improves our release process
2) It gives a rythm which is good for us and for our users. I believe
this is extremely important
3) It allows us to iron out migration issues
4) It allows our users to report issues as soon as they happen rather
than reporting them at the end when we're close to releasing 1.0
The possible downsides:
1) Too many releases for our users. I don't think this is valid as we
have release notes and our users do not have to upgrade. They can
decide by looking at the release notes.
Thus my recommendation is to prepare Beta 3 release today and do the
release tomorrow.
Let me know if this is fine with everyone. If this is fine I'll
create a branch for Beta 3 in a few hours.
How do we fix all issues for 1.0 final
---------------------------------------------
Looking at what we fixed in Beta 1, 2 and 3, I still believe we
should focus more on fixing only important bugs and move out
improvements and nice to have stuff. I believe we need to review
again the current issues tasked for 1.0 and move those that are not
important bugs. Also we should be careful not to create new issues
for 1.0 if they are not bugs.
Let's do this sorting and let's post back here. If it still doesn't
fit in the planned Beta 4 and RC1 then we might need to include
another Beta 5.
WDYT?
Thanks
-Vincent
___________________________________________________________________________
Yahoo! Mail r�invente le mail ! D�couvrez le nouveau Yahoo! Mail et son interface r�volutionnaire.
http://fr.mail.yahoo.com
Jeremi,
Do you think you could use branches and thus benefit from the
versioning feature of SVN? :-)
The idea is:
* Create a 1.0 branch and move gelcv1 to it
* Make the trunk be the 2.0 version
WDYT?
Thanks
-Vincent
On Jan 25, 2007, at 7:06 PM, Jeremi Joslin wrote:
> Author: jeremi
> Date: 2007-01-25 19:06:04 +0100 (Thu, 25 Jan 2007)
> New Revision: 1988
>
> Added:
> xwiki-apps/gelc/gelcv2/
> Log:
> Created directory xwiki-apps/gelc/gelcv2
>
>
>
> --
> You receive this message as a subscriber of the xwiki-
> commits(a)objectweb.org mailing list.
> To unsubscribe: mailto:xwiki-commits-unsubscribe@objectweb.org
> For general help: mailto:sympa@objectweb.org?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/
> wws
___________________________________________________________________________
Yahoo! Mail r�invente le mail ! D�couvrez le nouveau Yahoo! Mail et son interface r�volutionnaire.
http://fr.mail.yahoo.com
Hi all,
We are looking for wiki solution. Your XWiki looks impressive but we have one question.
We need authentication from LDAP and also handling the groups and user privileges from LDAP. We saw on JIRA [#XWIKI-330] issue (new feature) about that. Is someone taking any progress regarding this or do you know when this kind of feature is going to be in you software?
Regards Sasa.
Hi Ludovic,
Sorry I'm late on this (was on holiday). See below
On Mar 9, 2007, at 6:44 PM, Ludovic Dubost wrote:
>
> Hi,
>
> I'm in the process of finishing an XWiki Google Web Toolkit API
> (server-side and client-side).
> I'd like to commit that one in the core including the Java code
> that is
> compiled to Javascript. There is common code for both.
> Curriki will also rely on this API.
> It is not necessary that the build system compiles the code to
> Javascript for the moment, however it is needed to compile the
> server code.
>
> Currently I suggest commiting the code in:
>
> web/standard/src/main/java/api
> or
> web/standard/src/main/java/com.xpn.xwiki.gwt.api
>
I suggest committing this in a new module in xwiki/xwiki/trunk/web/gwt
One reason is that it's not going to work for m2 where you have
currently committed it (in standard/). We won't be able to use the
gwt maven2 plugin there.
Also it's cleaner to separate it from the rest. This is the general
direction for the build: separate different "features" into different
build modules for a better modularity.
Here's how I see it working with m2:
* The gwt m2 plugin generates the javascript from the java files in
the generate-sources build phase
* We use the WAR plugin in gwt/ to wrap both the server java classes
and the generated js into one WAR
* We then use the WAR overlay feature of the WAR plugin in standard/
to add the gwt WAR.
Please let me all know if you're ok with this and I'll do the move.
> I also have a Google Web Toolkit client for the FeedPlugin. It's a
> very
> cool RSS Aggregator interface.
> It's only client side code. I'm not sure if it should be commit in
> the core.
I don't think it should be in the core but for now I'd rather we have
it in a separate module in web/rssreader. Again the idea is to use
the m2 plugin to generate a WAR overlay for the standard WAR.
In the future we need to think how to externalize this in the same
way as we're externalizing plugins in xwiki-plugins. We can probably
consider it as a XWiki Application in the same manner as we have
Blog, Calendar, etc applications. We need a xwiki-applications
directory for these (different from the current xwiki-applications
which is for applications like Curriki sitting on top of XWiki). Then
when we build the default wiki we'll include several of these
applications in it and we'll also release them as XARs.
Again let me know about the creation of the rssreader module and I'll
do it.
> If it is it would be in
>
> web/standard/src/main/java/rssreader
> or
> web/standard/src/main/java/com.xpn.xwiki.gwt.reader
>
> Can we vote for these 2 things:
>
> - commit the API
> - commit the RSS Reader
See above.
Thanks
-Vincent
Hi,
One user spammed our jira yesterday (user name: "marie"). I've
removed the spam comments she left and removed the user from JIRA.
-Vincent
___________________________________________________________________________
Yahoo! Mail r�invente le mail ! D�couvrez le nouveau Yahoo! Mail et son interface r�volutionnaire.
http://fr.mail.yahoo.com
Hi Sergiu,
Ludovic has noticed several important issues with beta 3. Apparently
this is cause by a modification you made, see http://
svn.forge.objectweb.org/cgi-bin/viewcvs.cgi/xwiki/xwiki/trunk/core/
src/main/java/com/xpn/xwiki/XWiki.java?r2=1946&r1=1944&rev=1946
Apparently there are some data loss happening, some strange stuff
with history, some panels do not work anymore (the Add Object panel
doesn't work for example).
Ludovic is suggesting we rollback this change.
WDYT?
Thanks
-Vincent
PS: I'm holding of the release till this is resolved.
___________________________________________________________________________
Yahoo! Mail r�invente le mail ! D�couvrez le nouveau Yahoo! Mail et son interface r�volutionnaire.
http://fr.mail.yahoo.com