User:PhilippOeser/Foundation18

Warmup (December 2017)
Info

after some time not being active did some warmup in the tracker

Tracker Triaging
 * : confirmed, investigated, posted patch [made a commit -- see Master Commits]
 * : found commit causing this, posted hacky workaround, mont29 did real fix and closed
 * : found commit causing this, mont29 did real fix and closed
 * : posted solution, outcome pending
 * : confirmed, posted backtrace, still open
 * : investigated -> not reproducable
 * : confirmed, investigated, suggested workaround, real solution pending
 * : confirmed, investigated, posted patch [somewhat made a commit -- see 2.8 Commits]
 * : confirmed, investigated, shied away, but dfelinto fixed/closed
 * : raised from incomplete to confirmed, investigated, found cause, lijenstina did fix and closed
 * : investigated, asked for more info, closed later (see Week 1)

Master Commits
 * Fix T53639: text sequence strips no stamped into render

2.8 Commits
 * patch that 'Fix T53647: Outliner crashes when active object is deleted' was based on

Week 1 (January 2nd - 5th)
Info

spend time mostly triaging/investigating tracker reports. Also looked into running tests for 2.79a release

Tracker Triaging
 * : triaged incomplete, suggested solution, closed later (see Week 2)
 * : triaged incomplete (missing info), closed later (see Week 2)
 * : triaged incomplete, suggested solution, closed later (see Week 2)
 * : triaged incomplete (not reproducable), response pending
 * : investigated, still have to discuss with mont29, pending
 * : confirmed, investigated, posted patch [made a commit -- see Master Commits]
 * : closed as invalid (not a bug), posted solution
 * : confirmed, investigated (tbc in Week 2)
 * : triaged normal, investigated, solution pending
 * : confirmed, but triaged invalid (2.8 report)
 * : confirmed, assigned mont29 (fbx)
 * : confirmed, investigated a bit, brecht claimed
 * : triaged normal, investigated, solution pending
 * : triaged normal, solution pending
 * : confirmed, investigated, solution pending
 * : confirmed, investigated, solution pending
 * : marked as todo, solution pending
 * : triaged incomplete (not reproducable), response pending
 * : triaged low, posted workaround, reporter closed as resolved
 * : triaged incomplete (expected behaviour), no response, closed later (see Week 2)
 * : triaged invalid (not a bug per se), suggested/posted workaround
 * : triaged incomplete (missing info), closed later (see Week 2)
 * : triaged invalid (2.8 report)
 * : closed (more than a week without reply)
 * : reopened (some information was given), but asked for even more info, closed later (see Week 2)
 * : confirmed, investigated a bit, solution peding
 * : triaged incomplete, suggested solution, reporter closed as resolved
 * : triaged incomplete, response, then closed as invalid (not a bug)
 * : closed as duplicate of
 * : confirmed, investigated, assigned sergey, sergey did fix and closed
 * : investigated, asked campbell, he closed as todo
 * : investigated, closed as invalid (windows internal problem)
 * : triaged normal, solution pending

Master Commits
 * Fix T53650: remove hard limits on force field size and max distance

Week 2 (January 8th - 12th)
Info

spend time mostly triaging/investigating tracker reports. Had to refresh blender-deps and enabled them for some reports (alembic,...) Also tried to investigate some of the pending solutions more in depth [only limited success]

Tracker Triaging
 * : confirmed, investigated, solution pending
 * : confirmed, campbell investigated and closed as invalid (corrupt input file)
 * : triaged incomplete (missing info), response pending
 * : closed (graphics driver bug)
 * : confirmed, assigned sybren (alembic), solution pending
 * : reopened (could confirm the issue), assigned sybren (alembic), solution pending
 * : confirmed, assigned sybren (alembic), solution pending
 * : closed (more than a week without reply)
 * : closed (more than a week without reply)
 * : closed (more than a week without reply)
 * : triaged incomplete (missing info), response pending
 * : [LONG] confirmed, investigated, solution pending
 * : confirmed, campbell moved to todo
 * : confirmed, tested provided patch, bjornmose commited and closed
 * : assigned sergey (cycles), brecht fixed and closed
 * : assigned aligorith, solution pending
 * : confirmed, assigned campbell, he closed as todo
 * : triaged incomplete (graphics driver issue), response pending
 * : investigated (cannot reproduce), added Windows tag
 * : triaged incomplete (file renders fine here), response pending
 * : investigated, found commit causing this, assigned campbell, he fixed and closed
 * : investigated, closed as invalid (not a bug)
 * : investigated, suggested patch [made a commit -- see Master Commits], but WARNING / OOPS: there are issues with it and should be reverted for now...
 * : moved to todo (not a bug per se), but want to discuss with campbell also
 * : triaged incomplete (missing info), response pending
 * : closed/archived (graphics driver bug and no response)
 * : investigated more, got closer, but this was a time-sink also..., gave up and assigned campbell for now
 * : triaged incomplete (caused by addon, which one? response pending)
 * : triaged incomplete (missing info), response pending
 * : confirmed, solution pending
 * : investigated, suggested workaround
 * : closed (more than a week without reply)
 * : closed (more than a week without reply)
 * : closed (more than a week without reply)

