> > How's about Avalon 5?
> AValon5 refers to framework classes which are on a completely different
> release schedule than logkit and Logkit should never need another major
> version.
AV5 also refers to a container and component packages.
As an aside, I disagree with respect to the release schedule on the
following grounds.
When we release James vX, we release all of it. There may be classes,
entire subsystems, that haven't changed in ages. But they are all part of a
single, defined, tagged, supported Release build.
Any project that adopts a piecemeal approach to release management
encounters problems. This isn't to say that there aren't reasons to do so.
In some cases it makes sense, but it rarely doesn't cause problems, so it
should be avoided when possible.
Yes, someone else can take Frameworks and Components, and write their own
container. But that is their problem to support. The Avalon PMC is
responsible for what it ships.
This isn't to say that there isn't a place for releasing supplimental
packages separate from the main release. But a coordinated approach to code
release should be normative, in my view.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
