I agree with all your comments (replied before your last message).
JB didn't speak of introducing anything new before stabilizing the timeline
refactoring.
The target is then 16.08 (1 month to go) ; if this can't be achieved, we will
have to point the release to something before the great
Vincent,
hopefully you'll notice that I understand and highly appreciate what JB
is doing! So this is no bashing. My experience is that it is difficult
to iron out all the issue when *not* working on real projects. Yes, this
is inherently dangerous. I know that, and I'm willing to take some
Yes, it's this "But This Ain't Monday...!" feeling. :)
I've probably grown too lazy because with the 15.07 and 16.03 git master
cycles the timeline code was stabilizing very rapidly so I could work
without much trouble on git master. My view is that JB does a tremendous
job and the
Oh, I know _exactly_ how that feels.
Even saving often is no help, as the project looks ok, it's only when you
load it back up that the corruption becomes apparent.
I have changed my routine to be: save, then revert to last saved version.
This generally allows me to catch these timeline
The git master has some terrible issues with moving clips. I've just
lost half an hour work; have backups though. Nevertheless it is no fun
to notice severe timeline corruption only quite some time later. I've
already reported several timeline corruption issues in the past weeks.
Does anybody