Master Commits
 * Fix T53752: Draw curve fails w/ stylus WARNING / OOPS: there are issues with it and should be reverted for now...

Next Week

I'd really like to spend more time on actually fixing (pending previous but also older bugs), but priority will still be triaging what's incoming/already there... Also need to make entries in the wiki TODO for the things I marked as TODO

Week 3 (January 15th - 19th)
Info

More time was spent on reading code and trying to fix bugs myself [with limited success in the timespan of 1hr / report...]. Most of the time I hopped on tho other reports if I hit that timelimit (marked by '[LONG]'). Had a day off on tuesday but made up for this on Saturday. Summary: involved in 30 reports, 4 longer investigations

Tracker Triaging
 * : [LONG] investigated, solution halfway there...
 * : confirmed, solution pending
 * : assigned to sergey, he closed
 * : confirmed, some investigation, solution pending
 * : [LONG] some investigation, asked campbell, he fixed and closed
 * : invesigated, not reproducable
 * : investigated, assigned mont29, he fixed and closed
 * : investigated, not a bug, suggested solution, reporter then closed
 * : checked, was already fixed in master
 * : checked, suggested 'nota bug', brecht as well and closed
 * : closed (more than a week without reply)
 * : [LONG] dived into dupli(group) code but 1hr was not enough to find cause/solution yet...
 * : closed (3rd party addon)
 * : investifated, assigend mont29, solution pending / is TODO
 * : closed after short investigation (not a bug)
 * : confirmed, made crash-preventing patch, assigned campbell who fixed and closed
 * : made sure every information is there, brecht took over (OSX issue)
 * : investigated, moderated, bastien/campbell decided to remove old version
 * : too little info, no response after suggestions, closed
 * : claimed (py API addition), pending
 * : closed, spam
 * : invesigated, assigned (but will likely fix myself if still enough time)
 * : invesigated, assigned, howardt already had this TODO in another task and closed
 * : closed (more than a week without reply)
 * : closed (more than a week without reply)
 * : some more investigation (testing different file)
 * : confirmed, assigned
 * : investigated code, found cause, assigned sergey, pending
 * : investigated, but missing information
 * : [LONG] investigating custom normals code, assigned mont29 in the who closed as invalid (known limitation)

Next Week

General rate of incoming reports leaves about 4-5hrs [out of 20] of longer investigations [diving deeper in code] for selected reports. I have a couple of these still with pending results. Try to finish these off while still keeping the priority of handling incoming (new) reports.

Week 4 (January 22nd - 26th)
Info

Still struggeling to get to good results investigating certain reports when constraining to 1-1.5hrs max (which is a good limit though to get other stuff done)

Summary: involved in 37 reports, 4 longer investigations, 3 master commits

