• Mercurial Support ??? (Really would be nice to do - but not sure will able)
• Split emforge-web to emforge-core and emforge-web
• Bug-Fixing

• Remember Me & Single Sign-On
• Bug-Fixing

• Windows Installer
• Filters for tasks in GUI (like we implemented in MyLyn connector)
• Support for MsSQL
• Bug Fixes

• Maven-SCM Support - should allow us to browse many version control systems
• MyLyn connector
• Localization
• Finish Geronimo support (failed... seems we will not support Geronimo for now)
• Add into downloads zip-file with emforge bundled together with jetty - to provide ready-to-use package with minimal dependencies (see here for possible solution).
• Upgrade manager (for automatically upgrading database then new version is installed)

Current Status (May 19 2008)

• MyLyn connector is mostly done for read-only mode, so, it is possible to get list of tasks by calling different searches, as well as view detailed task information, but - it is not possible to add/edit tasks
• CVS Support - for implementing CVS support we changed EmForge to work with Version Control Systems via maven-scm. Unfortunately no anyone CVS provider does not supported currently required rls command, so, we will need to fix it.

We hope to finish active development during this week, so, during next week we will able to test and finally release new version of EmForge

• Bug-Fixing
• Improving working with Reports
• PDF Export
• Better integration with JBossAS, Geronimo, Glassfish

Nothing serious planned for this milestone - onle bug-fixes for critical problems what will be found them EmForge will come public

Some extra functionality should be done:

• Initial Reports Implementation (^15833)
• Initial Web-Services Implementaiton (^76676)
• Whole project should use same service implementation for working with jBPM as used via Web-Services.
• Fix problems with Glassfish
• Write EmForgeSetupGuide
• Write EmForge Workflow Development tutorial

Major issues for this milestones are:

Design

During working on design we also should fix several issues, related to common errors processing, common design rules for all pages and so on

Processes and Task

Ok, EmForge is BPM based, so, we have workflow as background, and this thermins are growing from jBPM, but we should make it more easy for other people to work with it understand it.

• Switch from tomahawk to RichFaces
• Switch to jBPM-JPDL 3.2.1 (seems latest for now)

A lot of plans for this milestone - major is to make it publically avialable.

Publish sources

Wiki Improvements

• Implement searching by pages
• Implement Diff

Source Browser

Role Management

Moving to another server

I decided to prolong milestone to one more week to be able finish all planned tasks. Anyway we already installing it to the our servers

Design!

Most changes in this version was realted to design - we tried to make it a little bit more better.

Also, some other features was done:

• Ajax-Based Table Pagination
• 'Request Status' for tasks
• Configuration Issues
• And a lot of bug-fixes

Major features in this version:

• Most important for me is that most job for this version was done without me :) Sergey and Mikhail (and Arcady) done really good job!
• Mikhail prepeared custom reports (^11902) for Collaborative project. It is currently hardcoded - and not user some Report Engine (JasperReports for example) - such functionality we will implement later;
• Sergey did a big job for migration Wiki-Interface to the JSF (^19435);
• Arcady joined to the project and did some minor features;
• Anonymous access to the server is enabled (^24782). Now, emforge server available not only for registred users! Feel free to show it to your friends!
• Some improvements for Task-Form - to make it more comfortable to work with tasks

But, design is still ugly, and a lot of functionality is missed - so, we do not starting the promotion company at the moment - probably after next milestone

• Some tasks required by Collaborative project
• Continue JSF-Migration (Especially migration of Wiki-Interface to JSF)
• Bug fixing, Bug-Fixing, Bug-Fixing
• Expecially for HTML Editor and IE issues

• Migration of Project-Related Pages to JSF
• Simplifiying the working with processes & projects & milestones:
  • Selecting current project ^3476 (it is partially implemented)
  • Selecting Milestone from Combobox ^747
• Integration of Workflow Management & Wiki-Engine:
  • Now, it is possible to specify Wiki-Based Description for Project Definition ^13109
  • Wiki-Page is assigned to each process-instance (as description) (^3532). So, you can place links to the processes (seems currently doesn't work) and
  • You can attach files to the processes (^2454)
• Many smaller improvements and bug-fixes
• Ajax added. We started to use Ajax technologies in the project. Currently you can see it in Comment-Editing - Switching from Wiki to Preview and back performed without reloading whole page.
  • But in same time we removed possibility to edit comment with HTML-Editor. Unfortunately we did not managed to make any HTML editor available for JSF to work stable and correctly - so, currently they are removed. Waiting for stable releases of Tomahawk and MyFaces - hope it is fixed there.
  • Note: Ajax functionality in this Version does not work under IE 7.0 - may be under IE 6.0 too. Use Company-Recommended FireFox browser !!!

• Bug-Fixing (I sure in EmForge-0.14 will be a lot of bugs)
• Continue Migration to JSF (ProjectList, Project Form and Edit Project Form should be migrated to JSF)

• Bug-Fixing
• Migration BPM Related GUI to the JSF/Facelets
• Other Improvements Related to Task-Window (Like previews for Comments)

• Continue working on Milestones (close milestones and so on)
• Support for History
• Bug-Fixing

Main task for milestone EmForge-0.12 is bug-fixing in wiki to make it better to use and continue migration to jsf/facelets.

Major targets for this release are:

• JSF/FaceLets integration;
• BugFixing;
• Continue to work on the MileStone page.