Closed guoyunhe closed 4 years ago
If you want, we can publish releases as directories on the static server, that would allow to reference older versions of the theme and allow the maintainer of the app to update in their free time
I am not sure how the cron jobs is working in static.opensuse.org. If they do git submodule update --init
every hour, then we just need to add the release as a submodule of https://github.com/openSUSE/static.opensuse.org
v2.0.0
.rel-2.0
.rel-2.0
will be hosted at https://static.opensuse.org/chameleon-2.0/ (waiting for heroes to merge and deploy)rel-2.0
will never be updated unless people report critical bugs that cannot wait for next release.rel-2.1
whenever they want.Sounds good to me, I would reserve 2.0.1 for bugfixes, because it's easy enough to change a number on one site, and bugs can still be used on some sites (I know I abuse some bugs), otherwise sounds sane
@hellcp it may take several weeks to get the CDN deployed. Before that I won't push anything to master. Only dev branch will be updated.
excellent, thank you
@hellcp now you can switch from:
static.opensuse.org/chameleon/
to
static.opensuse.org/chameleon-2.0/
master branch will not be touched until all sites have been switched to versioned URLs.
all new changes will happen in dev branch. and I am preparing for 3.0.
dev
will be created.dev
branch. No direct commit tomaster
.dev
tomaster
./chameleon-1.3
. We only push critical bug fixes to release branches. No feature or design changes./chameleon-dev
. only for live testing.dev
version can be merged intomaster
.@hellcp