Closed antis81 closed 11 years ago
scunz
commented
11 years ago @antis81, you should probably merge this intermediate state here. Without this change, the development branch won't compile...
Any thoughts on how we could track such dependencies better? I think it happened a few times now that we totally did agree that something was ready without realizing that it got dependencies.
antis81
commented
11 years ago Upsi, ok. That's actually a hard :chestnut: and really a problem, yeah. At least the tool chain will prevent a direct merge. For the moment, we could use mail notification from jenkins.
What I'd wish for is a "task-branch", which is "automagically" generated on each dependent module. That's something I'm really missing in Git also, but currently only a dream :cloud:. Let's say, we want to setup a new task, where we can select affected modules (and add / remove some later). On these, a branch is generated on a certain commit. Afterwards we could decide to either completely or partly merge back. That would be great.
But currently, I don't have any good idea how to reliable solve this. We could setup subtasks like
... but an automatic check would be far better :smile:.
Currently only minor adjustments, but more to come ...