Tracker Triaging
 * : [LONG] investigated, found cause, assigned sergey
 * : investigated, suggested patch, mont29 committed similar [somewhat made a commit -- see Master Commits]
 * : checked, couldnt reproduce
 * : confirmed, suggested patch, assigned campbell who fixed differently
 * : assigned luciorossi who closed as invalid
 * : [LONG] investigation, hit time limit, move on...
 * : incomplete report, asked for specific info, closed later (no answer)
 * : investigated, suggested solution, talked to lijenstina et.al, [committed -- see Master Commits]
 * : closed spam
 * : closed spam
 * : triaged incomplete suggested something to try, no answer yet
 * : triaged incomplete suggested something to try, no answer yet
 * : added similar reports
 * : investigated, suggested fix, talked to nBurn [committed -- see Master Commits]
 * : closed (more than a week without reply)
 * : closed (more than a week without reply)
 * : closed (more than a week without reply)
 * : closed (more than a week without reply)
 * : [LONG] more investigations, got closer to cause but hit time limit, asked brecht/sergey instead
 * : first incomplete, after more information: confirmed, assigned sybren
 * : checked, was already fixed in master
 * : checked, assigned luciorossi who closed as invalid
 * : checked, involved campbell, probably todo rather then bug
 * : confirmed, brecht resolved (tradeoff simple vs complex scene)
 * : confirmed, assigned nexyon
 * : confirmed, assigned nexyon
 * : checked, assigned mont29 who fixed
 * : [LONGISH] more a todo, but had a closer look at view code, no real result yet
 * : confirmed, brecht closed as duplicate
 * : discussing the report, no real solution yet
 * : closed spam
 * : checked, not reproducable, external addon? yes
 * : marked incomplete
 * : checked code closely, assigned aligorith
 * : no bug but todo, suggested workaround
 * : closed (more than a week without reply)
 * : closed (more than a week without reply)

Master Commits


 * Fix T53841: Can not import .obj or .fbx generated from Marvelous Designer
 * fix T53624: A.N.T. Landscape should not be operating in edit mode
 * fix T53766: MeasureIt measurements not appearing on all layers an object exists on

Week 14 (April 2nd - 6th)
Info

Most time spent triaging incoming reports, also took a first round of looking at older open/untriaged reports. Summary: involved in 46 reports

Tracker Triaging
 * : sugested better python usage, crash involved needs confirmation still
 * : confirmed, claimed, looked at code a bit, but postponed
 * : no real bug, but asked @severin as well, not closed yet
 * : confirmed, not solved yet
 * : cannot reproduce, special hardware, needs triage still
 * : investigated, asked for more information (no answer, later closed)
 * : investigated, suggested to try it the right way (no answer, later closed)
 * : asked reporter to try stuff, he then could resolve
 * : investigated, found cause and workaround but not solution, assigned brecht
 * : investigated, clarified, mont29 closed then
 * : investigated, could not reproduce, user could resolve, closed then
 * : investigated, suggested workaround, user happy, still need proper code fix
 * : incomplete, no answer (closed later)
 * : confirmed, assigned @aligorith, solution pending
 * : assigned @akitula, solution pending
 * : suggested workaround, assigned @severin, solution pending
 * : checked, couldnt reproduce, but archived (as is 2.8 report)
 * : added information given in IRC
 * : confirmed, claimed, but not high prio atm
 * : checked, suggested better .blend but closed as not a bug
 * : incomplete, asked for info, user could resolve, closed then
 * : confirmed, also checked suggested patch, campbell did real fix
 * : investigated, found causing commit, assigned @severin, solution pending
 * : investigated, claimed, suggested patch, review pending
 * : investigated, suggested better/correct usage, closed as not a bug
 * : investigated, claimed, solution pending
 * : confirmed, @blendify fixed later
 * : checked, found user error, closed as not a bug
 * : investigated, asked for more information, Tamito Kajiyama took over later and closed as duplicate
 * : closed (more than a week without reply)
 * : closed (more than a week without reply)
 * : closed (factory startup fixed issue in report)
 * : needs triage again (user provided more info since incomplete triage)
 * : closed as resolved (user feedback suggested issue is gone)
 * : closed as resolved (user feedback suggested issue is gone)
 * : closed as resolved (user feedback suggested issue is gone)
 * : investigated, could not reproduce, solution pending
 * : closed as invalid (external addon)
 * : checked, could not reproduce, no answer, @lijenstina closed later
 * : confirmed, claimed, will look into it later
 * : triaged incomplete, @lijenstina closed later
 * : needs triage again (user provided more info since incomplete triage)
 * : closed as not a bug (with explanation to reporter what the misunderstanding was)
 * : closed as archived (was on TODO already)
 * : investigated, suggested code change, mont29 commited and closed later
 * : investigated, suggested code change, mont29 commited and closed later

Week 15 (April 9th - 13th)
Info

continued with triaging incomming reports, some more cleanup in older reports Summary: involved in 34 reports, 1 master commit

