Stabalization - roadmap to v1.0

[tcharding]

Tracking issue for what is needed for us to be able to stabalize the bech32 crate.

Issues we want resolved

• Support identifying potentially errorneous characters #95

Issues that might apply

[tcharding]

Original discussion is in #60 but that issue is quite old and a bit stale. I've opened this one so that, if @apoelstra and @Kixunil are happy, we can close #60 to save others trawling through the stale stuff.

There is a problem though with this, not everyone can edit the issue like the ones on rust-bitcoin. I'm not a maintainer here and neither is @Kixunil - not sure how to project manage this crate.

I can just close this if its not an improvement over #60.

[tcharding]

@clarkmoody or @apoelstra please add a 1.0 label same as rust-bitcoin.

name: 1.0
color: #78BE0C
description: Issues and PRs required or helping to stabilize the API

[apoelstra]

Done.

[tcharding]

Oh I can't add labels to issues, even ones I wrote myself.

[apoelstra]

:/. Do you remember offhand if there's a non-maintainer github role that would let you do that?

[tcharding]

Looks like there is, "Triage". https://docs.github.com/en/organizations/managing-user-access-to-your-organizations-repositories/managing-repository-roles/repository-roles-for-an-organization

[apoelstra]

@clarkmoody can we make @tcharding a "Triage" member here?

I will do the same on rust-secp if you need, @tcharding .

[tcharding]

I will do the same on rust-secp if you need, @tcharding .

Yes please.

[clarkmoody]

@clarkmoody can we make @tcharding a "Triage" member here?

Done! 😄

[tcharding]

Thanks!