You get a bonus - 1 coin for daily activity. Now you have 1 coin

Flag Day in Programming

Lecture



A flag day, as used in system administration, is a change that requires a complete restart or conversion of a significant body of software or data. The change is large and expensive, and—in the event of failure—is also difficult and costly to undo.

The situation can arise when there are limits on the backward compatibility and forward compatibility between components of a system, which then requires that updates be performed almost simultaneously (during a «flag day cutover») in order for the system to function after the update. This contrasts with the method of gradual, phased upgrading, which avoids the interruption of service caused by en masse updates.

This system terminology arose from a major change to the ASCII definition of the Multics operating system, which was scheduled for the U.S. holiday Flag Day, June 14, 1966.

Another historic flag day was January 1, 1983, when the ARPANET switched from NCP to the TCP/IP protocol suite. This major change required shutting down and restarting all ARPANET nodes and interfaces across the entire network.

See also

  • Bug compatibility, backward compatibility with known defects
  • Compatibility mode
  • [[b9176]]
  • Computer compatibility
  • Deprecation
  • Downgrade attack
  • Emulator
  • Legacy mode
  • Shim (computing)
  • Software regression
  • Vendor lock-in

See also

Comments

To leave a comment

If you have any suggestion, idea, thanks or comment, feel free to write. We really value feedback and are glad to hear your opinion.
To reply

Lectures and tutorial on "Software and information systems development"

Terms: Software and information systems development