Releases for Project Forecast
project_forecast 6.x-1.0
| Download | Size | md5 hash |
|---|---|---|
| project_forecast-6.x-1.0.tar.gz | 18.84 KB | 5dcf4814c2a480758a48e43b779035a5 |
This module has been in -beta and -rc long enough, let's have a stable release.
6.x-1.0 brings a minor fix in its value provider section so that it can make use of the larger fix in the Value Providers module, which in turn gets rid of some situations where the forecast would be calculated incorrectly. Also, the milestone add-on's dependency on CCK is now documented in the .info file, so you can't get PHP errors by accidentally enabling the milestones add-on but not CCK (Drupal won't let you do that now).
And that's it! I know that a lot could be done in terms of documentation and transparency, but the module works completely fine now so let's still enjoy the 1.0. Yay!
project_forecast 6.x-1.0-rc3
| Download | Size | md5 hash |
|---|---|---|
| project_forecast-6.x-1.0-rc3.tar.gz | 18.88 KB | 72bc10f37d2b42b0130c0c3ba03ed1bf |
Seems I only tagged the task_status subdirectory for the last release so it was unusable... sorry for that. This one should be working fine again, plus Views 2.0 compatibility is now restored also for the milestones add-on. Please report any bugs in the issue queue, and update to this version as soon as possible!
project_forecast 6.x-1.0-rc2
| Download | Size | md5 hash |
|---|---|---|
| project_forecast-6.x-1.0-rc2.tar.gz | 6.96 KB | 690fd742b64bccae0323a22a01fb9207 |
Dude! The last release of Project Forecast was in July? High time we get another one.
This release candidate features compatibility with the current Views and CCK releases (at the moment, that's Views 6.x-2.1 and CCK 6.x-2.0-rc10) so if you needed to defer updates because of Project Forecast, you can now update to these newer versions. (As we all know, Views 6.x-2.0-rc2 brought a pretty grave incompatible change so all the modules had to adapt their Views integration.)
Oops, just noticed that the Milestones extension module didn't get updated to the new Views yet. You'll need to wait for another release for that :P
Also, this release candidate features further usability improvements, most importantly the combination of the general ("Relationships") and "Task filters" configuration tabs into a single admin settings page.
And lastly, this release also contains a new add-on module, Project Forecast Task Status, which makes it possible to influence a task's time need (for the calculation, at least) depending on a task status field with fields like "open", "in progress" and "closed".
project_forecast 6.x-1.0-rc1
| Download | Size | md5 hash |
|---|---|---|
| project_forecast-6.x-1.0-rc1.tar.gz | 17.12 KB | 7fe8985745999f85366872bd8c75854a |
Complete revamp. I won't go as far as to list all the improvements, let's just say the previous version was an unusable hack and this one is better :P
Make sure you update all the dependencies to the latest versions (which are, at the time: timebudget-6.x-1.0-alpha1, duration-6.x-1.0-rc1, project_admin_category-6.x-1.1, and, new dependency, value_provider-6.x-1-0-beta1). Hope it works for you, if it doesn't: bad luck, because now I'm away and my company is now responsible for maintaining it. Hopefully they'll do a good job - which is probable, because they need it in one of our products which is currently being developed :-]
project_forecast 6.x-1.0-beta1
| Download | Size | md5 hash |
|---|---|---|
| project_forecast-6.x-1.0-beta1.tar.gz | 14.63 KB | 91f4496bbda4dab4ce5e3dc1b52e85a4 |
Initial release. Tested and working with CCK 6.x-1.0-alpha and Views 6.x-2.0-beta1. I also tried with beta3, but it seemed to have a bug as it returned the result query with wrong column names, which does not suit this module very well. I'll investigate and maybe submit a patch for Views, if it hasn't been fixed in HEAD already.
As for this release itself, the README.txt is still missing but everything works, though it would be nice to have a few more additional data sources for a more accurate calculation of the forecast (time already spent this week by a given user, taking task states into account for the remaining time need, etc.). But if you like the idea, you probably can do without these features for now :)
