Closed ijmitch closed 9 months ago
By Merging #416, I think it created conflicts. @ijmitch Can you have a look please?
I completely agree with what you added, since I had the feeling that a first explanation of the branching with main
was missing and necessary (I just couldn't express it clearly).
@dennis-behm Are you OK to merge it into the main version? There are few things I'd like to fix in Ian's new section, but just minor things.
Looks like I was able to fix the conflict, it was a minor thing with the new sections names.
LGTM!
Thanks @ijmitch - this looks good to me!
Thanks @ijmitch - this looks good to me!
Good enough to merge? (I don't have write access.)
thanks @dennis-behm
I wish I'd recognised earlier that it's not just the accommodation of the needs of busy/sophisticated teams that's important here.
All the more frustrated with myself since it was a real client project where the need for maximum clarity and simplicity really struck home.
There is just as much need for teams whose needs are less demanding in terms of frequency and size of change. Here I am trying to define the simplest employment of the process with a new 'Starting simple' section which aims to justify that the simplest way to use this recommendation is actually the best simple scenario solution.