Tracker Triaging
 * : incomplete, asked for more info, no answer, closed later
 * : investigated, clarified, claimed for the time being, solution pending
 * : investigated, suggested substitution of code to @campbellbarton,solution pending
 * : investigated, found code cause, assigned @campbellbarton, solution pending
 * : investigated, found (user) cause, suggested better usage, closed as not a bug
 * : investigated, explained cause in detail, mont29 then closed as not a bug
 * : investigated, made patch [committed -- see Master Commits]
 * : investigated, explained cause in detail, then closed as not a bug
 * : [LONG] investigated in detail, archived as 'known bug, won't fix in 2.7x, will be fixed in 2.8'
 * : first incomplete, but user could verify it was caused by external addon, closed then
 * : confirmed, found relating issues, possibly fixed now, will need to recheck
 * : confirmed, detailed report, assigned @howardt, solution pending
 * : [LONGISH] confirmed, found causing commit, assigned @campbelbarton in the end
 * : investigated, closed as feature request
 * : investigated, closed as already fixed in master
 * : [LONGISH] investigated, suggested possible patch workaround, but no easy fix, @sergey closed as TODO
 * : closed (more than a week without reply)
 * : closed (more than a week without reply)
 * : closed (more than a week without reply)
 * : closed (more than a week without reply)
 * : needs triage again (user provided more info since incomplete triage)
 * : needs triage again (user provided more info since incomplete triage)
 * : incomplete, asked for more information
 * : needs triage again (user provided more info since incomplete triage)
 * : needs triage again (user provided more info since incomplete triage)
 * : closed (wasnt closed though issue seems resolved)
 * : investigated, explained somewhat hidden reason, closed as not a bug
 * : investigated, found causing commit, assigned @campbellbarton, solution pending (though fix might be in already)
 * : [LONGISH] investigated, but dont think this is a bug, asked@sergey, solution pending
 * : [LONGISH] investigated, confirmed, also confirmed user provided patch, solution pending
 * : [LONGISH] investigated, confirmed, found causing commit, assigned @nBurn (who fixed and closed)
 * : [LONGISH] investigated, confirmed, assigned @sergey in the end
 * : investigated, detailed report, asked @campbellbarton for advice, solution pending
 * : investigated, detailed report, assigned @campbellbarton (who fixed and closed)

Master Commits
 * fix T54549: Vector Transform node in wrong nodeclass

Week 16 (April 16th - 20th)
Info

continued with triaging incomming reports, some more cleanup in older reports Summary: involved in 48 reports, 1 master commit

Tracker Triaging
 * : closed, was resolved by user actually
 * : closed (more than a week without reply)
 * : closed (after some of my investigation mont29 then also asked sergey and this will be solved by 2.8 CoW)
 * : closed (checked, and was also resolved by a previous campbellbarton commit)
 * : closed (checked, and was also resolved by a previous campbellbarton commit)
 * : closed (checked, and was also resolved by a previous campbellbarton commit)
 * : closed (2.8 report)
 * : investigated, then closed as duplicate
 * : investigated in some depth (UI code), claimed, but solution pending
 * : investigated in some depth (bmesh op), claimed, but solution pending
 * : investigated, was corrupted UVs, no answer how these were imported/generated, closed later
 * : investigated, confirmed and claimed, solution pending [might as well be corrupt .lwo] but needs another look
 * : investigated, closed as archived, suggested workaround [cycles terminator issue]
 * : confirmed with some further investigation, assigened to sergey (busy)
 * : confirmed, assigned campbellbarton (undo rewrite), might have another look myself if time permits
 * : closed (feature request)
 * : triaged incomplete, no answer, lijestina closed later
 * : triaged incomplete, example file came a lot later, needs triage now actually
 * : investigated but is a limitation of alembic, added to TODO
 * : confirmed (though similar report existed), assigned sergey but he archived as not a bug
 * : confirmed (surface deform modifier violating modifier stack), assigned lucarood, but no answer yet (might also have a go at it)
 * : mixed report (user error which I explained) and graphics glitches (which I marked incomplete, no answer, lijenstina closed later)
 * : was fixed already, but Chaosgroup didnt update their version of our addon, closed
 * : second part of report was valid, comited fix (see master commits)
 * : archived (design of scale manipulator), redirected to 2.8 design task
 * : confirmed, found causing commit, assigned campbell, solution pending [could also look into it]
 * : [LONGISH] interesting problem that boils down to have py access to renderings etc, claimed as TODO
 * : could not reproduce, but newest blender version also solved it for user apparently, closed
 * : closed (not a bug, there are options to control this already)
 * : confirmed and claimed, but solution pending, needs a second look
 * : not a valid report, closed later
 * : more of a question about 2.8, closed
 * : fancy hardware, asked for more information
 * : confirmed and claimed for the time being [needs a second thourough look later]
 * : cannot reproduce, even after second answer
 * : closed, 2.8 report
 * : marked incomplete, no answer, lijenstina closed later
 * : more of a TODO, but claimed, no patch yet though
 * : older report, one suggestion was there, but no answer anymore... closed later
 * : closed (more than a week without reply)
 * : closed (more than a week without reply)
 * : needs triage again (user provided more info since incomplete triage)
 * : confirmed and claimed, simple fix will do later
 * : more a TODO, but claimed (sergey approved to work on it), patch follows (needs some cleanup still)
 * : cannot reproduce, marked incomplete, lijenstina closed later due to no answer
 * : [LONGISH] investigation, claimed, but no solution yet
 * : confirmed, assigned campbell (undo refactor)

