en Copyright 2015 Java http://172.16.0.5:8080/history/wasmtime-44.0.1/docs/contributing-development-process.md#7dbcf4c1 Clarify merge etiquette in Wasmtime (#12408)Document that we typically expect maintainers themselves to add theirown PRs to the merge queue after approval, but clarify that forcontributors this is a responsibility of maintainers to add PRs to themerge queue. List of files: /wasmtime-44.0.1/docs/contributing-development-process.md Tue, 27 Jan 2026 02:07:04 +0000 Alex Crichton <alex@alexcrichton.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/docs/contributing-development-process.md#69fecf4e Add contributor docs about our RFC process (#11349)We have some off-hand links to particular RFCs in our docs, but did not have anygeneral information about our usage of the RFC process. I've added thatinformation in this commit. List of files: /wasmtime-44.0.1/docs/contributing-development-process.md Wed, 30 Jul 2025 18:25:38 +0000 Nick Fitzgerald <fitzgen@gmail.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/docs/contributing-development-process.md#bb2ae7cd chore: Add issue triage process to contributing docs (#10152) List of files: /wasmtime-44.0.1/docs/contributing-development-process.md Wed, 29 Jan 2025 22:09:44 +0000 Oscar Spencer <oscar.spen@gmail.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/docs/contributing-development-process.md#e9ecab49 Clarify rebasing/merging guidelines in docs (#9931)Indicate that a rebase is required if there's a merge conflict or CIissues for example. Inspired by discussion on #9897 List of files: /wasmtime-44.0.1/docs/contributing-development-process.md Mon, 06 Jan 2025 16:49:21 +0000 Alex Crichton <alex@alexcrichton.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/docs/contributing-development-process.md#4d5eaea6 Update PR template and dev process docs (#6158)Overall, I'm just trying to make these bits of documentation reflect ourprocess as it stands today. There are some specific changes I want todraw attention to though.Asking new contributors to pick a reviewer is a waste of time for tworeasons: Only people with write access to the repository are allowed topick reviewers, and new contributors have no idea who would be a goodreviewer for their PR anyway. So I'm deleting all mention of that. Wenow auto-assign reviewers instead.By the time someone is opening a PR, asking them to open an issue justmakes extra work for everyone. They've already picked an approachwithout discussing it; we might as well look at what they did. We maythen have to ask them to take a different approach, but at that point,asking them to open an issue won't save them any effort.I removed mention of tests from the pull request template. There aremany things we'd like to see in a PR, and we may have to ask for themduring review if the contributor doesn't follow our development processdocumentation. But I think the only crucial information for starting areview is the two questions I'm leaving in the template: why do you wantthis, and where can I find more context?The code of conduct link still had the branch name as `master`, which isa hint at how long it's been since anyone reviewed it. List of files: /wasmtime-44.0.1/docs/contributing-development-process.md Wed, 05 Apr 2023 20:47:02 +0000 Jamey Sharp <jsharp@fastly.com> http://172.16.0.5:8080/history/wasmtime-44.0.1/docs/contributing-development-process.md#986f9f79 Merge the CONTRIBUTING.md files List of files: /wasmtime-44.0.1/docs/contributing-development-process.md Tue, 25 Feb 2020 19:48:03 +0000 Alex Crichton <alex@alexcrichton.com>