Chris Biscardi

`get_issues_and_prs` gets all PRs since the origin date, which is going to be roughly `0..1`'s date. That set of PRs is what is [is checked](https://github.com/bevyengine/bevy-website/blob/4576f6b1fc4f4f66c9e063734fcbe2af688a986e/generate-release/src/helpers.rs#L48) so any PR opened before...

related to this, we should probably add an example of how we'd expect people to add things like colliders to the right locations relating to the tilemap/tile positioning.

Sounds like we should document answers to: 1. Is TileVisible required, or would Bevy's builtin Visibility suffice. [I asked](https://canary.discord.com/channels/691052431525675048/692572690833473578/1323096406524956673) in #engine-dev about Visibility and if its intended use was a...

seems like 0.16 is going to improve relationships (and perf) as well: https://github.com/bevyengine/bevy/pull/17398

Relationships have merged, so I think one question here for 0.16 is now "is ChildOf/Children" the right relationship to use. The despawn_recursive behavior is opt-in for the new generic relationships...

yeah, not requiring Transform makes sense to me.

Since people are trying things for the hierarchy-related comments here, its worth noting that if you (the reader) are going to explore changes to hierarchy, etc then the primary next...

confirmed the behavior described here. haven't looked into cause yet though. Toggling visibility on the tile shows it is always in the expected location. https://github.com/user-attachments/assets/8728d017-298a-4a4e-bdbd-413273eb60c8

I think deferred_rendering is broken too ``` 2024-10-01T19:43:15.414646Z INFO bevy_diagnostic::system_information_diagnostics_plugin::internal: SystemInfo { os: "Windows 11 Pro", kernel: "22631", cpu: "AMD Ryzen 9 7950X 16-Core Processor", core_count: "16", memory: "63.2 GiB"...

Alternatively, or in the meantime, manually constructing namespaces like in https://github.com/typst/typst/issues/7121 works. All my bibliography entries are now prefixed with `bib:`