And since Samba 3.3.x will work with Windows 7, there should be some development and testing to adapt and adopt Samba 3.3.x or 3.4.x prior to RedHat>CentOS doing so. There is good incentive to do so.
well.. a good incentive, IMHO, is a BIG money amount to the developers or, if you prefer, your time to test the migration to samba 3.3/3.4.. naturally you should then mantain all the samba packages for SME because many, many (thousands) users would rely on them..
SME will never compile/rebuild any package because:
- there are no human resources to do
- it's designed with stability in mind, exactly as CentOS/RH.. RH will never be a bleeding edge distro
you/we just have to wait that upstream source gives us the right rpms
so, I repeat, if you wish samba 3.3/3.4 on your server to use windows 7
- do it yourself and share the results
- or pay someone to do it for you
- or change Server/Client OS
windows XP is pretty stable now, about 8 years from its release.. what make you think that windows 7 will be stable since its release?
another question: do you use SME in a enterprise or just at home? in the first case, do you really think to move in a short time your client pc to windows 7? for what? what's the pro?
finally, as broken compatibility is for sure a windows 7 issue and not a samba one, I suggest you to write to M$ to ask the reason why it doesn't work.. does windows 7 join a windows 2k domain? maybe not, I don't know, but I wouldn't be surprised if you need at least windows 2003 server to use windows 7
Stefano