| [birt-pmc] Callisto release plan update |
|
All, I attend the Eclipse planning council conf call this
morning. The main topics in the
call are Callisto schedule and technical requirements
for each project. On schedule, the immediate milestone is M5, the goal of this
milestone is to have all projects “work” together on top of the
3.2M5 platform and have all projects available for update from one update
manager link. David from IBM
have draft a proposal in this link about how the update site will work, please
review and let’s discuss it in our Monday PMC meeting. http://wiki.eclipse.org/index.php/Callisto_Coordinated_Update_Sites Action item for us in M5 are (a) move our build and
development environment to platform 3.2.
(b) complete the feature and packaging project
to support the Callisto update site. On Callisto technical requirements
for each project,
following are the 5 items discussed 1.
All Callisto projects must “work” against
Eclipse 3.2 2.
All Callisto projects should have jar'ed
plug-ins 3. All Callisto projects should
use Eclipse message bundles (not Java resource bundles) 4. All Callisto projects
must use capabilities to avoid conflicts in UI menus, tool bars, etc… 5. All Callisto projects
must use ICU4J Bjorn will update the Callisto
project page on what is required, from what I can gather during the call, (1)
is required, “works” means all projects must run on 3.2 and
community developers can build on 3.2 with the source code download. (4) is required. (5) is required but we
will know the specifics after M5.
(2) and (3) are strongly recommended. We can discuss these items in our Monday
PMC meeting. Regards, Actuate Engineering |