Hello everyone, I'm Joe (Github ID: jbiz805), one of the contributors in AGE.
While I was working on the AGE readme for the past couple of months I couldn't help but notice questionable naming of branches in AGE repo. I am quite confused with the branch naming at the moment because the latest version is PG 12(AGE_PG12.1.0_ALPHA) and yet the Master branch dedicates to PG 11. Unlike other standalone software out there, I understand that there must be branches for each Postgres version for AGE, like the upcoming 13, 14, and 15. But if PG 12 is now official (as updated in *release/PG12/1.1.0*) I think the topics below need to be discussed. Also, I think the whole branch names need updates because to an outsider or non-developer pov, the branches seem quite unorganized. *1) Master Branch & Rename AGE_PG12.1.0_ALPHA* - since it's no longer Alpha, rename the alpha branch or remove the word alpha - also PG12 is the latest version for AGE, so shouldn't it be promoted to Master branch and PG 11 be made into a separate branch (for example, *AGE_PG11.1.0*)? - Just out of curiosity, does every GitHub repo require a master / main branch or can we just clearly specify branches for PG 11 and PG 12? *2) Update release notes for AGE_PG12.1.0_ALPHA (minor)* - currently showing Aug 11th release note, which belongs to PG 11 *3) Rename PG 11 release branches * - right now PG 12 release branch is named *release/PG12/1.1.0* *-* suggestion to rename PG 11 release branches, for example, *release/PG11/0.6.0*, *release/PG11/0.7.0*.... so on) Let's discuss the topics above and see what we can do about organizing the branches. Best regards, Joe * Joe Suh / 서준섭* * 과장 / 마케팅전략팀* *M* : 010-5364-5357 * P* : 070-5038-5732 *F * : 070-8677-2552 서울특별시 강남구 테헤란로 516 정헌빌딩 4층 F4, 516, Teheran-ro, Gangnam-gu, Seoul, Republic of Korea
