Remove trailingslashit rule for theme directory URIs

Currently the nginx rules for the theme directory includes a similar to the following, can we please remove it, as it breaks access to URLs that shouldn’t have a trailing slash, such as https://wordpress.org/themes/sitemap.xml
There should already be a handler in the PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. https://www.php.net/manual/en/preface.php. environment to add the trailing slash if it’s missing.

location /themes/ {
        # Add a trailing slash to all themes
        rewrite ^/themes/([^/]+)$ /themes/$1/ permanent;
}

This is being tracked as #5022-meta.

#prio2

#5022-meta

plugins.svn is very slow

This is a known issue, but it seems like it’s gotten significantly worse in the past ~6 months, to the point where it’s disruptive to workflows, and would delay promptly recovering from bad deploys.

Here are some timings from my WordCamp.org sandbox using, using themes.svn as a baseline.

/wp-content/themes ( 10 svn:externals to themes.svn )
$ time svnup

real 0m0.313s

wp-content/plugins ( 27 svn:externals to plugins.svn items, 1 to meta.svn )
$ time svnup

real 3m29.532s

$ time deployDeploy Launching code from a local development environment to the production web server, so that it's available to visitors.-wordcamp.sh

real 4m44.074s

With a deploy taking almost 5 minutes, there’ll be a lot of extra/unnecessary downtime if we ever need to revert a bad commit and re-deploy.

#prio-2

#prio2

Remove cookie-stripping behaviour from Trac Ticket caching

As per previous discussions, can we please remove the TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. Caching that strips the Set-Cookie headers from Trac ticket pages?

As mentioned, this causes failures to comment on tickets – https://meta.trac.wordpress.org/ticket/4360

As discussed, you’ll find a hacky Trac plugin that attempts to avoid setting useless Trac cookies in https://wordpress.slack.com/archives/G02QCEMRY/p1554790742034300?thread_ts=1554340318.022800&cid=G02QCEMRY but it’s mostly untested and may not work as needed.

The Latest trac plugin is in https://gist.github.com/dd32/e1a6e434cb9b5721cc086e51751f8c44 and has been tested well on a standalone trac installation.
The pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party does several things:
– Prevents Cookies being sent on anonymous pageviews
– Prevents anonymous sessions being saved to the DB (as there’s no such thing anymore)
– Blocks access to /prefs for anonymous users
– Expires all trac_* cookies after the user is no longer authenticated, such as to remove the trac_form_token cookie.

#trac #prio1