v50 Steam/Premium information for editors
- v50 information can now be added to pages in the main namespace. v0.47 information can still be found in the DF2014 namespace. See here for more details on the new versioning policy.
- Use this page to report any issues related to the migration.
This notice may be cached—the current version can be found here.
Difference between revisions of "Category talk:Version 0.28.181.40d"
Jump to navigation
Jump to search
m |
|||
| Line 2: | Line 2: | ||
:It might be useful for things specific to this particular version. It might also become more relevant when a new version becomes available... --[[User:Corona688|Corona688]] 18:37, 6 July 2009 (UTC) | :It might be useful for things specific to this particular version. It might also become more relevant when a new version becomes available... --[[User:Corona688|Corona688]] 18:37, 6 July 2009 (UTC) | ||
: Unless a new version fork from the main branche of development, I don't see the point either. Since this wiki is always reflecting the latest stable release. --[[User:Karl|Karl]] 18:49, 6 July 2009 (UTC) | : Unless a new version fork from the main branche of development, I don't see the point either. Since this wiki is always reflecting the latest stable release. --[[User:Karl|Karl]] 18:49, 6 July 2009 (UTC) | ||
| + | ::When .41a or .42a or whatever comes out then this category becomes a list of things that need to be rechecked. As soon as a new version is it, then the wiki is no longer reflecting the latest stable release and needs a lot of review to be brought up to date. The point of these categories is to help streamline that process when it comes about. The correct usage is as follows: | ||
| + | ::-When writing information that you suspect will change in a future release, tag it with <nowiki>{{subst:current}}</nowiki>. | ||
| + | ::-When the future release comes out, look at things in the outdated categories to see if they have actually changed. | ||
| + | ::[[User:VengefulDonut|VengefulDonut]] 14:12, 7 July 2009 (UTC) | ||
Revision as of 14:12, 7 July 2009
Is this category really necessary? I mean, unless the articles say otherwise, they already talk about how things currently are, so do we need an entire category devoted to telling readers that the article is, indeed, saying how things are? It's redundancy incarnate. If there's changes for .40d#, then they can be put in their own category. Otherwise, virtually every single line of pretty much every single article currently on the wiki would belong in this category. --LegacyCWAL 18:17, 6 July 2009 (UTC)
- It might be useful for things specific to this particular version. It might also become more relevant when a new version becomes available... --Corona688 18:37, 6 July 2009 (UTC)
- Unless a new version fork from the main branche of development, I don't see the point either. Since this wiki is always reflecting the latest stable release. --Karl 18:49, 6 July 2009 (UTC)
- When .41a or .42a or whatever comes out then this category becomes a list of things that need to be rechecked. As soon as a new version is it, then the wiki is no longer reflecting the latest stable release and needs a lot of review to be brought up to date. The point of these categories is to help streamline that process when it comes about. The correct usage is as follows:
- -When writing information that you suspect will change in a future release, tag it with {{subst:current}}.
- -When the future release comes out, look at things in the outdated categories to see if they have actually changed.
- VengefulDonut 14:12, 7 July 2009 (UTC)