Le mercredi 25 juin 2014, 23:01:19 Vincent PINON a écrit :
> as we work openly and with few manpower, "master" branch remained
> unusable during several month twice last years (and so rolling packages
> like the ones from dev PPA or Arch).
> how could we enforce the "work in a branch" rule, balancing with the
> need for help and visibility (testers => packages)?
We keep receiving bugs or forum entries against "latest git" (crash, odd
behavior...), this because "master" branch is still GLSL work that I can't fix
& maintain (my GPU support for OpenGL 3.1 is buggy, and so many changes
occured that I couldn't follow)...
I'm about to ask KDE sysadmins to move "master" to a "GLSL" branch (work in
progress) and put back the branch from v0.9.8 ('next")...
just like last year for the "refactoring" branch :-(
This will break the git base for people still working on "master" and
unfortunately drop some unrelated works (I tried to cherry-pick as much as
possible).
If you are against this move, please raise your finger quickly (24h?).
And please from now on work in branches as long as your code is not usable by
testers. Test it a bit on your side, and also on a 2nd PC or by someone else
before merging?
------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
_______________________________________________
Kdenlive-devel mailing list
Kdenlive-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kdenlive-devel
