From: "Erik Schilling" <erik.schilling@linaro.org>
To: "Bartosz Golaszewski" <brgl@bgdev.pl>
Cc: "Linux-GPIO" <linux-gpio@vger.kernel.org>,
"Viresh Kumar" <viresh.kumar@linaro.org>,
"Manos Pitsidianakis" <manos.pitsidianakis@linaro.org>,
"Kent Gibson" <warthog618@gmail.com>
Subject: Re: [libgpiod][PATCH] bindings: rust: libgpiod: release 0.2.0
Date: Thu, 05 Oct 2023 20:09:56 +0200 [thread overview]
Message-ID: <CW0PH9GI74F3.1B30D7MK0P0DB@ablu-work> (raw)
In-Reply-To: <CAMRc=MeTHSwyTPcjm1kttCjr4GrknqM2pqfWZ8ngFWWxC8YxeQ@mail.gmail.com>
On Thu Oct 5, 2023 at 7:47 PM CEST, Bartosz Golaszewski wrote:
> On Thu, Oct 5, 2023 at 9:42 AM Erik Schilling <erik.schilling@linaro.org> wrote:
> >
> > Since we had some (potentially-)breaking changes, we bump the major for
> > the next release of the crate.
> >
> > Note:
> > I am using the term "major" as defined in the Rust SemVer compatibility
> > guide [1], where the first non-zero digit is considered as "major".
> >
>
> This makes no sense to me in terms of logical versioning but I trust
> you guys know what you're doing.
It basically allows for people to either use just MAJOR, MAJOR.MINOR
(like we do at the moment) or MAJOR.MINOR.PATCH by leaving the leading
fields 0.
I got no strong feelings on this. We could switch to MAJOR.MINOR.PATCH
with the next bump if that is more logical to your :).
> Applied.
Thanks! Published: https://crates.io/crates/libgpiod.
- Erik
>
> Bart
>
> > [1] https://doc.rust-lang.org/cargo/reference/semver.html
> >
> > Changelog:
> > =========
> >
> > (potentially-)breaking changes:
> > a29f3e6 (bindings: rust: rename {event,settings}_clone to try_clone, 2023-10-04)
> > b290348 (bindings: rust: fix soundness of line_info modeling, 2023-10-03)
> > d04639d (bindings: rust: bump MSRV to 1.60, 2023-06-16)
> >
> > new functionality:
> > 808d15e (bindings: rust: allow cloning line::InfoRef -> line::Info, 2023-10-03)
> > 64aac85 (bindings: rust: mark all owning types as `Send`, 2023-09-28)
> > d12ce74 (bindings: rust: provide LineRequest::chip_name(), 2023-07-20)
> > 53226d5 (bindings: rust: examples: add dedicated examples, 2023-06-14)
> >
> > other changes:
> > 0a570b6 (bindings: rust: drop unneeded Arc within Chip, 2023-09-27)
> > a97fe96 (bindings: rust: construct chip infos by reference, 2023-09-27)
> > 27afa47 (bindings: rust: remove useless clone, 2023-09-28)
> > 3f6e0bf (bindings: rust: add README.md for libgpiod crate, 2023-07-03)
> > 4b8357b (bindings: rust: clippy: silence false-positive on iterator, 2023-06-30)
> > 39189f0 (bindings: rust: clippy: drop unneeded conversions, 2023-06-30)
> > 46115fd (bindings: rust: clippy: silence false-positives on casts, 2023-06-30)
> > 901104e (bindings: rust: clippy: drop unnecessary casts, 2023-06-30)
> > 46ecbe0 (rust: examples: file comment consistency, 2023-06-24)
> > aaed0f2 (bindings: rust: examples: replace tools examples with use case examples, 2023-06-23)
> > b37bd9e (bindings: rust: examples: consistency cleanup, 2023-06-23)
> > 06c8ad9 (bindings: rust: package new examples in the distro tarball, 2023-06-15)
> >
> > Signed-off-by: Erik Schilling <erik.schilling@linaro.org>
> > ---
> > After merging a couple of important soundness fixes and threading API
> > adjustments, I suggest doing a new release for the Rust bindings.
> >
> > Once this is merged, I will publish the tree of this commit to
> > https://crates.io/crates/libgpiod/.
> > ---
> > bindings/rust/libgpiod/Cargo.toml | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/bindings/rust/libgpiod/Cargo.toml b/bindings/rust/libgpiod/Cargo.toml
> > index 518e5e5..3be4aa0 100644
> > --- a/bindings/rust/libgpiod/Cargo.toml
> > +++ b/bindings/rust/libgpiod/Cargo.toml
> > @@ -4,7 +4,7 @@
> >
> > [package]
> > name = "libgpiod"
> > -version = "0.1.0"
> > +version = "0.2.0"
> > authors = ["Viresh Kumar <viresh.kumar@linaro.org>"]
> > description = "libgpiod wrappers"
> > repository = "https://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git"
> >
> > ---
> > base-commit: a29f3e6957914dc564c723a8fc405cd99e407fd2
> > change-id: 20231005-b4-rust-release-0_2_0-1344e6af7cc2
> >
> > Best regards,
> > --
> > Erik Schilling <erik.schilling@linaro.org>
> >
prev parent reply other threads:[~2023-10-05 18:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 7:42 [libgpiod][PATCH] bindings: rust: libgpiod: release 0.2.0 Erik Schilling
2023-10-05 7:43 ` Viresh Kumar
2023-10-05 17:47 ` Bartosz Golaszewski
2023-10-05 18:09 ` Erik Schilling [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CW0PH9GI74F3.1B30D7MK0P0DB@ablu-work \
--to=erik.schilling@linaro.org \
--cc=brgl@bgdev.pl \
--cc=linux-gpio@vger.kernel.org \
--cc=manos.pitsidianakis@linaro.org \
--cc=viresh.kumar@linaro.org \
--cc=warthog618@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox