Hi,
In my opinion, this is no problem as long as these new API's don't break compatibility with the NT 5.2 API's. For example, the Vista comctl32.dll introduced many new flags and I think we can also implement them as they don't break compatibility with NT 5.2's comctl32.dll (from what I read in MSDN).
Ummm I partly disagree with that, IMHO we should not mix different versions of the WinAPI even when they do not (apparently) conflict each other. There are practical reasons, any *well* written application designed for WinXP (for example) is going to use Vista constants or flags. Should we allow this application to work on Ros when it will fail on Windows? I think this will make reactos LESS compatible with windows. Also, supporting some vista flags or not supporting them is an arbitrary decision IMHO we should have a strict rule about that or will end up having a FrankensWin :D
There are of course exceptions like the current storage stack you used as an example but I think a decision has to be made between targeting a specific windows version and update it time to time dropping older versions like NT4 (what we currently do) or target multiple versions at the same time.
I know it means more work but I see this as a strategic decision, in the future reactos can benefit from massive demand of companies moving away from old unsupported Oss like NT4 or Windows 2000 seeking a modern OS that will run their unmodified NT4 applications or drivers.