John James Jacoby 3:59 pm on August 13, 2021
Tags: prio2 ( 100 )

Delete 2.9.5 tag at buddypress.svn.wordpress.org

A BuddyPress committer made a mistake in the 2.9.5 tag while back-porting a fix & performing a bunch of minor releases. I do not have the power to bypass the pre-commit hook:

Committing transaction...
svn: E165001: Commit failed (details follow):
svn: E165001: Commit blocked by pre-commit hook (exit code 1) with output:
Cannot commit to a tag.

If possible, may I please have this tag deleted: https://buddypress.svn.wordpress.org/tags/2.9.5

Bonus ask, may I please have the power to commit to tags on the BuddyPress & bbPressbbPress Free, open source software built on top of WordPress for easily creating forums on sites. https://bbpress.org. repositories (or have the restriction removed completely?) It happens rarely, but it’s an easy clean-up for me when it does.

IIRC, the original reason we’d added that hook many years ago was because we were using those tags for deployment to dotorg, but we switched to deployingDeploy Launching code from a local development environment to the production web server, so that it's available to visitors. from plugins.svn when we introduced build processes.

#prio2

Dion Hulse 1:02 am on August 16, 2021

may I please have the power to commit to tags on the BuddyPress & bbPressbbPress Free, open source software built on top of WordPress for easily creating forums on sites. https://bbpress.org. repositories (or have the restriction removed completely?) It happens rarely, but it’s an easy clean-up for me when it does.

The restriction is in place on most repos (backpress, bbpress, buddypress, glotpress, coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.) as tags are more “should never be altered” and svn doesn’t have that restriction. That’s even more important given it’s mirrored onto git://buddypress.git.wordpress.org/ and git alterations to tags are not possible.
- John James Jacoby 2:36 am on August 16, 2021
  
  Hey @dd32 👋
  
  I don’t mean to challenge your GitGit 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/. knowledge, but tags in Git can be deleted (even remote ones) and obviously tags can be deleted in SubversionSVN 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/., too.
  
  Our “should never be altered” policy is in place to circumvent technical propagation problems, and the embodiment of it eliminates the human temptation to casually violate it.
  
  My request isn’t to alter a tag, it is to delete it completely, also to prevent propagation problems.
  
  (In this specific situation, the policy gets in its own way – our own way – and requires manual human intervention.)
  
  The only alternative I can think of (to not deleting the tag) is simply to retag with a higher minor version number. It just seems unnecessary and undesirable to leave a botched tag existing in perpetuity.
  
  What do you think?
  - Dion Hulse 3:05 am on August 16, 2021
    
    No offence taken at all @jjj 🙂 You’re totally right, I shouldn’t have replied before coffee! I also have little git knowledge 😉
    
    I was incorrect, What I should’ve said is that the existing blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. is to prevent modifying tags, which can’t be done in git, and I’m fairly certain that the mirror script we’re using doesn’t handle deleting git tags.
    I don’t think we should be encouraging people to be able to bypass/remove the tag block though.
    
    In the past, coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. has simply skipped the version number when mis-tags have happened, and there’s still outstanding git branch removals from last year.
    - Barry 2:50 pm on October 16, 2021
      
      Hi @dd32 and @jjj – I’m not a fan of modifying (including deleting) tags in SVNSVN 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/. as they are supposed to be immutable, but if it’s something that y’all feel strongly about allowing, we should modify the pre-commit hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same. to allow that in general and not make one-off exceptions via this p2. In general, I think this should be a community/policy decision that is consistent across all plugins.
      
      It’s been months since the original request, so I’m going to assume for now we aren’t going to allow deleting/modifying tags, but if it turns out that’s something we want to allow in general, please let us know.
      - John James Jacoby 3:31 pm on October 18, 2021
        
        I get it, and I broadly agree. A policy change across the entire organization is obvious overkill, and not what I’m suggesting.
        
        For context, the 2.9.5 tag on the BuddyPress SubversionSVN 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/. repository will produce a fatal error for everyone who checks it out and activates it. Yes; the audience is small, and fatal error protection in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. should prevent most catastrophes.
        
        But… I strongly believe we all have a mutual responsibility to users to actively prevent breaking their sites, and it is within (y)our control to bypass the immutability of tags on an as-needed basis to keep users’ sites safe. That is all I care about.
        
        (I asked for the ability just to make life easy in the future, not to be a superhero 🦸🏻‍♂️)
        
        Rather than redefine the entire tag policy, can we clearly define the as-needed policy?