On May 18, Imre Jonk wrote:
> Thid only had merit when DebOps roles were in separate git
> you can just fork the DebOps monorepo, create your own branch and put the
> roles there. It's very easy to keep your changed updated with the main project
> by fetching new changes from master and rebasing your branch on top of them.
Check. Will the non-commercial roles currently in debops-contrib (like
debops-contrib.dropbear_initramfs) be merged into debops master?
Yes, that's the plan. They will have to be renamed and cleaned up, of course.
They were imported from the repositories in https://github.com/debops-contrib/
organization when the migration to the monorepo happened, but I hadn't got
time to work on them yet. I'll probably migrate the 'debops-contrib.apparmor'
role next, or better yet write a similar one as 'debops.apparmor' since this
will be mandatory in Debian Buster. The next development cycle will probably
be focused on Debian Buster compatibility to prepare for the next release of
> I'm currently working on updating the 'debops.users'
role and moving the
> management of sysadmin accounts to a new 'debops.system_users' role which
> integrate with the LDAP support. After finishing these, I plan to make a new
> DebOps release so there's something tagged. Probably a week or two from now.
I red it on the list. Sounds good! We've only been using v0.8.1 roles
until now, so that means that I'll have to get some work done to get our
infrastructure ready for the next tag :)
After the v1.0.0 release I plan to cherry-pick any non-breaking changes to it
from later versions, so that sticking to one release without suddenly breaking
your infrastructure is feasible. I'm not sure how many such "stable"
will be feasible, perhaps sticking to the Debian release cycle will make the
most sense, we will see. But to get to that point, I want to clean up all of
the old roles first... Hmm, you know what? Screw that plan - people are using
DebOps in production already, so I'll bite the bullet and release v1.0.0 after
merging the user role changes. Let's get this thing rolling, this will be
a good test if cherry-picking non-breaking changes makes sense. Expect
a release in a week or two when I get the user roles updated.