Aurora 4x
VB6 Aurora => Wiki Discussion => Topic started by: Erik L on August 19, 2014, 12:44:12 PM
-
As it sits currently, each 0.0x update results in a new version. This can rapidly get unwieldy. I was thinking of limiting the versioning on the wiki to the 0.x updates which are database updates.
Thoughts?
-
I agree. The little changes can be annotated in the affected articles themselves as it has been done until now, and I don't think too many people play old versions if they can update without loosing their game.
-
I agree. The little changes can be annotated in the affected articles themselves as it has been done until now, and I don't think too many people play old versions if they can update without loosing their game.
That's pretty much my thinking on it too.
-
In dwarf fortress, namespaces are limited to each major release.
How are the versions organized for Aurora? Are there incompatible changes between minor versions like 6. 42 and 6. 43 that prevent someone from changing versions or any major differences them?
I did the initial versions based on the versions listed on the wiki page that warranted a Release Note.
-
In dwarf fortress, namespaces are limited to each major release.
How are the versions organized for Aurora? Are there incompatible changes between minor versions like 6. 42 and 6. 43 that prevent someone from changing versions or any major differences them?
I did the initial versions based on the versions listed on the wiki page that warranted a Release Note.
X.00 are major releases with usually fundamental changes to the game. This requires a game restart.
0.X0 are database/executable releases. This requires a game restart.
0.0X are executable releases. Usually bug fixes or changes that don't require a database change. Saves from previous 0.X0 releases are compatible.
I'd say have the versions on the X.00 and 0.X0 versions.
-
Still, how do I assign a version to a page? Also the template does not show any versions, just that it is outdated.
-
I sent mail to Erik. Some variables need to be updated and the wiki reloaded to define the namespaces before they can be used.
-
X. 00 are major releases with usually fundamental changes to the game. This requires a game restart.
0. X0 are database/executable releases. This requires a game restart.
0. 0X are executable releases. Usually bug fixes or changes that don't require a database change. Saves from previous 0. X0 releases are compatible.
I'd say have the versions on the X. 00 and 0. X0 versions.
Great. That works out. I actually suggest just the latest 0. XX release. So the namespace would 6. 4X while the actual version strings displayed about be 6. 43 (dictated by current/version and ArticleVersion). 6. 43 version string would update with the version but the namespace itself remains 6. 4X.
-
So, what is needed to make the versioning work? On the DF wiki all pages have a version prefix and and are moved to a version category.
Is that all there is needed, and does someone maybe have a tool to move the pages automated instead of manually going through?
-
I don't know the wiki tools. It sounds plausible there is one.
hxxp: www. bay12forums. com/smf/index. php?topic=139631. 0 suggests there is a copying phase that does get done.
hxxp: dwarffortresswiki. org/index. php/Dwarf_Fortress_Wiki:Versions#Redirects has more templates used that describe how new pages are created
hxxp: dwarffortresswiki. org/index. php/Dwarf_Fortress_Wiki:DF2014_migration has directions on wiki page management during a migration
hxxp: dwarffortresswiki. org/index. php/Dwarf_Fortress_Wiki_talk:Namespace_migration mentions existing problems for the DF2014 migration
Until the {{NAMESPACE}} var works in the versioned pages, ArticleVersion won't work. You can verify it by creating a versioned page and previewing {{NAMESPACE}}. ArticleVersion contains the names of the namespaces we want.
-
Currently there are two namespaces in use, Aurorawiki and Examples (I think). Aurorawiki is where all of the pages are that we are concerned with. Examples contains all of the ship examples that were put up ages ago.
The versioning uses 5.50, 6.00, 6.40 and Current_Version. There are namespaces created for those. So pages need to be moved into the namespaces for the appropriate version.
So let's assume the next two versions are 6.50 and 7.0. When 6.50 comes out, everything in Current_Version gets moved into 6.40. When 7.0 comes out, a new namespace of 6.50 is created and all Current_Version moves into that namespace leaving Current_Version for 7.0.
Minor versions such as 6.43 or 6.42 live in Current_Version with the exception of something in 6.43 overriding something in 6.42.
-
Can somebody create those namespaces? I really don't know how to do it, or if I even can, and I'd like to redo the missile article, but here the old info really shouldn't get lost as it changed so much.
Unrelated thing, in the category overview there are an enormous amount of template categories with one entry and seeming no use, can they be deleted?
-
Only with edit access to localsettings.php.
-
Okay then I will have to wait.
-
Is anything happening with the versioning?
-
I've been swamped with the "real" job. I'll have to go back and figure out what has been done and what needs to be done to get it working.