The messy Qt-JIRA roadmap (and all those dead Qt3D versions)
-
From time to time I'm looking on the "Roadmap-page":https://bugreports.qt-project.org/browse/QTBUG#selectedTab=com.atlassian.jira.plugin.system.project:roadmap-panel&allVersions=true of the Qt-JIRA and see that numbers are changing on nearly all "versions" ...
... beside the "Qt3D ..." entriesI think it's a bit strange that those entries with milestone-dates (Qt3D 2.**) are still in there ;)
The other thing is the state of 4.8.5 and "5.0.2 vs. 5.0.3" ... if the list would be better maintained, it would be easier to understand why 4.8.5 is not yet released (or similar with 5.0.2)
-
I doubt you will reach anybody here that will be do something about that, sorry. You might want to write to the Qt development mailing list for that.
-
This is the list Tobias is referring to: http://lists.qt-project.org/mailman/listinfo/development
-
sl.sy.ifm: Yeap:-) The mailing lists, IRC and the bug report system are the ways of communication in Qt. Most developers do not care to bother with anything else. We are paid to fix bugs and not to check all over the internet for posts about Qt after all.
-
was there some general rest on forum? or did someone clean this thread? (but why? and without statement?)
After the last posts a question came up in my mind:
Is there something like a "Community Manager" in qt-project? (so someone helping to forward information from community to development and vice versa, I mean a non-developer employee of one contributing company) -
sl.sy.ifm: Check the big red banner on top of each page: There was a server problem and backups could not get restored completely.
-
thanks for the hint, I think there was none when I wrote the last post (at least I think I refreshed the main-page at that point) ...
In one of the disappeared posts I mentioned that OpenSceneGraph established linking between mailinglist and forum ... I just found some description about that: http://forum.openscenegraph.org/viewtopic.php?t=18
-
There is a community manager in Digia which e.g. runs this site.
The problem with having some mediator is that a mediator is in the middle of everything. That does not scale well. E.g. somebody could put a bug into our bugtracker based on reports in the forum. That sounds good at first, but fails in practice since the developers will request new information, etc. which has to get noticed by the middleman, forwarded to the person with the original problem, noticed by him, acted upon, forwarded to the mediator (which has to take notice again). Not even counting the loss of information that is bound to happen, this process is very fragile and slow!
As a developer I think that a problem that a user has and does not care enough about to report it is not that important in the first place. I have lots of tasks open at any given time, all of which were annoying enough for someone to actually take the time and report them... why should I check somewhere else for more stuff?
-
Hello,
Is there a simple way for us to follow Qt3D changes ?
I prefer to see devs doing what they do the best, but sure we looks around the changes :-)
I updated a few the QT3D wiki pages in order, I hope , to collect more information about the new version.
Best,
Skylar -
One way to follow changes is to follow the code review (patch submissions):
- Recently-merged patches: https://codereview.qt-project.org/#q,status:merged+project:qt/qt3d,n,z
- Patches being reviewed: https://codereview.qt-project.org/#q,status:open+project:qt/qt3d,n,z
-
Thank you !
I will add them to wiki page "Qt3D":https://qt-project.org/wiki/Category:Developing_with_Qt::Qt3D
