Hi *, On Mon, Dec 29, 2008 at 2:45 PM, Jens-Heiner Rechtien <[email protected]> wrote: > [...] > CVS cloned CWSs are integrated by applying patches. It isn't that easy > and especially in this round there were a number of problems, most of > them caused by cross merges etc.
jl105 wasn't cloned, it was based on m35 and it wasn't the "current round", but integrated in m37 > So I ask you to bear with us for the moment. Getting this milestone out > of the door before x-mas was quite a heroic effort. All the effort is useless, if the result cannot be trusted, if everything has to be checked again. The whole cws based approach is a waste that way. Don't get me wrong, I understand that it is a big effort to integrate that many cws, and especially if you have to manually resolve lots of conflicts. I fully understand that in such a scenario changes of one cws might get lost if other cws touch the same files. BUT: I don't understand when whole modules are left out, when only a fraction actually gets integrated, when files that are not touched by other cws are discarded. This just isn't acceptable. I don't say that is somebody's fault. I think it is the tooling that is at fault (otherwise I couldn't explain that), but that doesn't make it any better. Same for integrating more than 40 cws in one milestone: I see that it is a major task, especially before a longer holiday. But if that milestone doesn't build (wasn't the case this time, but AFAICT took quite a while to fix the breakers), or doesn't include all the fixes that the integrated cws should bring - what is all that effort worth in the end? ciao Christian --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
