web2project v2.1 Release Notes
Tags: 
Date: 24 September, 2010 - 04:54

web2project homepageAs of 22 September 2010, web2project v2.1 is officially released! You can download it from SourceForge now.

For Project Managers, there are not a huge number of tangible improvements. This was mostly a cleanup release:

  • The most important part is that now a User can add Tasklogs for people other than themselves. When you create or edit a Task, you can denote "Allow users to add task logs for others" which allows just that. Users can add hours for anyone currently assigned to work on the Task. The system tracks who logged the time for audit purposes.

For Developers, we had a significant number of cleanups related to timezones, Gantt chart creation, and miscellaneous things here and there:

  • The most important part are some cleanups related to the contact_methods refactoring. There were a number of issues that made it into the v2.0 release that are now closed.
  • More useful in general was a complete refactoring of the Gantt chart creation. One of our goals for v2.2 is to supplement the current image-based (jpGraph) Gantt charts with both a jQuery and a Flex/Flash-based option.
  • We added a significant number of Unit Tests for the system in general but focused on the PEAR/Date and CDate classes specifically. We hope to replace PEAR/Date with core PHP functionality in coming releases.
  • We resolved a number of browser compatibility issues for IE 8.
  • iCalendar generation has been updated to create VEVENTS that pass validation as per the formal specification.
  • We moved a number of duplicate and oddball functions into the deprecation area for refactoring and eventual removal.

For anyone who might be interested, the big time sink during this release was of a legal nature. After the battle between WordPress and the Thesis theme played out and how the GPL could be interpretted, we investigated what it would take to change to a BSD-based license. The good news is that it will be possible - more to follow - and the bad news is the amout of effort involved.

Once again, some great community members stepped up and did a great job in reporting issues, testing fixes, and generally offering insight and sanity checks. Special thanks goes to opto and figgles.

In summary, we closed 38 issues including 3 crash-level issues, 20 minor issues, and 4 features. As always, these are just the formally reported issues and don't include smaller items that were reported via Twitter, the web2project forums, and other means. If you want to explore everything of interest, check out the web2project v2.1 Release Notes. And of course, if you're looking for ways to collaborate with us more easily, you should check out our web2project git repository.

You can download web2project v2.1 from SourceForge now.

* And yes, I always wait a few days to announce the releases in case we have to make a patch release. ;)


Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Your comment on dotProject

Mr. Casey,

I found your comment "Keith Casey (usuário não registrado) em 14/10/2010 às 11:55 am - Since dotProject is effectively dead, you should look at web2project. We have an upgrade path from dotProject and 20-50x improvement on many screens." at http://br-linux.org/2010/curso-dotproject-no-rio-de-janeiro/, to be very, very offensive.

That page is about a dotProject course on Brazil, that could also be a knowledge source to future w2p users. But now, people that see your comment will think I'm trying to fool them, and probably they're not going to take the course. There's no w2p course on Brazil, not even a community so, probably, they will go elsewhere and make a MS Project course. Very good to all of us. More than that, it's simple a lie that dP is dead. (See a dP commit, made 7 (!!) days ago, it's right here: http://dotproject.svn.sourceforge.net/viewvc/dotproject?view=revision&revision=6051)

You could have made your comment/advertise about w2p without offending dP and our community. I never said bad things about web2project and I even comment that it is an alternative and should be analysed. I don't know how flames could be good for the free software community, dotProject or web2project. Shame on you.

Diego Viégas

dotProject Dead

With all due respect, dotProject is effectively dead:

When you have to write an annual blog post explaining how your project isn't dead, there's a problem. And to be clear, I was guilty of this when I wrote the posts in 2006 and 2007.

Next, they're now at a year+ between patch level releases. The security vulnerability reported in July 2008 took a year to be fixed. The major vulnerability reported in October 2009 and announced publicly in January 2010 is still unresolved. They have code out there that they know has major vulnerabilities and have done nothing to address it.

Despite being released almost 6 months after the PHP 5.3 release, there are still problems and bugs related to 5.3. We're now almost a year later and the bugs are still open.

Many of the recent commits are actually patches written by me and many others during the 2006-2008 timeframe but are only now being applied to the system. I recently had a patch accepted that I submitted in October 2007. Yes, there are bugs that should have been closed three years ago that are simply left unresolved.. why?

But since it's a volunteer team, it's not their fault, right?

I strongly disagree. When you have code that is used by hundreds or thousands of people, you have a responsibility to make sure your code works. Mistakes and bug happen, but you have a responsibility of identifying those bugs and working to get them closed. Letting bugs - especially major security vulnerabilities - sit open for years is irresponsible.

Despite my comment, I would encourage you to check out web2project. I think you'll be impressed by its speed, stability, and general ease of use. More importantly, there are well over 150+ dotProject issues that have been closed and dozens of new features added. You'll find a system with strong Unit Testing, proper timezone support, very extensible, strong pr-bt support, and solid coding standards and practices. Also, you'll find a community that is open and welcoming.

Regardless, I appreciate your feedback.

I did not mean to offend you or cause people to believe that you are deceiving them. Please feel free to delete my comment on your site.

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <br> <img> <p> <blockquote> <strike>
  • Lines and paragraphs break automatically.

More information about formatting options