You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Previously we'd include the ID of the commitfest in the URL of the
patch. In 9f12a5e we introduced a stable URL for patches that would
redirect to the one for the latest commitfest. This starts to use that
URL as the valid only URL for a patch (with the previous URL redirecting
to this one).
The reasoning behind this is that the old approach resulted in N
different URLs for each patch, which all showed the exact same patch
information. The only difference between all these URLs would be the
breadcrumb at the top of the page.
The only benefit of that approach is that if you're on an old
commitfest, and click a link there, then the breadcrumb will bring you
back to where you came from. Since people rarely have a reason to browse
closed commitfests, the that benefit seems pretty small. Especially
because people can just as well press their browser back button, in that
case.
The problems that these N links cause seem much more impactful to most
users:
1. If you click an old link to a cf entry (e.g. one in the email
archives), then the breadcrumb will contain some arbitrarily old
commitfest. It seems much more useful to have the breadcrumb show the
commitfest that the patch is currently active in (or got
committed/rejected in).
2. Places that use the stable URLs require an extra round-trip to
actually get to the patch page.
3. It's a bit confusing that old pages of a patch still get updated with
all the new information, i.e. why have all these pages if they
contain the exact same content.
4. Problem 3 is generally also bad for Search Engine Optimization (SEO),
for now we don't care much about that though.
Finally this also changes the links on the patch page itself for each of
the commitfests that a patch has been part of. Those links were already
rather useless, since all they effectively did was change the
breadcrumb. But with this new commit, they wouldn't even do that anymore,
and simply redirect to the current page. So now they start pointing to
the commitfest itself, which seems more useful behaviour anyway.
0 commit comments