> Everyone thinks their situation is a special case or that their > source code is better written and tested than anyone else's. The > reality is that isn't true. OpenAFS is a community effort. We all > play by the same rules and we all work together to develop a better > product. Continuing attempts to pull everything into 1.4 is only > going to cause 1.4 to be 1.5 and cause everyone to be unhappy. >
I've herd this came as a surprise to some folks. It shouldn't have. Attempts to introduce anything large into an existing stable series have always been met with manifold problems, complaints from other sites who aren't interested in destabilizing influence, and besides, no one accepting code has ever said that developing patches for 1.4 with the idea that they'd go upstream on that branch first or only was a good idea; In general, when patches show up there either someone (usually me) has to do the work of merging them to the head and 1.5, or we have to send them back and ask for a revised version. The problem really is that 1.5 moved ahead from 1.4 in both client and server, and now some folks are stuck. We'll help you if you help us. But we can't do all the updating and and implementation and integration testing ourselves. Derrick
