Taxel: Change default branch to be main

[glensc]

Problem: Requirement to have 1 review, slows down project development.

Solution: Use a different branch than master for development.

• EDIT[2021-03-25]: Decided to switch to git-flow model, where changes go to develop and releases from master branch: Switch to use git flow development model #160
• EDIT[2021-04-04]: will go with simple main for now, as I'm doing changes alone here.
• EDIT[2021-04-12]: set default branch to 0.7.x, 0.6.x (aka main) should be merged here: Merge up 0.6.x to master #209
• EDIT[2021-04-17]: set default branch to be main

refs:

• Feature: Add PlexApi class for dealing with Plex Api fetching and caching #142 (comment)
• Create CONTRIBUTING.md file #159 (comment)
• Create CONTRIBUTING.md file #159 (comment)

@Taxel please update project settings to reflect new changes.

[Taxel]

@glensc I disabled the branch protection for master and switched the default branch to 0.7.x. Would it make more sense to merge 0.7.x into main and using that as the default branch?

[glensc]

@Taxel hello! :)

I've made a mess here during your absence, so let me provide a plan on how to proceed.

[glensc]

I actually like the two branch mechanism here, provides some kind of stability and developer releases procedure.

so, right now:

1. merge main -> master: Merge up 0.6.x to master #209 this is known as 0.6.x branch @glensc
2. re-create main from merged master @glensc
3. set default branch to be main @Taxel
4. merge 0.7.x -> main: Merge up 0.7.x to main #248, this is known as 0.7.x branch @glensc
5. create branches 0.6.x, 0.7.x from their last state. they will be left for bugfixes only @glensc

altho I prefer merging to 0.8.x and one new version start merging to 0.9.x branch, but this procedure would require to update default branch from time to time. it's tedious and requires owner permission in the repository, which I don't have.

and next steps:

1. create a branch from main for 0.8.x development, make new developments go there.
2. delete master branch
3. create 0.5.x for maintenance @glensc

time to time when development is complete, create merge up pull request (like #209, #248):

1. create a merge request to merge 0.8.x to main
2. merge 0.8.x merge up merge request
3. create a new branch 0.9.x from main

EDIT: Edited for clarity and added checkboxes

[glensc]

@Taxel wdyt? is it clear? if no objections I will proceed with the "right now" items.

[glensc]

@Taxel I realized that the plan has a conflict with the current default branch (0.7.x), github may do something funny, for example close all pull requests.

so, I'll merge #209, and you set the default branch back to main, but not before #209 is merged.

EDIT: #209 is merged

[glensc]

@Taxel merged #209, can you set the default branch to be main now, so could proceed with this plan:

• Taxel: Change default branch to be main #162 (comment)

sorry for the mess. I'm trying to figure out myself too how this should work :)

[glensc]

And as I guessed, GitHub still did something funny. when #209 was merged, all other PR's merging to main were closed as the main branch was deleted:

• Add system_device, history methods to PlexApi #200

[Taxel]

@glensc default branch is now main.

[glensc]

All done!

I guess should update documentation, re-opened PR for that:

• Switch to use git flow development model #160