For many cases in the future many different versions will have different ways of doing things. To avoid confusion, we’d need some way to signal the version of Mojo/MAX/Magic the post was written for. And maybe add an option similar to Airflow’s (and many other’s) documentation page, where the whole website can be changed to target a certain version.
1 Like
I see where you’re going with this and I do think a proper solution is in necessary.
In the meantime, a tag in someone’s code would be helpful though that has it’s own problems i.e. how to type greater than or equal to is not known by most people.
#mojo > 24.5 Is that 24.6 then?
#mojo ≥ 24.5 is more informative but again, it’s not easy. (I ended up finding it on the net as U+2265)
Yes that seems like an ok solution for now. Though I’d argue people are quite used to just writing # mojo = ">=24.5,<24.6" since it’s the format for dependency declaration
1 Like
I’ll bring it up with @Caroline and the moderators
how do we feel about using a tag on the topic? i.e. 24_5 for 24.5
I feel like that would lead to inconsistency for people asking debugging questions (tagging would be a silent standard/convention and we’d need to remind people at every step) or for questions and examples that may translate to a range of versions.
Also I think adding an option to search by version will allow indexing posts based on that, which is very useful for SEO and for the internal search engine. For example, I wrote a how-to iterate a list using SIMD which is valid for mojo <= 24.5 but if the PR where I’m introducing an iterator which does that behind the scenes is merged before next stable I’d need to write another post which is for mojo >= 24.6; if a user searches “how to iterate over a list using SIMD in mojo 24.4” since no post has the tag the result would probably prioritize newer posts, which is no problem if you have 2 posts but I’m not sure how that scales in the long term.
I know this is a pretty big ask because it will require quite some refactoring, but I think it’s very much worth it. I’ve used the feature of looking for the documentation for a specific version in many documentation websites and it makes a huge difference that their versioning is so indexable. I often have problems with stack-overflow results because the questions or answers are for different API versions that are ahead or behind what I’m using.
The version range should be editable by other people, maybe only moderators. But not everyone will come back and fix their example/question and set until what version it’s valid.
1 Like
We have the ability to require one tag from a tag group on every post – so I can create a tag group for release numbers, and require folks to use one on all posts. Thoughts?
Oooh, I like that. Is that constrained by category so for Mojo and Max that seems like it would work nicely or is that any post at all will require a tag??
It’s constrained by category so it’s pretty configurable
1 Like
This topic was automatically closed 12 hours after the last reply. New replies are no longer allowed.