UDST release schedule and branching scheme

[pksohn]

Hi all,
Now that the core UDST libraries have up-to-date releases out on PyPI and Conda, I'd like to hear any opinions you all have about two things:

GitHub branching

The current model we're using is:
- Successful PRs get merged directly to master
- Master branch is most up-to-date code and diverges from versions on PyPI/Conda
- Master branch occasionally tagged to a release and uploaded to package managers

We've considered trying gitflow, which is a little more involved but has the advantage of keeping the master branch in line with the latest release. The main difference for contributors would be that PRs get merged to a dev branch instead of master. Any preferences here? Would this be overkill?

Release Schedule

There was a huge lag in issuing the latest releases - I think they included changes dating back to 2015. We'd like to get on a more frequent schedule, and our intent is to continue issuing releases whenever there seems to be a critical mass of new features. Are there any preferences for a different model? We could potentially cut new releases on a schedule (e.g. quarterly). I'm guessing most folks on this forum are cloning from GitHub directly, so maybe don't have strong opinions about this, but I thought we'd check.

Thanks,
Paul

[Eh2406]

We are cloning from github, but of course we were the versions on conda/pip where massively out of date. If we have more uptodate releases, with release notes, we may track the current release.

Perhaps we release on an as needed basis, but have a scheduled release triage. So once per quarter someone goes thru all the projects to see if it is overdue for a release.