Closed KYovchevski closed 3 months ago
Would've been nice to have had that review in the past week that it was open, and not right after it was merged. I am being put on a different project starting Monday and this was my last chance to wrap this up.
Would've been nice to have had that review in the past week that it was open, and not right after it was merged.
A merge is a nice way to bump an MR to the top of my notification/TODO list, and hence get it looked at.
I also don't know how to solve this better going forward other than better educating the team (on both writer and reviewer side) to learn about the ins and outs of doc-comments... Including how to build-test and read them, and having CI complaining about invalid constructs.
What thought has gone into releasing 0.3.1
instead of 0.4.0
? From what I can see there were breaking changes, such as:
R8g8...
-> Rg8
rename;enum
type renames;Image
;https://github.com/Traverse-Research/ispc-downsampler/compare/0.3.0...main
Let's do a 0.4.0
release as we indeed have breaking changes since the previous release 😄.
Should we also fix https://github.com/Traverse-Research/ispc-downsampler/pull/54#pullrequestreview-2104445560?