Blender Features Request Tracker with bugs
There is char about
bug tracking
.
code.blender.org/2019/12/tracker-curfew/
Want suggest to publish for each new version blender some stats about resolved bugs and implemented features with priority status. I think that this can be more clear about situation around development of this software on release notes on splash screen.
Kiss kiss : )
5 Comments
I am not following you there.
Isn't it what release notes do already? Aside from the priority.
Unless you mean a report about ongoing unresolved bugs and features being worked on? But that's basically the entire tracker .
A more digestible page could be more user-friendly but that seems quite overkill for me, and the user-friendly news covering on development seems already well covered by code.blender.org and Pablo's Blender Today live streams and the "Blender <version> New Features in LESS than Five Minutes" series on Blender's official Youtube
Or maybe you just want raw stats? Like "128 bug fixes in this release and three new features" ? But I don't know how valuable this information would be...
Totally not as on my links. What is problem with stats as pure numbers by priority? It's helping to chose about upgrade or not to new version, etc.
Resolved Bugs:CriticalNormalImplemented Features++ chart
It's due that many ideas from RCS are very old. Don't know - it's more bugs or features?
Are you implying that you chose to upgrade your software depending on the numbers of bugs fixes and new features? Not for the features and the fixed bug themselves? That makes no sense to me.
It's have sense, coz new versions often not working with old addons, and giving new other bugs that are not disclosed yet.. even other can be solved but maybe not so important.
Last time I talk with some pro around 3d in big company. I ask.. why you not use blender more in company with rest topics - coz bugs, and costing time. Ask about this same around bugs in 3dmax, maya, rhinoceros (in case it use cycles, etc.). I know.. open source, bugs.. but... final productions versions and quality is different. I'm critical about this all around road map, priority etc..
Forgive my high doubts, but in which context someone will look at those numbers to decide whether it's interesting to implement Blender in a pipeline? These numbers vary for tons of reason that have nothing to do with a release's stability or ability to comply with a company's needs.
The amount of bugfix and features in a version means nothing. What matters is what got fixed or implemented, and how .
Any pro from any company can tell anything they want, only a few people actually know on which basis a software is implemented or not in a pipeline. And the biggest reason why is simply that it costs too much to change a pipeline. No amounts of bugfixes and new features will change that. When you have a company that have thousands of employees and have developed a functional pipeline around some specific tools for decades, you just can't switch tools around whenever you feel like it, it costs money and time and very few softwares can justify such an investment.
Many companies do use Blender, but the only ones that do use it at the core of their pipeline are companies that were created very recently, like Tangent. Other ones keep it as a sidekick that has no impact on the pipeline, and some people just use it mainly for quick works. Do any of these companies consider switching their pipeline softwares? No, because what they have just works, and any change means breaking efficiency and schedules for months or years.
The "big company" i work at uses Blender for animators to edit reference footage, and some modelers sometimes throw an FBX in it to make a quick UV pass on a lightweight model and bounce it back off to the actual pipeline. That's it. Nobody cares about how many bugs are fixed or new features are implemented. No company in the world update their core pipeline software every three months. My company just updated their Maya to 2015 version, and plan to have 2018 used on every of their projects by 2023. Have they ever considered switching to any other software? No, because the current pipeline works.