Master branch behind version-1.13

[claudep]

The latest release was done from the version-1.13 branch which has 4 more commits than the master branch.

@moggers87, is this wanted or just an oversight?

[moggers87]

I can't push to master directly. I did email @Bouke after the release, but I think he's been busy and hasn't had time to get around to pushing that branch to master yet.

[claudep]

If the rule is that a merge request needs an approval before being pushed to master, it's a good thing. But if only @Bouke can merge to master, then I'd consider this as a bug :-) (bus factor and all that). @Bouke, can we solve that?

[moggers87]

I can push to master if the commits have been reviewed, but I can't be both committer and reviewer. @Bouke doesn't have those restrictions being the repo owner, of course.

@claudep are you volunteering to become an additional maintainer? 😉

[claudep]

I cannot claim to be knowledgeable in every part of this package, but for the parts that I know, I would be glad to help for reviews.

[Bouke]

Thanks for the great enthusiasm here, this is why it's great to be part of the FOSS community! I've now merged the 1.13 branch into master. Merging things into master requires the reviewer to be a separate user from the committer. So with that in mind, @claudep's help would be great! The bus factor is certainly a thing, and that's also why I've already moved django-user-sessions over to jazzband. However that project itself is currently also limited to a single person, so that doesn't help with the bus factor. There is some activity under way that should help, so I'm awaiting their resolve.

[claudep]

I guess this can now be closed.