Bugtracker category Raytracing is now obsolete or mis-named since RenderWB has superceded it

Post by **Kunda1** » Wed Dec 02, 2020 11:42 am

So Raytracing WB was deprecated in favor of Render WB. We still have a bugtracker category called 'Raytracing'. How should we proceed?
We rename it?
Deprecate it?
Close all tickets and move them to the Github RenderWB repo?

howetuft wrote: pinged by pinger macro

yorik wrote: pinged by pinger macro

howetuft · Post by **howetuft** » Thu Dec 03, 2020 9:51 pm

AFAIC, I would vote for renaming it into Render... It would be a convenient way to collect bugs, we can reference it in Render's Readme!

Post by **Kunda1** » Thu Dec 03, 2020 11:04 pm

You would prefer mantis to github tickets?
It is technically an external workbench

Post by **yorik** » Fri Dec 04, 2020 11:53 am

Besides, Raytracing bug/features likely won't translate "as is" to Render..
I'll have a look there and try to migrate or close what is possible

howetuft · Post by **howetuft** » Sat Dec 05, 2020 6:57 am

@Kunda1 After a bit of thinking: yes, you must be right, one entry point, in Github, might be more readable for user.
I agree with @Yorik's triage approach, I will join my efforts.

Bugtracker category Raytracing is now obsolete or mis-named since RenderWB has superceded it

Bugtracker category Raytracing is now obsolete or mis-named since RenderWB has superceded it

Re: Bugtracker category Raytracing is now obsolete or mis-named since RenderWB has superceded it

Re: Bugtracker category Raytracing is now obsolete or mis-named since RenderWB has superceded it

Re: Bugtracker category Raytracing is now obsolete or mis-named since RenderWB has superceded it

Re: Bugtracker category Raytracing is now obsolete or mis-named since RenderWB has superceded it