Hi all-
Just wanted to propose a short term conceptual plan
forward for Apache River, and see if we're in sync.
Once we get the source accepted and contributed
to the project (hopefully this week!)... I'd like to propose
that we immediately start working on a release (v0.1). This will
not only help us understand the paces of getting a release
out through Apache, but also provide a release to the Community
from Apache. To focus on getting a release out, the initial work
would be targeted at integration stuff (for example, getting Service UI
integrated) and some documentation rather than on very many
bug fixes or rfes.
Once we accomplish that, we can turn our focus towards another
near term release (v0.2) which could include additional bug fixes
and smaller rfes as well as any cleanup we learn from getting
the v0.1 release out. This would not only provide an added value
release out to the Community, but also give us further experience
and additional momentum of an active project moving forward.
At that point, I think we'd be seasoned enough to focus on a
release with some 'meat to it' ;-) (some of the more major bug
fixes/rfes that have been discussed).
Running in parallel to this development focus, I think there
should be some longer range project discussions (what kind
of releases do we eventually want to do in the project, what
are we trying to accomplish (iterating on the core infrastructure
or branching out into other areas), etc).
There it is (again - high level, just to see if we agree on an
overall direction). Please share your thoughts.
thanks -Jim
ps. On a specific item - not sure where a package name
(to org.apache) change would fit in this proposal. Maybe
release v0.2 or after?
