[Sound-open-firmware] New, separate sof-tplg-v1.2.3.tar.gz tarball release for topologies
Hi,
Topologies tend to require more frequent releases, so we plan to split future sof binary releases into two different tarballs instead of one.
From:
sof-bin-v1.2.3.tar.gz # firmare _and_ topologies in the same tarball
To:
sof-bin-v1.2.4.tar.gz # firmware sof-tplg-v1.2.4.tar.gz # topologies
Every firmware tarball will have a corresponding topologies tarball.
Some topologies releases will have NO corresponding firmware tarball.
At this point in time there is no plan to change the structure of the sof-bin git repo, this change will affect tarballs only.
Thoughts, comments? Thanks!
Marc
On 22. 02. 22 7:33, Herbert, Marc wrote:
Hi,
Topologies tend to require more frequent releases, so we plan to split future sof binary releases into two different tarballs instead of one.
From:
sof-bin-v1.2.3.tar.gz # firmare _and_ topologies in the same tarball
To:
sof-bin-v1.2.4.tar.gz # firmware sof-tplg-v1.2.4.tar.gz # topologies
Every firmware tarball will have a corresponding topologies tarball.
Some topologies releases will have NO corresponding firmware tarball.
At this point in time there is no plan to change the structure of the sof-bin git repo, this change will affect tarballs only.
Thoughts, comments? Thanks!
Hi,
the split looks fine. I would suggest to write the required sof-bin version by sof-tplg to each release notes on github to make things clear.
Jaroslav
BTW: Could you send information about new releases to this list?
Jaroslav,
We could send information to this list but... my messages do not make it.
I answered https://mailman.alsa-project.org/pipermail/sound-open-firmware/2022-February... 2 weeks ago and my answer was never moderated.
This message below did not make it either.
Before sending it I tried to subscribe but that did not seem to work either.
Marc
On 2022-02-22, 01:26, "Jaroslav Kysela" perex@perex.cz wrote:
On 22. 02. 22 7:33, Herbert, Marc wrote: > Hi, > > Topologies tend to require more frequent releases, so we plan to split future sof binary releases into two different tarballs instead of one. > > From: > > sof-bin-v1.2.3.tar.gz # firmare _and_ topologies in the same tarball > > To: > > sof-bin-v1.2.4.tar.gz # firmware > sof-tplg-v1.2.4.tar.gz # topologies > > Every firmware tarball will have a corresponding topologies tarball. > > Some topologies releases will have NO corresponding firmware tarball. > > At this point in time there is no plan to change the structure of the sof-bin git repo, this change will affect tarballs only. > > Thoughts, comments? Thanks!
Hi,
the split looks fine. I would suggest to write the required sof-bin version by sof-tplg to each release notes on github to make things clear.
Jaroslav
BTW: Could you send information about new releases to this list?
-- Jaroslav Kysela perex@perex.cz Linux Sound Maintainer; ALSA Project; Red Hat, Inc.
On 22. 02. 22 17:08, Herbert, Marc wrote:
Jaroslav,
We could send information to this list but... my messages do not make it.
I answered https://mailman.alsa-project.org/pipermail/sound-open-firmware/2022-February... 2 weeks ago and my answer was never moderated.
This message below did not make it either.
Before sending it I tried to subscribe but that did not seem to work either.
You are not subscribed, you may try to subscribe again. Contact me directly, if something does not work. It seems that the ALSA's outgoing SMTP server is fine.
Liam and Pierre-Louis are also moderators. If the message is not touched 7 days - it's auto-discarded.
Jaroslav
the split looks fine. I would suggest to write the required sof-bin versionby sof-tplg to each release notes on github to make things clear.
JaroslavBTW: Could you send information about new releases to this list?
I wonder if there is a way we can simply install the list as a release watcher on github. Or maybe set up an action on release to do it.
-- Jaroslav Kysela perex@perex.cz Linux Sound Maintainer; ALSA Project; Red Hat, Inc. _______________________________________________ Sound-open-firmware mailing list Sound-open-firmware@alsa-project.org https://mailman.alsa-project.org/mailman/listinfo/sound-open-firmware
On 2022-02-22 16:36, Curtis Malainey wrote:
the split looks fine. I would suggest to write the required sof-bin versionby sof-tplg to each release notes on github to make things clear.
JaroslavBTW: Could you send information about new releases to this list?
I wonder if there is a way we can simply install the list as a release watcher on github. Or maybe set up an action on release to do it.
I'd love that too. I do the debian packaging and I managed to miss a couple of releases before I got caught up.
My inbox is a nightmare, and I do a lot of filtering - so it's really easy to miss updates. If there was a way to generate a notice of a new release that was sent to my email directly rather than the list I'd be much less likely to miss it :)
Mark
participants (4)
-
Curtis Malainey -
Herbert, Marc -
Jaroslav Kysela -
Mark Pearson