...

1. Deliver the end-of-expedition report to the LO (that you have been writing throughout the expedition). Post a copy to the development team via Slack. See examples from prior technical reports for formats and variations.
2. Establish with MCS, LOs, CoChiefs when the final database snapshot will be taken for EOX.
3. Circulate through the labs. What data didn’t get into the database? Provide support and training to help get the data in or find an appropriate place for it. 
4. Honor moratorium. Once content is uploaded to LIMS, and raw files have gone to data1, expedition-specific data may be cleaned off of instrument hosts and workstations. Good practice to confer with technical staff that manage this for their labs. There is variance between crews as to how these procedures are carried out.
5. Conduct end of expedition procedures for backing up the database.
6. Provide courier services if called upon to do so.
7. Confirm with the MCS what is to be included in the backup going to shore and that it does cover all the information you are aware of that should go to shore.
8. Ensure all your code changes are checked in.
9. Clean the development office. Assist in the general cleaning efforts. 
10. Be ready to move out. Your replacement will be here soon.
11. Provide assistance and information to oncoming developers.
    Assist them to accomplish their oncoming duties.
    They may not have sailed for quite a while, plan to
12. Review your changes.
13. Review the current state of the labs.
Review the current state of deployed applicationsOncoming personnel expect functional laboratory and compute systems to successfully execution of the new expedition.
Assist with those goals.

Out of Scope

These checklist items are included to raise full process awarenesssituational awareness, but are not in the responsibility of the offgoing developers. However, they are dependent on what you do. Other actors than the developers are responsible for these equally critical activities. The sooner done, the sooner accessible. Under routine circumstances we promote a two-week turn-around time for making shipboard gathered content available in shore systems.

1. Retrieve data content from tape. Distribute it to Publications, Data Librarian, DBA, Operations, and public access storage locations. - Systems
2. Restore (routinely selected) database content from the full backup to the shore production transfer schema. - DBA
3. Establish moratorium credentials and controls for the expedition data. - DBA
4. Copy the content into the publicly accessible LIMS. - DBA
5. Update the Database Overview configuration to summarize the added content. - DBA