Skip to contentSkip to conversation

Linux 2.4.35 tree abandoned/delayed?

DISCUSSION Tony Borras 2 participants 2 messages Jul 17, 2007 1 message not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw

I did get the current 'pre' set of 2.4.35 (circa early June) patches and applied to 2.4.34.5. After fixing a goto mislable in one of the patches (dont remember if it was one of the patch-2.4.34.? or patch-2.4.35.pre5), managed to build a vmlinuz-2.4.35 successfully.

Just wondered whether to expect an abandonded tree, in which case I will fly with this 2.4.35 build or should wait for its eventual release.

Thanks Greg!

Tony Borras

There are 10 types of people in this world, those that read binary and those who don't!

--
__ __ _ I N C. http://www.sysdev.org

/ __|\\// __||  \  __   __          /         [email protected]
\__ \ \/\__ \||)|/ O_)\/ /        \/  System Tools / Utilities
|___/ || ___/|_ /\___|\_/        WIntel / Linux Device Drivers
#2 lore raw

Hi Tony,

Quoted 5 lines · Tony Borras

I did get the current 'pre' set of 2.4.35 (circa early June) patches and applied to 2.4.34.5. After fixing a goto mislable in one of the patches (dont remember if it was one of the patch-2.4.34.? or patch-2.4.35.pre5), managed to build a vmlinuz-2.4.35 successfully.

could you please report what the problem was, in case it's not fixed yet ?

Quoted 3 lines

Just wondered whether to expect an abandonded tree, in which case I will fly with this 2.4.35 build or should wait for its eventual release.

No it's not abandonned at all !!!

The difficulty with 2.4 is to get user feedback on patches. While in 2.6, there are hundreds or thousands of testers for every release, in 2.4, I have to wait longer after every release in order to start collecting problem reports, or confirmation of fixes. People using it in production generally cannot reboot a machine in the evening just to try a patch. Also, subsystem maintainers have less time to spend on it and are themselves slowed down by the slow feedback process.

That's merely why I maintain a parallel 2.4.34.X stable branch. I thought I could release one version every 6 months, but I think that this delay will probably slightly increase after 2.4.35, we'll see.

I still have a few patches to merge, and I expect to be able to work on them next week-end, then release -rc1, which I expect to be the only -rc before -final (which will probably not be true as in every -rc).

Thanks,
Willy