Re: [AD] Merged in 4.1.17 into new_api_branch

[Evert Glebbeek <eglebbk@xxxxxxxxxx>]

On Thursday 09 December 2004 00:41, Elias Pschernig wrote:
> Ah, nice work. I'm really wondering how well the transition from 4.1
> to 4.3 will work out - it isn't too far away if all goes as planned.
> Ideally we'd just swap back the new_api_branch and continue with a
> single branch in 4.3. Another route would be to leave new_api_branch
> as the place for experimental stuff, and only extract back parts into
> the current WIP as needed - but I somehow feel that approach would
> require more maintenance. And personally, I would rather avoid having to
> do things like merging changes between branches with CVS :P

I think we should fork off 4.2 when it becomes stable, similar to how 4.0 
was forked off, then replace mainline with the contentx of new_api_branch 
and then close down (at least for now) new_api_branch.
In fact, I was even contemplating wether or not it would be a good idea to 
do the flip before that time and split off 4.2 before its release date. 
The idea behind this that I'd like to get the stuff into mainline before 
Peter's time becomes too limited again (I think he said he would have a 
busier semester after Januari/Februari?). On the whole, I don't think this 
would be a good idea in general though.

> [Oh, and since you and Grzegorz both overlooked it in that other thread
> - could you temporarily give Tomasu access to CVS for the makedoc stuff?
> It's not a real problem since he's in #allegro most of the time and can
> dcc changes, but still might be useful..]

What is the problem exactly...? I couldn't see any way to only grant acces 
for a specific module... besides, isn't Thomas already on the list of 
developers?

Evert