| RE: [birt-pmc] 2.1 Project Plan |
|
Good points. I agree we shall update the planning doc
to indicate that we plan to do. I have logged bugzilla requests for item 2
to each component. Some of the plugins probably can not be
jar’ed because we need user to download third party packages into those
plugin folders. Specifically
the PDF emitter and View plugins
will still need to stay in folder format. Item 3 message bundle is not scheduled for
2.1currently for lack of resources to commit to it. Wenfeng -----Original
Message----- Guys, Sorry to bring this up after the fact, but as I was
going through the 2.1 requirements today, I remembered Wenfeng's email from
2/3/2006 about the Callisto Requirements. I think that our 2.1 project
plan should reflect a stance on each of the following items (pulled from the Callisto
project web site). Currently the project plan mentions that this is part
of the Callisto release without specifically identifying which of the
requirements we will be in compliance with. Since three of the five are must have requirements, it seems the only
two that we need to address are items 2 and 3. I assume that we
will be in compliance on items 1, 4, and 5. Callisto Requirements
This group (the Planning Council) is the body that
sets the requirements for Callisto. As Kevin stated, our key goal is to be the
best that we can and thus these requirements are minimums. 1. What
we deliver in June must work
together. Thus if project X does not work with Callisto, it will not be part of
Callisto. Additionally, once this Planning Council believes that a project X
cannot safely be made to work in time for Callisto, the project will be dropped
from Callisto. 2. All
Callisto projects should have
jar'ed plug-ins because this is good Eclipse citizenship. 3. All
Callisto projects should use
Eclipse message bundles, not Java bundles because this is a good Eclipse
citizenship. 4. All
Callisto projects must use ICU4J
by RC0. 5. All
Callisto projects must use
capabilities. Scott |