Hi Sebastien!
I see at least one reason: avoiding regressions, as an user I think these are really annoying. It's more work for the developers but git helps here.
This is always difficult to decide. I don't think we will ever be able to merge a branch without creating regression but we have to check if those regressions are major and if they affect lots of people. With the git plugin for example, I feel it is ok to if we have all the major operations supported even if we lack one or the other feature from 2.32 for now. The main reason is that even our unstable releases don't get a lot of testing and the branches nearly don't get any testing at all. If we want to deliver a stable release we have to check that the important changes have been in master for at least some months. Another reason now is that I want to have the basic user-interface of 3.0 ready before the hackfest in december because that is our only chance to create useful documentation and to find usability problems.
Anyway, I will try to merge the newproject branch this week as I think the basic functionality are here. And I need to merge it soon if we want to have it in the next release.
That would be great. Sorry that I didn't get around having a look at that branch yet. Regards, Johannes
Attachment:
signature.asc
Description: This is a digitally signed message part