--- This was an email sent out to the guys on 5/5/20 ---

Hey guys,
Good afternoon. We are in the process of moving some servers from Newtek over to Hostek (different server/hosting companies). As part of this move, we need to get all custom files into the main master code branch. Below are some of our requirements and requests for code and branches.

1. Please gather up any and all custom files that are stable and put them into one branch. This may require you to go on to servers and grab the latest and greatest code from the live sources. This is a giant custom code round-up. We will then merge your custom update branch in with master. We need these files before 3 pm on Monday, May 11th. I have a 2 hour window where we will be merging in any files that are not part of the master branch but should be. This is not a code sign-off party, it is more of a merge what already exists type party. Bring your own chips and soda :). I’ll be on the GoToMeeting session from 3pm to 5pm to help merge in code and get master up to date with all custom files.
	a. We need all custom files even old ones. These include: images, logos, watermarks, black box files, custom code, labels, forms, etc.

Alan and I wanted to setup some general guidelines for code and branches. Once we get master up to date, we want to keep it that way.

- One project per branch - try doing less on each branch
- For big projects, schedule and do mini sign-off’s along the way
- All files need to be part of master - regardless
- For quickies… (labels, images, logos, watermarks, black box files, and other custom stuff) – let Alan know and he will merge them in.
	o You are responsible for getting them on to the correct server, we will just help you merge them in (keep the file list going)
- Anything that deals with core logic or core files needs to go through a full sign-off process with Brandon or Alan. If you have questions on core, ask.
- Anything custom needs to be part of master – this is different than what it used to be. We want everything to be part of master.
- Length of the projects… if it has been weeks, we need to reverse merge in current master files (try to bring your older branch up to speed with any new changes). This helps speed up the merge process. Try to get older files as close to possible with what is currently part of master
	o Where possible, lets get projects merged as soon as possible. Push daily. Shoot for a week or less between merges unless you are on a big one. Things get really outdated if branches sit for weeks and months. Try to help eliminate the burden of bringing older code up to the newest levels. If needs be, we can show you how to pull the latest master code and then add your changes on top of that.

Last but not least, Alan is willing to help with preliminary sign-off’s. How this works is you get with Alan via email or text and let him know what branch or pull request needs review. Before he goes in, he would like a small summary paragraph (tell him what the project is and/or does – briefly). He will go in and do a code review and provide comments inside of bit bucket. These may be questions, suggestions, style, flow stuff, or general overview. Once all is well, he can either sign off with you or you can schedule some time with Brandon. This process will be done as Alan has time and doesn’t require an actual face to face meeting. That could really help in a lot of situations. Once again, think of this as a preliminary sign-off and/or a prep step. We are trying to ease the burden of code sign-off.

If you physically need time, for testing, questions, help, or whatever… schedule it with Brandon (in the adilas shop) and we’ll get you the help you need. We are trying to standardize and stabilize things as much as possible. Thanks guys and more good things to come.

Stay healthy, happy, and enjoy the journey. Yee haw!