Re: is the 3.4 branch 'dead'?

Tor Norbye said:
> Not dead, just a royal pain to keep synchronized - since CVS
> does such a spectacularly bad job at it. Even after making
> just a single change in a file and doing a cvs update -jHEAD,
> I get tons of "old" changes that I have already merged.
>
> But if you want to merge the usertasks module only (and core,
> since they're dependent) that's probably good. The suggestions
> module (and related support modules) are not as important
> to merge to 3.4 since they cannot work properly on 3.4
> (javaparser cannot work with the 3.4 java module, and even
> the suggestions framework depends on changes to openide made
> only in the trunk/4.0.)

I still wonder... Am I or am I not supposed to backport the features to
the 3.4 branch? I would personally like to avoid that (since I then need
to set up two compilation environments), but if we have a userbase that
"demands" new feature in the 3.4 branch; it's worth the extra effort...

I could perhaps ask in a different way... Does anyone use the 3.4 branch?

Trond