Re: Community update

On Wed, Aug 25, 2004 at 08:25:11AM -0500, Bob Jacoby wrote:
> Thanks for all the responses. I guess I'm still a little confused on
> the difference between APLAWS and APLAWS+. Your and Richard's statement=
s
> seem to have subtle differences, but this may be due to the APLAWS vs=20
> APLAWS+ thing.

APLAWS comes in three versions. The original one was against CCM 5.0,
the second versionwas against CCM 5.2, while the third was against
CCM 6.1.  Since this third version was such a huge step forward, it
was decided to call the new release APLAWS+

>=20
> Richard: "Patches to APLAWS+ that affect CCM should (and generally do) =
find their way upstream."
> Daniel: "APLAWS & CCM are one & the same codebase ..."

My fault, I should have said APLAWS+ here.

> Let me express my understanding so you can correct me...
>=20
> APLAWS was a fork from the original CCM codebase. It provided=20
> additional features (and perhaps bug fixes) that were not=20
> supported within CCM. APLAWS+ is separate from APLAWS and=20
> bundles together various applications and components. APLAWS+
>  pieces were written to be based on the APLAWS fork of the CCM
> and would not work against CCM itself. The APLAWS fork has, for
> the most part, been merged back in to the CCM codebase and for=20
> all intensive purposes doesn't exist anymore. APLAWS+ can therefore=20
> work against the CCM codebase, with the exception of a few pieces=20
> that still require the APLAWS fork (I assume due to some functionality=20
> in APLAWS that wasn't merged in to the CCM codebase).=20

In the first two version of APLAWS we maintained a fork of Core + CMS
in order to add significant new features which could not be done on the=20
official stable release branch. All the changes that matttered in APLAWS=20
branch of Core 5.2 were merged into Core 6.1. Thus the new release  (now
called APLAWS+)  can run on the official stable release branch of Core an=
d
CMS 6.1.

> >From Richard's statement I infer that APLAWS+ still makes modification=
s
> to code that exists within the CCM codebase so another fork exists - ju=
st=20
> at a higher level. With the move to ObjectWeb do APLAWS+ developers int=
end
>  to stop introducing these core changes in to APLAWS+ and put them in C=
CM
> from the beginning?

Exactly correct. All changes APLAS+ requires to Core/CMS will be made
to the standard CCM codeline. We don't anticupate these changes to be
anything other than bug fixes  in the short term since the current
project focus is on stability and quality.


Dan.
--=20
|=3D-   Red Hat, 338 Euston Road, London, NW1 3BT.  +44 (0)7977 267 243  =
 -=3D|
|=3D-         Perl modules: http://search.cpan.org/~danberr/             =
 -=3D|
|=3D-             Projects: http://freshmeat.net/~danielpb/              =
 -=3D|
|=3D- GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505=
 -=3D|=20


--=20
Redhat-ccm-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/redhat-ccm-list
Archives: https://www.redhat.com/pipermail/redhat-ccm-list/