naming convention

About this tag
The naming convention tag on WindowsForum.com covers discussions about how Microsoft and other software vendors label their products and updates. A key topic is Microsoft's shift from seasonal Windows update names like "Fall Creators Update" to a clearer H1/H2 designation, driven by the need for global inclusivity. The tag also touches on technical naming conventions such as the 8.3 naming convention in Windows, which can affect Office on Demand functionality when disabled. Additionally, version control practices like GitFlow and repository layout conventions are discussed, reflecting broader naming and organizational standards in software development. These threads explore how naming choices impact usability, compatibility, and enterprise IT management.
  1. Microsoft’s Shift to Clear, Inclusive Windows Naming: From Seasons to H1/H2

    Microsoft’s journey to a clear, inclusive, and universally logical Windows version naming convention has been less straightforward than many users might realize. After years of bewildering and, at times, geographically exclusive update names like “Anniversary Update,” “Fall Creators Update,” and...
  2. GitFlow for Visual Studio

    I know, I know... I've been highlighting a number of Git related extensions recently. And I know all of YOU are using Git already (just like I am... um... errr.... um... kind of... yeah). Okay, fine, so I'm a Git noob. Right now Git continues to gain support, mindshare and seems to one of those...
  3. You cannot start the Office on Demand application when the 8.3 naming convention is disabled in Wind

    Link Removed