[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [sc-dev] call-backs, co-routines and inversion of control

On 11.01.2013, at 12:10, Jonatan Liljedahl <lijon@xxxxxxxxxxxx> wrote:

> Well, if s.bind changes to always synching at the end, and it didn't
> before, then it's a change in behavior that might break peoples code.
> I haven't studied the code or your patch in detail so I don't really
> know if this is the case or not.

Ah, didn't think of this. Well if this is the only issue, we can change this easily.

> However, using branches or keeping track of them are not hard.
> git branch - shows a list of your branches
> git checkout <the_branch> - switch to the branch

You also have to keep the branch up to date with master. If someone else starts working on the same thing, you get conflicts you have to resolve. Then you also need to build the branch and run it on a day to day basis in order to find problems

This is something more than two or three people should do, I think.

> Anyone interested in this particular feature would check out the
> branch while developing it into finished state, then people can test
> it, then it can be merged back into master. Another good thing with
> this approach is that the merge back can be compressed into one or a
> few commits, instead of having half-finished work spread out over
> multiple commits, making it hard to backtrack in case of discovered
> bugs or regressions, etc.

It would be good, I just doubt that this is what would be happening now. Maybe I'm too pessimistic, but it seems to me that currently, the branch would just stay untouched and untested.

sc-dev mailing list

info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: https://listarc.bham.ac.uk/marchives/sc-dev/
search: https://listarc.bham.ac.uk/lists/sc-dev/search/