Mark the 6.x-3.x branch as recommended

As written in irc i personally wouldn't do that, because this might add a bunch of additional cost both on the site-maintainers side and on the issue queue maintaining side.

The problem is that many contribs seem not working with views 3, while other have already abandonned the support of Views 2.

Any way to get both working simultaneously?

It's totally possible, but module authors would need to be aware of the differences and code around it. I don't imagine that many of them will want to go through the effort. :(

I mean having 2 Views modules enabled on the same install, one for 2 and one for 3.
But I can answer myself: it would need Views 3 not being an upgrade of Views 2, but a separate module, renaming the module itself and most its functions... and the contribs would have to be aware.
Maybe a good idea for such a breaking upgrade of a module would be to allow the new module to coexist with the old one. This would make the upgrade path much less stressful, inducing a much faster adoption rate of the new one.

Well if you have your views exported into code, nearly everything works, see #1090098: pager settings lost for all views when updating from 6.x-2.9 to 3.0-alpha3 for more information. So you should definitive do that.

About the upgrade from d6 to d7, that's a bit more complicated. The changed table structure of d7 core is respected, and some of the views will be converted somehow on the fly, though there is a big big problem with the upgrade path of cck to fieldapi. That's something views itself can't provide, but cck could in theory. Unfortunately noone with enough knowledge of both views and cck
found the time to develop that update path, though it definitive should be possible at least on a basic level (80%).

Hi

>dawehner
you tell about exported views into code : so it mean i need to export my views 2 version then import them into views 3 to convert them ?

No you can export the views to code and load them directly from there. Probably using features is the easiest way to do that.

http://drupal.org/project/features will probably explain you that.

ok because i just try to import views 2 code into views 3 and it seem to work...perhaps all cases aren't like that..

adding new blocker issue