Release coordination

[jywarren]

Just an issue to coordinate releases!

Hi @harshkhandeparkar and @harshithpabbati i believe you two are able to prepare releases for publication on the beta site. Would you like to do so and then I can push to the main sequencer.publiclab.org if all goes well? Thank you!

[jywarren]

And if you look at https://github.com/publiclab/image-sequencer/pulse/monthly and https://github.com/publiclab/image-sequencer/blame/main/package.json#L3, it's been 13 months since our last release at v3.5.1 -- i think it's time to put out a new release! v3.6.0 perhaps?

[jywarren]

Honestly it's been the entire previous GSoC with a ton of new features there. We may just want to release a v4, esp since SO much has changed. Many new systems including GPU acceleration, wasm, a ton of new modules, etc.

[harshkhandeparkar]

Yeah, I did forget to push in the last few months. Can we set up a GitHub action for this? The script is at https://github.com/HarshKhandeparkar/Update-is

[harshkhandeparkar]

Just pushed to beta btw.

[harshkhandeparkar]

The current beta is hosted at Harshit's fork, I am the only one who has access as of now. Can bots push to branches?

[harshkhandeparkar]

Actually, if publiclab has a spare server, someone could set up a cron job that checks for updates every hour or something and pushes to the beta if something new has been committed.

[jywarren]

Well, i wonder if we could just point at the latest GItPod build instead? That's already a working system to build a demo. What do you think?

[jywarren]

I guess it's already set up to prebuild environments from all branches: https://github.com/publiclab/image-sequencer/blob/main/.gitpod.yml#L12

Ah, cool - so, you just add any Github URL to: https://gitpod.io/# - so, https://gitpod.io/#https://github.com/publiclab/image-sequencer/ should build the main branch.

I think that worked? That is basically good enough to use as a "live" beta, no? Is that the URL (or at least the branch) that the badge in the README goes to?

[harshkhandeparkar]

IG it's good ¯\(ツ)/¯. Will it have an editor along with it? It is not the intended way of doing it though... gh-pages are generally preferred because that is how it will be finally deployed.

[harshkhandeparkar]

Why do we have a UI? 😂

[harshkhandeparkar]

https://github.com/HarshKhandeparkar/image-sequencer-ui still exists although no one is helping me with it.

[jywarren]

Thanks Harsh. Now that we have Jest tests for the UI I think we can more readily test image-sequencer-ui against the expected behaviors. But, we do need to codify what we expect a UI to be able to do! Does image-sequencer-ui have tests or does it match the CSS selectors of our UI tests closely enough that it can pass our Jest tests?

[jywarren]

And, let's move this convo to another issue so we can focus on release coordination here, is that OK? Thank you! ❤️

[jywarren]

Speaking of which, I've opened a PR for 3.6.0: #1695 🎉

[harshkhandeparkar]

Should we have included the February bug stomps too?