[DISCUSS] Migration strategy for commits to newly supported, unsynchronized, AGE PG version branches.
Hi All, There is a need to discuss our strategy going forward for migrating commits from, as an example, AGE for PG 11 (called PG11 from this point) to AGE for PG 12, 13, etc. (called PG, from this point) for newly supported PostgreSQL version branches. First, I'm no Github expert and welcome any viable, potential alternatives. So, please do add suggestions or comments. The issues that arise come down to the *author *and *co-author* of the work being moved from one version to another. These issues are due to the creation of newly supported PostgreSQL version branches and the adding of commits that were not part of the previous version, at the time of the creation of these new branches. Please note: Once a new branch is synchronized (brought up to current), it will be up to the individuals who put forth a PR, to apply it to applicable versions. We will only be migrating commits to synchronize newly created branches. This means that, once a branch is synchronized, any new PRs added, are the responsibility of the PR creators. For example, if one creates a PR for PG11, and PG12 and PG13 have been synchronized at the time, it will be up to that person to create a PR for PG12 and PG13. As far as I'm aware, other than modifying patch files directly, there are only 2 ways to migrate a commit from one separate branch to another. Remember, these branches are diverging. 1. Extract a patch manually, apply it to a local feature branch, make sure that everything works as expected, rebase it to the local PG branch, then push that branch back to the remote. 2. This is similar to #1, except it is done as a PR. Using option #1, the original author of the patch is preserved, but there is no co-author information for the person doing the migration. Additionally, it doesn't use a PR, so isn't as trackable. Using option #2, the original author is changed to the PR creator and the original author is now the co-author. Our preference would be to preserve the original author, as the author, and have the person writing the PR become the co-author. However, it doesn't appear as if that is possible. The co-author is important to keep as a record of who did the work migrating the PR and, they potentially did a lot of work to migrate that patch. Being faced with these two options, neither of which are ideal, we're leaning towards option #2. This is where anyone who has any comments, experience, or expertise is welcome to speak up. Additionally, if there are any reasonably viable alternatives, we would be interested in hearing them out. Otherwise, provided no input or reasonable alternatives we will be going with option #2. Thank you to everyone in advance, John Gemignani
[GitHub] [age-viewer] Nimra-1234 commented on issue #125: Update Readme file in AGE Viewer Go branch
Nimra-1234 commented on issue #125: URL: https://github.com/apache/age-viewer/issues/125#issuecomment-1421053548 @saadjameel I'm not added in AGE Viewer Go branch ( https://github.com/apache/age/graphs/contributors ). Therefore can't do PR. Kindly add me . -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@age.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [age] TalhaMunir-JD commented on issue #474: Grow the community to have our changes to MariaDB necessary to do this integrated into the primary source code
TalhaMunir-JD commented on issue #474: URL: https://github.com/apache/age/issues/474#issuecomment-1421011543 Hi I am Talha and I am excited to start working on this project -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@age.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [age] TalhaMunir-JD commented on issue #454: All Functions
TalhaMunir-JD commented on issue #454: URL: https://github.com/apache/age/issues/454#issuecomment-1421011364 Hi I am Talha and I am excited to start working on this project -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@age.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [age] TalhaMunir-JD commented on issue #453: Union
TalhaMunir-JD commented on issue #453: URL: https://github.com/apache/age/issues/453#issuecomment-1421011194 Hi I am Talha and I am excited to start working on this project -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@age.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [age] TalhaMunir-JD commented on issue #452: Match / Create / Set / Remove / Delete / Merge / Call / Yield Clause
TalhaMunir-JD commented on issue #452: URL: https://github.com/apache/age/issues/452#issuecomment-1421011015 Hi I am Talha and I am excited to start working on this project -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@age.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [age] TalhaMunir-JD commented on issue #473: Write the extension to use those hooks
TalhaMunir-JD commented on issue #473: URL: https://github.com/apache/age/issues/473#issuecomment-1421010816 Hi I am Talha and I am excited to start working on this project -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@age.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [age] TalhaMunir-JD commented on issue #472: Add in the Hooks to allow extension to make modifications as necessary
TalhaMunir-JD commented on issue #472: URL: https://github.com/apache/age/issues/472#issuecomment-1421010616 Hi I am Talha and I am excited to start working on this project -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@age.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [age] TalhaMunir-JD commented on issue #451: Fork the MariaDB Source Code
TalhaMunir-JD commented on issue #451: URL: https://github.com/apache/age/issues/451#issuecomment-1421010253 Hi I am Talha and I am excited to start working on this project -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@age.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [age-viewer] MJinH commented on issue #124: For AGE-VIEWER IN GO interns
MJinH commented on issue #124: URL: https://github.com/apache/age-viewer/issues/124#issuecomment-1420480504 Here's my crud link. [application](https://github.com/MJinH/go-crud) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@age.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
