After the 6.9 RC1 release was successfully published, the 6.9 branch was created. However, there were a few missteps.
The first attempt to branch in [61215] copied trunk to the top level of the repository. This was reverted in [61218].
The second attempt to branch in [61219] copied the branches folder into branches/6.9. This was reverted in [61220] with a branch deletion.
The third attempt to branch in [61221] appeared to work successfully from an SVN Apache Subversion (often abbreviated SVN, after its command name svn) is a software versioning and revision control system. Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS). WordPress core and the wordpress.org released code are all centrally managed through SVN. https://subversion.apache.org/. perspective. On GitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ however, the wordpress-develop mirror shows that the branch is “8697 commits ahead of and 4 commits behind trunk“.
This seems to be caused by the fact that the scripts responsible for syncing the SVN repository to the Git Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. Git is easy to learn and has a tiny footprint with lightning fast performance. Most modern plugin and theme development is being done with this version control system. https://git-scm.com/. mirrors did not perform a proper deletion of the branch in Git for the develop.git.wordpress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ mirror. I’ve confirmed this by running the following on a develop.git.wordpress.org checkout: git rev-list --count HEAD..6.9 (prints 8697).
Is it possible to correct this, perhaps by properly deleting the branch in Git and re-syncing the mirrors so that the 6.9 branch is created cleanly starting with [61221]? Another possible option could be to perform two manual commits to the Git mirror that takes the same steps that [61219-61220] did for SVN (deletes the branch, properly creates the branch).
While this will likely result in changes to the commit hashes, this seems like a fair trade off considering it just happened for the sake of an accurate history in version control. Any actions taken should not impact the RC1 release in any way because that was published from [61213] in trunk, and the post release version bump commit ([61214]) occurred before the first branching attempt in [61215].
Possibly relevant: The post-receive hook on develop.git.wordpress.org is as follows: git push --mirror github-wp-develop:WordPress/wordpress-develop.git (note the absence of a --force flag).
If necessary, guidance can be published to the Make WordPress Core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. blog for anyone who has synced their fork in the last 24 hours.
Login to Reply<\/a><\/li><\/ul><\/div>","commentTrashedActions":"
