some notes about Safari team plans for WebCore and JavaScriptCore

[Chris Lee]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

First off, I'd like to say a huge "Thanks" to Apple for picking KHTML. (And of 
course, to our own KHTML devs for kicking ass in the first place.)

Second: Darin, you've given some interesting input for wanting to keep the 
development split. Is there any reason why Apple couldn't develop on a 
khtml_safari or a khtml_webcore branch in our CVS? You can enforce your 
commit policy, your testing procedures, and you could retain full control of 
the entire branch.

Alternately, since I know that Lars has been doing a lot of work like this in 
the past, is there any reason why the more controversial or unstable stuff 
wouldn't continue to be developed in the make_it_cool branch in our CVS? I 
think this would be less preferable than the first, since I don't think 
anybody would be willing to make any guarantees about the state of HEAD at 
any given time... but I don't see any reason why development can't be along 
two branches in the same repository.

And if Apple is concerned about reliability or speed or anything about the CVS 
server, I bet one of those shiny Xserves would make a nice cvs.kde.org... :)

- -clee

On Tuesday 22 July 2003 3:19, Darin Adler wrote:
> On Tuesday, July 22, 2003, at 02:55 PM, Dirk Mueller wrote:
> >> - Although we don't want to rule it out permanently, we don't plan to
> >> share a single source tree with the KDE original of KHTML any time in
> >> the foreseeable future.
> >
> > Can you elaborate on the reasons behind this decision?
>
> Here's one reason we won't do this any time soon:
>
> - Our team needs to be able to control what goes into our tree; there
> are at least some changes that happen in the KDE version that we don't
> want. I'm certain there are also changes we have made that you don't
> want, given things that have been said on this mailing list.
>
> Here are a few other considerations:
>
> - Our schedules are different; a current example is that we have been
> doing lots of active development, and shipped 1.0 recently. KDE head is
> not considered stable at this point, yet WebCore has many differences
> from the KDE 3.1 branch.
> - Our team uses a process where we require review of each change as it
> is landed, which is different from the process used in KDE.
> - A lot of work will be required to make this happen; our first
> priority is the bug fixes and features for our upcoming releases.
>
> There are probably others. I haven't tried to make an exhaustive list.
>
> There may be some way of resolving many of these issues in the long
> run, depending on how comfortable you are doing KDE development with
> the policies we use on the Safari team.
>
>      -- Darin
>
> _______________________________________________
> Khtml-devel at mail.kde.org
> http://mail.kde.org/mailman/listinfo/khtml-devel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/HejOemvcH/HdKGIRAr1hAJ9FqOo9ydIL1caZxJ6CyIm9XuvA1ACcDZ1A
P578i8WotozBSZeTtXNtLB0=
=NJT+
-----END PGP SIGNATURE-----