Introduced with Arma 3 version Dev – Category talk

Dev Branch Version Tracking

Currently we have this page: DEV
With each dev version having it's own subcategory, which later gets deleted like so: -wrong parameter ("arma3dev") defined!-[[:Category:Introduced with arma3dev version 1.35|1.35]]

I'd like to propose a different system:

1. We instead have only one category specifically for the development branch, no numbering. That means anything in the dev branch and not yet in the stable branch would be tagged with it.
2. Then when features are moved into the stable branch they can simply updated to the relevant stable branch number.

This seems more efficient and also provides a centralized page of things currently not in the stable branch. --SilentSpike (talk) 19:34, 14 December 2014 (CET)

Well, this is how it was done before. Then we added in version number support. If we just say dev then we could lose track of when it was introduced. As it stands, version subcategories are easy to hide once they have been cleared of pages. It takes no more work. you simply clear the category page and add {{Delete|Reason for deletion}}. You still have a category that shows all the intro versions of pending dev features. I don't see how this is a problem. In either situation it requires the same effort. Dev branch has versions too. I don't see why we shouldnt treat it the same as stable. I would also like to add that it provides a little history on when it was first introduced. The only way I would agree is if we meet half way. We would still input version, but it would end up in one category. That way we still have one list to look at while displaying appropriate version in detail. I wish there were a way that we could display all commands in one category, but still seperate them by version.--Benargee (talk) 20:50, 14 December 2014 (CET)

I've never seen it done like that before for as long as I've been active on the biki (the good part of a year now). The arma3dev icons have only started popping up fairly recently from what I can tell and I'm not sure I agree that it's the same amount of work to continuously create and delete categories instead of having one constant one. As for your point about losing track of what dev version a change was introduced in, that happens anyway when the dev tags are updated to the stable one so it seems that isn't an issue for the current system. --SilentSpike (talk) 21:30, 14 December 2014 (CET)

There was a short period during the transition that everything was just dev, no version. It was agreed that version should be included. Category creation is a one click operation with the command template preload function. hiding categories is as simple as selecting the whole page and deleting it. As long as I am active on this wiki, I will be taking care of that department if no one else is willing to. When the day comes that I move on, then you can discuss with everybody else how it is too much effort. I am not saying that I am in charge, just saying that I got it covered. Hold that thought, I will edit the command template so that it also shows the entire list of dev commands down below. Standby.

Solution, I have modified the command template. It will show all dev commands in one category, as well as separate at the same time. Tell me what you think. I have to manually refresh each page for immediate results. Every new command page will do it instantly.--Benargee (talk) 21:53, 14 December 2014 (CET)

That's definitely useful, but I'm still not sure about the whole system that requires data to be entered and later deleted. I can live with it, just feels quite redundant. Appreciate you being flexible about it though. --SilentSpike (talk) 15:00, 16 December 2014 (CET)

Well, with categories, creation is optional. category pages dont have to exist for them to show their content. So really, we could not create them from now on to avoid having to delete them. --Benargee (talk) 16:36, 16 December 2014 (CET)