Change default branch to 1.3 about dataformat HOT 7 CLOSED

That would require admin access to the repo.

/cc @outofcontrol

from dataformat.

That's not our usual git practice, where master is the latest and greatest. We tried something like what you're saying in Vulkan, and regretted and reverted that practice later. It's up to the controlling Working Group(s) to decide collectively if they need to do this; I will not make this change without that signoff. As a general matter, all administrative / policy decisions on our repos are owned by the WG associated with the repo, not by any individual member of it.

from dataformat.

Given that this public repo lacks master branch altogether, it would make more sense to have the latest branch (1.3) as default. Otherwise, we could have master here and follow usual git workflow.

from dataformat.

I have no objection to renaming 1.3 to master and tagging it 1.3-gh. I'll do it if I have sufficient permissions.

from dataformat.

I've done it. However the default branch is still set to 1.2. @oddhack do you need me to get signoff to change it to master? Note that the owning WG at present is unclear. How to manage KDFS was to be discussed at the chairs and the board meeting last week.

from dataformat.

@oddhack, please respond to my previous comment.

from dataformat.

This has been fixed.

from dataformat.