Revisiting Planning, Development Process, GitHub Projects

Both.

I can see the request on the issues and on the pull request page, but not on the dashboards.

Did you get notification emails for the three review requests?

No.
I have to write more to send my reply.

Perhaps a problem with github today. Earlier, I took about half an hour to create a new repo.

Github has been really buggy the last few days.

Note: when you do review, if you want to suggest a change (likely not relevant here), you can indicate that, and tie the request to a specific commit line.

I think that’s what we want.

We now have a couple of issues on the proposal review board where we already have PRs and which are clearly for the next release. Shouldn’t we remove them from the board. Most of them are tagged with a Milestone anyway. Or, at least, we could move them to another column (what about “done” or “assigned to release”?).
What do you think?

Well, we need to close the issues, and merge the PRs.

That should clearly distinguish the status; shouldn’t it?

While I can do the merges, I’m leery of doing so without sign-off from rintze and/or sebastian.

Yes, finally the issues should be closed and the PRs merged. But in the meantime, I thought it would keep the board cleaner if we get them out of the way. Just to see where we still need to discuss if they can be addressed in CSL 1.0.2 or 1.0.3 or in whatever version in the future.

Sure. We can always remove when we get these merged.