Master Commits
 * Material Library VX: fix error when clearing category

Week 17 (April 23rd - 27th)
Info

continued with triaging incomming reports, some more cleanup in older reports. Also gathered a couple of claimed reports now that I also prepared some patches for. Next week I want to push some of these. Untriaged reports are down from 70 to around 40 now, some remaining are a bit fuzzy, but these also have to go down next week...

Tracker Triaging

Will provide info in a more compressed form from now on, going over every report again seems more timeconsuming than its benifits justify.

Summary: involved in 38 reports, 3 master commits

Master Commits
 * Fix T54789: A Simple Typo in the "Node Wrangler" Addon
 * Fix T54803: Materials Library VX: follow strict class naming
 * Fix discontinuity in default UVs for a torus

Week 18 (April 30th - May 4th)
Info

continued with triaging incomming reports, some more cleanup in older reports. Also going over claimed reports now.

Tracker Triaging

Will provide info in a more compressed form from now on, going over every report again seems more timeconsuming than its benifits justify.

Summary: involved in XXX (havent counted yet) reports, 1 master commit

Master Commits
 * Fix T54341: Particle Instance Modifier doesn't preserve edge datas

Week 19 (May 7th - May 11th)
Info

continued with triaging incomming reports, some more cleanup in older reports. Also going over claimed reports now.

Tracker Triaging

Will provide info in a more compressed form from now on, going over every report again seems more timeconsuming than its benifits justify. Summary: involved in XXX (havent counted yet) reports, 5 master commits

Master Commits Influence vertexgroup into account
 * Fix T54324: remove stencil entries from weight paint keymap
 * Fix T54525: crash when setting number of frames to use between dupoff frames
 * Fix Movieclip editors 'graph' and 'dopesheet' view using themes region background setting
 * Fix T54997: simple typo in property description
 * Fix T54992: Lattice modifier on another Lattice object does not take the

Week 20 (May 14th - May 18th)
Info

continued with triaging incomming reports, some more cleanup in older reports. Also going over claimed reports now.

Tracker Triaging

Will provide info in a more compressed form from now on, going over every report again seems more timeconsuming than its benifits justify. Summary: involved in XXX (havent counted yet) reports, 2 master commits

Master Commits
 * Fix T55065: lipSynch Importer not handling relative file paths correctly
 * Fix T55115: crash when iterating SmokeDomainSettings color_grid property through python

Week 21 (May 21st - May 25th)
Info

continued with triaging incomming reports, some more cleanup in older reports. Also going over claimed reports now.

Note: one public holiday, also took one day off

Tracker Triaging

Will provide info in a more compressed form from now on, going over every report again seems more timeconsuming than its benifits justify. Summary: involved in XXX (havent counted yet) reports, 3 master commits

Master Commits
 * Fix T54336: Extend property of Lasso select tool in Node editor does not work
 * Fix Extend property of Lasso select tool in Mask editor not working
 * Fix T55034: Setting duplication group for multiple selected items only affects one item

Week 22 (May 28st - June 1st)
Info

continued with triaging incomming reports, some more cleanup in older reports. Also going over claimed reports now. Also started porting old wiki over to new wiki (see T48096) and started looking into porting over the TODO list to phabricator.

Tracker Triaging

Will provide info in a more compressed form from now on, going over every report again seems more timeconsuming than its benifits justify. Summary: involved in XXX (havent counted yet) reports