Merge V2.1 into main and tag as V2.1.0

[micromouseonline]

Effectively makes the V2.1 boards the current 'main' branch.

There are a lot of changes and so expect conflicts. These may be difficult to resolve with KiCAD. I suggest we allow the incoming to override anything already there.

We will need to tag a release upon completion.

The great thing about Pull Requests is they can be revised and even rejected if things do not work out.

Resolves #77

[micromouseonline]

Wow - no conflicts. I am inmpressed.

Note that one of the options is to squash and merge.

[paulbuzzby]

I'll save hitting the merge button until tomorrow but that is good about no conflicts. I am yet to add the RAPID fields but this is still a good test

[micromouseonline]

Try an experiment. Since you have rwite access to the repo, you should be able to pull the V2.1 branch, make your change and push it back up. Since that branch is part of a PR, you changes should be incorporated.

Thus, only when there is agreement on the state of the PR branch, we can do the merge. Subsequent changes will then be done with the mini-bracnches as discussed.
This repo is currently private so the rules requiring multiple reviewers cannot be applied. I think that constraint goes away once it is public.

[paulbuzzby]

I just pushed a small change to the chassis board as there are 2 RSONLINE options. I wouldn't have thought it would get included in this PR but lets see

[micromouseonline]

Perfect. That is how it will work. Anyone with write access to the repo can edit/update the PR until it gets merged in.

I am assuming Ian sees these messages.

A risk, until we go public, is that one of the other contributors bypasses the rules. After going public, we can apply restrictions.

At some point, anyone who is not likely, or required, to be able to maintain the repo directly, should be withdrawn to a read-only role.

[IanSuper7]

Yes I’m getting the emails – lets cover this tonight on the call From: Peter Harrison ***@***.***> Sent: 13 August 2025 19:13 To: ukmars/gemini ***@***.***> Cc: IanSuper7 ***@***.***>; Review requested ***@***.***> Subject: Re: [ukmars/gemini] Merge V2.1 into main and tag as V2.1.0 (PR #80) <https://avatars.githubusercontent.com/u/667050?s=20&v=4> micromouseonline left a comment (ukmars/gemini#80) <#80 (comment)> Perfect. That is how it will work. Anyone with write access to the repo can edit/update the PR until it gets merged in. I am assuming Ian sees these messages. A risk, until we go public, is that one of the other contributors bypasses the rules. After going public, we can apply restrictions. At some point, anyone who is not likely, or required, to be able to maintain the repo directly, should be withdrawn to a read-only role. — Reply to this email directly, view it on GitHub <#80 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMQT2O6I6ECPJ542ROBYOPD3NN535AVCNFSM6AAAAACDZUDH5KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCOBUHE4DQNBZGI> . You are receiving this because your review was requested.Message ID: ***@***.*** ***@***.***> >