Anonymous
Unregistered
|
|
At my project, we've given XPlanner a mild try, but decided not to fully invest given some inconsistencies and bugs/problems we found.
Is XPlanner still maintained? From what I see at the forum, it looks deserted:
http://sourceforge.net/tracker/?group_id=49017&atid=454848
Cheers,
- Mark
|
Anonymous
Unregistered
|
|
If you look carefully, you should see the link to http://xplanner.codehaus.org where the project is been moved.
And the last news on that site was August 9th...
|
Anonymous
Unregistered
|
|
Aah I see, thanks for your reply...!
|
Anonymous
Unregistered
|
|
XPlanner is actively been developed. My company, Sabre, is investing 2 full-time equivalent developers to extend it and we are about to standardize its use across the entire organization (~1800 developers distributed over 3 continents).
We haven't made any release since last September because of my time constraints and a technical issue that got resolved once we moved to our new home codehaus (and subversion). 0.7 is due out soon and is a major improvement over what was presented in the article.
You can follow the status of the upcoming 0.7 at http://docs.codehaus.org/display/XPR/Release+0.7. You can file new requests into our jira instance at http://jira.codehaus.org/browse/XPR?report=com.atlassian.jira.plugin.system.project:roadmap-panel
Jacques Morel
XPlanner project manager
jacmorel@xplanner.org
|
Anonymous
Unregistered
|
|
One of Agile's great strengths is release early, release often. There's not been any public releases (outside of SVN) that adds anything visible, and neither the 0.61 or 0.62 releases seem to work (both fail with a NullPointerException on JBoss/Tomcat/MySQL on Mac OS X).
It also doesn't help that the http://www.xplanner.org/ doesn't mention anything about http://xplanner.codehaus.org/
The most amusing thing is that if you were using Xplanner to organise Xplanner development, you'd have iterations and functionality planned that others could see as well, even if they couldn't change it :-)
|
Anonymous
Unregistered
|
|
This is exactly why I'd be careful when considering this app. Look at the attitude: "Well, the problem could be *anywhere*. You have a null pointer exception to work with. Good luck." It is by no means easy to install as the article mentioned. Sure, it may be fine for some, but go look at the Forums on SourceForge at all the people trying to get it running on modern OSes. Everything's in chaos and disarray with xplanner right now.
|
Anonymous
Unregistered
|
|
Are you speaking from experience? ;-)
I have found that even though xplanner install is not for the faint of heart, most people that ask questions on the forums will find a solution to their problems. A few, I have to grant you that, will not and drop xplanner.
I believe most people in that camp have overlooked a very important passage of the install docs: xplanner only works on 1.4 and is only tested on tomcat5.0 and mysql4.x. Any other platform is not TESTED!!!
Stick with that setup and it is relatively simple to install xplanner. Diverge from it and prepare for a lonely road of java webapp install hell. Fortunately for them we answer their questions and help them in any way we can. Unfortunately, this means less time developing xplanner... ;-(
In any case, once the initial install problems go away, the product is very stable and provides good value especially for distributed teams.
Again remember: as any OS project it is done in our spare time. There is so much we can do.
FYI, 0.7 is in beta right now and it tries to address some of the installation headaches.
Jacques
|
Anonymous
Unregistered
|
|
As explained on the forum, for the past year, the product was mostly developed internally to Sabre. There we released frequently.
Several things contributed to the apparent lack of activity:
1. Split of the code base due to our inability to work through our corporate firewall. This motivated our migration to codehaus in May in order to use the proxy friendly subversion. Since then we have started to use our public tools (jira, confluence, forums, mailing list) to keep the community up-to-date. Until that point, there was no immediate value in publishing anything (except making sure people did not believe the project dead ;-).
2. My availability that prevented me to a. merge the code back, b. test/release sufficiently for a public release. As the change set became bigger, the more time it required of me to release hence the vicious circle that we are about to break out of!
Now that 1. is resolved and 2. is somewhat less of a problem, we are going to release more often. Our goal is to synchronize our internal and external releases therefore to do a milestone every 2-4 weeks and a release every 2-3 months.
Jacques
|
shay.bc
Unregistered
|
|
my team uses XPlanner as its main technical assigments distribution tool, and version planning/tracking tool, and a place to track bug fixes. although my corporate utilise many tools that cover these area (PS8, MSProject, TestDirector...) non of them is complete or accessable at times to my dev team.
we have search for a way to deal with our needs and the ONLY free solution that covers all the needs such as:
2 way communication developer->team leader on every assigment, priority based stoties, the ability to maintain searchable multiple versions projects in our place multi channel is allso an issue and much of the assigments are joind so XP answer that, the ability to easally and rappidlly move assigments as managment decidiond are made, capability to share the knowladge and let others the rights to change, remark, priorites etc. we are able to track test director bugs fix process through it just by linking TD to the story, even deploy versions has its own story at every release so we can monitor what version was deployed when and why ...
long story short we gave it a try, installed it by the book, had no problem integrating hebrew into it (beside search problems), my boss is happy with it, our project managers utilise it, and i have a way to control my teams assigments and they have a way of knowing every little time where the preasure is, what is more importante and what needs to be done when they are freed, also they can allways tell what is the deadline and priority of each assigment without too much talking and morning meetings to cever that section.
the funny thing is that we are driven to change the way we work due to the use of XPlanner and not the other way around since we see that the XP way suite us.
we are more then happy with XP, we are now integrating it to other dev teams at our corporate, we are anticipating upcomming release to provide more features,
like: alerts (notify team leader when assigment is complete, stuck more then... you can use "drools" maybe :-)) on changes, time planning date wise for each task, support more then 2 developers for a task, integration with eclipse and clearcase (so we can link source and baselines to a version, story task, this way we can deploy version depending on stories decided to deploy at the version tailor time), asimple javascript auto refresh at "Me" view and more
|
|
Previous
Index
Next
Threaded
Edit
Reply
Quote
