Hi again,
On 6/27/05, Eric Hoch <[EMAIL PROTECTED]> wrote:
> > For the record, Patrick has done this for the 1.1.x tree. It is
> > called cws_macjoin1153 and I downloaded it this weekend and will
>
> Eric Bachard has already done parts of this work. So it would be
> good if you contact him so that work isn't done twice.
>
> Since 1.1.5 is currently not on any roadmap for the next future I
> would not focus too much on this but a surprise cannot be excluded.
> With 2.0 and 1.1.5 the 1.1.x Codeline is more or obsolete only be
> needed for a 1.4.2 Neo/J Officerelease and Neo/J source code has
> the patches are already integrated or not? Sorry I don't know
> this.
Ah well, the different priorities.
What NO/J is interested in is a _stable_ OO X11 with as few bugs as
possible, so that the NO/J additions can be stabilized and the bugs in
them are easier to find. That stable OO is the 1.1.x branch. OO 2.0
will not be bug-free or entirely stable even when it's released. It
becomes relatively good around 2.0.1 or 2.0.2 or something like that.
And before 2.0.2, the better choice for NO/J is the latest of 1.1.x
-branch.
So 1.1.x is NOT obsolete. It becomes obsolete when there are only
handful of _users_ using it. And that will take several years. For an
example, just look at Apache web server usage stats (the different
versions).
It's ok, if people want to develop and test the latest HEAD-branch,
but there are many people who prefer stability&less bugs instead of
newest features.
At least from reading Pavel's blog OO 1.1.5 is going to happen sometime.
So, at least in my thinking, the best path forward is to first
integrate the stuff in macjoin1153 to OO 1.1.x branch and then check
which ones are still relevant and applicable to OO 2.0. That way fixes
are not lost in any branch.
> Much more interesting is the integration of the fixes into 2.0
> sources. Here we have to take a look and see if Patricks patches,
> ported to 2.0, are of any help for 2.0 and prevent double work.
> Here we should take a closer look. But this isn't easy and here any
> help is welcomed. Here you could do code comparison.
This is, obviously, what is priority for you. I would, however,
encourage spending some time to work also on first integrating
macjoin1153 to OO 1.1.x branch. This makes it easier to understand
what the changes are and whether they are relevant to OO 2.0.
Just my 2c, again,
Mox
--
Mox on G
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
