Make it sense to create tags there also include blender as a part of the tag e.g
blender-2.67
Is not be easier/more DRY to create only tags for the version number like 2. 67 because we are here in the blender stack exchange.
What you think?
$\begingroup$
$\endgroup$
2
-
$\begingroup$ Hey! You guys are talking about me! I did that! $\endgroup$– DanielCommented May 22, 2013 at 22:28
-
1$\begingroup$ We're don't talk about you but about the future of the version tags. You were only the initiator of the question. :D $\endgroup$– Azd325Commented May 22, 2013 at 22:47
Add a comment
|
4 Answers
$\begingroup$
$\endgroup$
10
I propose that there be two (maybe three) levels of specificity. For instance:
- blender-1 vs blender-2 (likely will rarely be used, if at all)
- blender-2.4 vs blender-2.6 (huge changes in interface, inner structure, etc)
- blender-2.66 vs blender-2.67 (new features present in one version and not earlier versions)
I would say that when tagging a question, the more general, the better. For example, if you can do the same thing in 2.4 as in 2.6, then it makes little sense to tag as 2.67. Perhaps we could also use tags such as blender-2.4+ for questions where an answer exists in 2.4 and up as a way of clarifying that the question isn't about 2.4 only, so answers in 2.6 would be fine as well.
One thing's for certain though: there is no use in having a blender tag. It adds no value to any question. I'm currently a mod on Christianity.SE and the tag "christianity" doesn't exist because there's no point in having it.
-
2$\begingroup$ The problem with this is that you will have many many tags. $\endgroup$– PhoneixSCommented May 22, 2013 at 21:58
-
3$\begingroup$ @PhoneixS: It's better to have many specific tags than a few too-broad tags. $\endgroup$ Commented May 22, 2013 at 21:59
-
$\begingroup$ Yes, if we will have version tags, they must be for specific version (2.66). And thinking again about it, well, there isn't so many new releases. $\endgroup$– PhoneixSCommented May 22, 2013 at 22:03
-
1$\begingroup$ The site is about Blender, let the questions specify the version. $\endgroup$– iKlsRCommented May 22, 2013 at 22:08
-
1$\begingroup$ I agree. Must be specific version tags. This matters a lot when talking about bugs. $\endgroup$– DanielCommented May 22, 2013 at 22:31
-
1$\begingroup$ I agree that
blendershould not be a valid tag within the scope of this forum. $\endgroup$– Mike PanCommented May 22, 2013 at 23:53 -
$\begingroup$ Should we just shorten it to
2.67instead ofblender-2.67? $\endgroup$– DanielCommented May 23, 2013 at 0:44 -
$\begingroup$ @DantheMan: There is potential for confusion that way. After all, Cycles, Yafaray, and other programs also have their own version numbers. $\endgroup$ Commented May 23, 2013 at 0:56
-
-
4$\begingroup$ Having version tags has worked well for us on Ask Ubuntu. Sometimes there are issues and questions specific to a single version, and it is useful to separate these out with a tag. $\endgroup$ Commented May 23, 2013 at 2:43
$\begingroup$
$\endgroup$
1
I'd encourage the use of either a blender prefix or a version prefix in order to make it clear what it is that number refers to. It might be obvious to many but the clarity would be improved even if it's less DRY.
$\begingroup$
$\endgroup$
4
I think we should only have one tag, something like versions or builds, which would be used for questions relating to different versions of blender.
Some examples of existing questions which could use this tag:
Mesh appears normal in solid mode but looks weird in textured mode
Blender release life cycle and versioning
Such a tag could also be used for upgrade questions such as this one:
Is there a way to update Blender without deleting it and downloading the new version?
This might be a stretch, but this question might also be eligible for such a tag:
Working with VRML 1.0 files in the current version of Blender
I feel that having many tags for specific releases of blender is overkill when most questions are only related to the current version, but there are enough questions that are related to versions of blender that such a tag could make sense.
-
$\begingroup$ Blender versions are actually stable builds for the most part. I say one tag is enough, the
buildstag should cover any of these questions.versionsis a very vague version of what OP and El'endia Starman suggested. $\endgroup$– iKlsR ModCommented Sep 21, 2013 at 1:58 -
$\begingroup$ @iKlsR They could be synonimized, but I think it would be good to at least have a prompt for whatever tag we use if a user starts typing
versionsorreleases$\endgroup$– gandalf3Commented Sep 21, 2013 at 2:04 -
1$\begingroup$ Good note, I will make this so. $\endgroup$– iKlsR ModCommented Sep 21, 2013 at 2:08
-
$\begingroup$ The problem with doing this for questions about different versions is that, as time goes on, a build that was up-to-date will become out-of-date, and a build that was beta will become the release-- but nobody will constantly update tags of all questions. $\endgroup$– NathanCommented Dec 3, 2021 at 23:25
$\begingroup$
$\endgroup$
5
This would be extremely messy, if such a tag were to exist, it would be one set tag such as blender and that alone. If a question is tied to a specific version it can be specified in the question and or answer.
That being said, I am against such a tag as it would make little if any sense or even be of any use as the site is about Blender and presumably and preferably, the questions will be too.
-
1$\begingroup$ I agree, keep it simple and tag with only blender $\endgroup$ Commented May 22, 2013 at 21:47
-
1$\begingroup$ Seconded. Having version-specific tags is too messy. $\endgroup$– Mike PanCommented May 22, 2013 at 22:18
-
1$\begingroup$ @iKlsR: I'm not sure if you're arguing for or against a plain blender tag. Can you clarify? $\endgroup$ Commented May 22, 2013 at 22:25
-
$\begingroup$ @El'endiaStarman The first paragraph I was evaluating what could happen if one were to be used and the second I clearly say why it makes no sense. I have edited it to be a bit clearer. $\endgroup$– iKlsRCommented May 22, 2013 at 22:26
-