snapcrafters / obs-studio

This is a community-supported modified build of OBS Studio.
https://snapcraft.io/obs-studio
118 stars 35 forks source link

Call for testing `obs-studio` #194

Closed github-actions[bot] closed 6 months ago

github-actions[bot] commented 6 months ago

A new version (30.1.1) of obs-studio was just pushed to the latest/candidate channel in the snap store. The following revisions are available.

CPU ArchitectureRevision
amd641299

Automated testing

If configured, the snap will be installed in a VM, and any test results or screenshots will be posted to this issue as a comment shortly.

How to test it manually

  1. Stop the application if it was already running

  2. Upgrade to this version by running

    snap refresh obs-studio --channel latest/candidate
  3. Start the app and test it out.

  4. Finally, add a comment below explaining whether this app is working, and include the output of the following command.

    snap version; lscpu | grep Architecture; snap info obs-studio | grep installed

How to release it

Maintainers can promote this to stable by commenting /promote <rev>[,<rev>] latest/stable [done].

For example

  • To promote a single revision, run /promote <rev> latest/stable
  • To promote multiple revisions, run /promote <rev>,<rev> latest/stable
  • To promote a revision and close the issue, run /promote <rev>,<rev> latest/stable done

You can promote all revisions that were just built with:

/promote 1299 latest/stable done
github-actions[bot] commented 6 months ago

The following screenshots were taken during automated testing:

window

screen

jnsgruk commented 6 months ago

/promote 1299 latest/stable done

github-actions[bot] commented 6 months ago

The following revisions were released to the latest/stable channel: 1299.

BrycensRanch commented 6 months ago

/promote 1299 latest/stable done

why would you push this to stable..? you can clearly see in the ss that upstream is missing a plugin update that popups once the user opens the snap + the snap is labeled as obs version 30.1.1 but in reality it is 30.0.2 because the upstream project is out of date

BrycensRanch commented 6 months ago

@jnsgruk

jnsgruk commented 6 months ago

The plugin update does indeed need to be applied, but the snap revision itself is functioning correctly, which means the other updates that apply in this revision are still valid. We can work on addressing the plugin update seperately.

jnsgruk commented 6 months ago

Ah but I see your point about the version itself - I've spotted the problem and will open a separate issue.

BrycensRanch commented 6 months ago

Ah okay, I'll try to PR upstream