From: Paul Eggleton [mailto:firstname.lastname@example.org]
Sent: Friday, July 06, 2012 4:23 AM
To: Stewart, David C
On Thursday 05 July 2012 23:00:17 Stewart, David C wrote:
Guys - I'm really struggling with this overall concept of concurrency.The key word there I think is "experiment". Is it reasonable to expect to
It implies that if Paul and I are sharing the same project and I make
a change to a .bb file to experiment with something (assuming we have
the ability to do that, refer to my last email) and my change breaks
my build, it will break everyone else's build as well. But the beauty
thing is that it breaks it silently, because the configuration
silently changed for everyone on the project.
handle people making experimental changes to something that others are
relying upon? It seems to me that whether experimental changes are likely
and whether or not it will seriously impact other users depends on what
development stage the particular project is at.
Whether it is reasonable or not, if it's possible for people to shoot themselves in the foot, they will. Even with safety guards on a circular saw, I have seen people routinely disable them, so there you go.
How about a strongly visible warning on the Projects page that simultaneous user changes will affect all users of the project's files? How about an asynchronous notification to users on the main screen that some files have changed since their last build (and maybe list them).
Again, writing a user story is what I'm looking for. I would do it myself, but I'm still struggling. :-)