| Thread Previous • Date Previous • Date Next • Thread Next |
Hi Egor, hope you had a nice holiday!
Just back from holiday. Will check Hannes's zoom as soon as I'm done stuffing the washing machine with smelly clothes ;-)
Looking forward to your comments (on the branch more rather than the laundry :-))
Having said that, good to hear there's a branch we can all contribute to.Is it OK if I start incorporating the wheel mouse changes? I'll add the stuff I'm most confident about first...
Hmm, I don't know, if it's a good idea to put more changes into this particular branch. The problem I see is that we can't merge the branch as long as there are still bugs in any one of the new features in the branch. Meaning that for example with this branch (branch_marc) there are (at least) two new features (the progress bar/ timing and the painting on and creation of slides). If, for example, we get the progress bar perfected quickly, but have trouble figuring something out with the painting, neither feature will find it's way into the trunk quickly. I would propose a model where we open a new branch for every feature, so that we can merge it with the trunk as soon as it's ready. We can create branches owned by the JessyInk team for all features, so everybody will be able to commit to them.
If you create a branch for the mouse wheel changes that you are confident about, we could merge them quickly into the trunk.
Let me know what you think of this workflow. We can certainly adapt it, if you think a different model works better in our current situation.
Cheers, Hannes
| Thread Previous • Date Previous • Date Next • Thread Next |
