apache-2.0

[Dean Gaudet <dg...@arctic.org>]

I really hate to be anal about this, but it's already out of date.  And
I'm not planning on maintaining the 2.0 tree at the moment because there
are just too many outstanding 1.3 things.  Someone is going to have to
track changes that go into 1.3... like I'm still tracking critical changes
for 1.2. 

I don't think Brian put any tags into apache-1.3 to indicate when the
split occured... I suggest someone applying the commits I made last night
after the branch, and then tagging apache-1.3 with APACHE_2_0_SPLIT, and
APACHE_2_0_LAST_MERGE. 

Going forward you can use cvs patch to generate a patch between
_LAST_MERGE and HEAD, and apply that to the 2.0 tree, then advance the
_LAST_MERGE tag. 

Dean

Re: apache-2.0

[Marc Slemko <ma...@worldgate.com>]

On Tue, 27 Jan 1998, Dean Gaudet wrote:

> I really hate to be anal about this, but it's already out of date.  And
> I'm not planning on maintaining the 2.0 tree at the moment because there
> are just too many outstanding 1.3 things.  Someone is going to have to
> track changes that go into 1.3... like I'm still tracking critical changes
> for 1.2. 

We are not yet committed to the 2.0 repository.  Moving apachen to -1.3 is
a good thing and should have been done before apachen was made.

I really do think that keeping the tree for 2.0 is a good idea.  There is
a lot of code in there that is worthwhile.  Change historys are very
useful.  2.0 will not be a complete rewrite of anything except perhaps
large parts of the core and, of course, modules as people decide they want
to.  Unless someone can show me the programmers hiding around...

While it is true that we can accomplish 10x more coding on 2.0 in a month
than we have on 1.1-1.3, there are limits.


> 
> I don't think Brian put any tags into apache-1.3 to indicate when the
> split occured... I suggest someone applying the commits I made last night
> after the branch, and then tagging apache-1.3 with APACHE_2_0_SPLIT, and
> APACHE_2_0_LAST_MERGE. 
> 
> Going forward you can use cvs patch to generate a patch between
> _LAST_MERGE and HEAD, and apply that to the 2.0 tree, then advance the
> _LAST_MERGE tag. 
> 
> Dean
> 
>