search

charlesangus / DeepC

Suite of Deep compositing tools for Foundry's Nuke.
GNU General Public License v3.0
103 stars 12 forks source link

Release/Development Branche #87

Open jonassorgenfrei opened 2 years ago

jonassorgenfrei commented 2 years ago

I would suggest to have release/development branches. So that the (main) release branche is always corresponding to the latest publish. Then we can merge pull requests to the development branche and merge the dev branche with the release branche when we create a new release.

At some point we might even can automate the building, and release circle with github actions in the futur. What do you think? @charlesangus @falkhofmann

charlesangus commented 2 years ago

It's an option, yeah. I've always kind of felt like for smaller projects like this, working out of the main branch simplifies things and adding a dev branch doesn't add a lot of value, but you're right, to automate builds, we would probably want a dev branch so that merges to master trigger a release.

I actually started looking at a Docker to containerize and standardize the (Linux) build env, which could be a first step to automating the build. Would we need a license for the automation machine, though? I don't really know how that works.

jonassorgenfrei commented 1 year ago

Have looked into GitHub automatization and made it work for windows and Linux using GitHub actions. Will check with foundry if the way I do this is valid for them. I would then add an action to build and release plus tag on every push to the main branch. May be we don't need an development branches then (?).