Page 1 of 1

Merging approved changes

Posted: Thu Nov 19, 2015 3:22 pm
by alex.barylski
Been a while since I posted - figured I'd through this out there to hear others experiences, suggestions, etc...

I am part of a small team of 3-4 developers. We host on GH using private repos. I am the primary DM/QA/BA/etc.

Despite our limited automated tests - I still need to manually go over the application to ensure it meets (what I understand) basic requirements. Hitherto, I have requested that devs send me patch files of the changes they made. I then apply these changes to my local copy, test, valid and in some cases demo. Once satisfied with result, I apply the patch/migrations, etc to the production server.

This works OK. I typically have the patches associated to tasks in Trello - and can pull them out and keep a communication/change history very easily.

We have considered having each patch pushed to GH perhaps as a complete branch, but I have not heard a compelling enough argument to do so, as of yet. So thats what brings me here, what says you???

Regards,
Alex

Re: Merging approved changes

Posted: Thu Nov 19, 2015 3:44 pm
by Celauran
What's your work flow like? Feature branches + pull requests sound like they'd work here.

Re: Merging approved changes

Posted: Fri Nov 20, 2015 3:45 pm
by Christopher
Hey Alex!

After reading your post, I was left wondering what the actual problem is? Is it the patches? testing the patches? or rolling out the patches?