BetaWiki:Guidelines: Difference between revisions

m
Tag: 2017 source edit
Tag: 2017 source edit
Line 245: Line 245:
In case there are several known builds with the same build number but from different labs, names of the pages should contain the lab name. To maintain a degree of consistency, the reduced name without a lab should be used for a disambiguation between the individual builds. If there are several known builds with the same build number that come from the same lab (i.e. are distinguished by the build date and time only), add the full timestamp to the lab component, i.e. <code>Windows Longhorn build 4050 (private/lab06_demo.031019-1809)</code>.
In case there are several known builds with the same build number but from different labs, names of the pages should contain the lab name. To maintain a degree of consistency, the reduced name without a lab should be used for a disambiguation between the individual builds. If there are several known builds with the same build number that come from the same lab (i.e. are distinguished by the build date and time only), add the full timestamp to the lab component, i.e. <code>Windows Longhorn build 4050 (private/lab06_demo.031019-1809)</code>.


For Windows versions that just used a major and a minor version number, use them in the version field and omit the buildnumber completely, i.e. <code>Windows 1.04</code>.
For Windows versions that only use a major and a minor version number, make use of them in the version field and omit the build number entirely, i.e. <code>Windows 1.04</code>.


Don't mention the full update name for builds of Windows 10 updates, just use a plain numeral 10, i.e.: <code>Windows 10 build 16179</code>. On the other side, it's encouraged to make separate build listings for the individual updates, whose names should contain the official name of the update, i.e.: <code>Windows 10 Creators Update</code>. The YYMM update version should redirect to the full name, for example <code>Windows 10 v1703</code> would redirect to the Creators Update mentioned before.
Don't mention the full update name for builds of Windows 10 updates, just use a plain numeral 10, i.e.: <code>Windows 10 build 16179</code>. On the other side, it's encouraged to make separate build listings for the individual updates, whose names should contain the official name of the update, i.e.: <code>Windows 10 Creators Update</code>. The YYMM update version should redirect to the full name, for example <code>Windows 10 v1703</code> would redirect to the Creators Update mentioned before.
Cookies help us deliver our services. By using our services, you agree to our use of cookies.