[kinlan]

There's lots of reasons some of which I can't go into details about, but there are some that I can:

There is a freeze to the new infrastructure's product features until after the new year and we needed to get this in before then (we can land feed support without a product feature change)

The people I have working on the older infrastructure will be on new projects for our team in the new year.

[lapcat]

Were the deadlines, feature freezes, and project reshuffling imposed on you from above, or were they your decisions?

In a blog post two months ago you said, "I've taken the decision..." https://web.dev/blog/webdev-migration

There was clearly someone in Google management who decided that RSS could be broken.

Why is this important? Well, for example, it seems that the RSS feed was already broken when this important announcement was posted: "Resuming the transition to Manifest V3" https://developer.chrome.com/blog/resuming-the-transition-to...

[kinlan]

> Were the deadlines, feature freezes, and project reshuffling imposed on you from above, or were they your decisions?

They were my decisions based on all the data I had, including launching with what we had.

re: "Resuming the transition to Manifest V3" this was posted on the old infrastructure and should have been in your RSS feeds up until late last week when our migration happened - so for just under a month... I can check more to make sure what I am saying is correct, but the migration only happened last week.

[lapcat]

According to my backups, https://developer.chrome.com/feeds had XML with <updated>2023-10-17T00:00:00Z</updated> until December 7, then HTML after December 8. So it wasn't entirely broken until December 8 but seems to have been frozen for some time before that.

[kinlan]

Hmm - that shouldn't have been the case, but I can speak to the team to see what might have happened. Thanks for diving in to this.

[listmaking]

Not the GP but I think that blog post https://web.dev/blog/webdev-migration you linked explains it pretty clearly?

• The people working on web.dev decided to migrate to a common Google site platform, so that they could focus on content rather than maintaining an ad-hoc infrastructure,

• That platform happens not to support RSS (yet), so they've done the best they can in the meantime, filing a bug with the platform, creating the https://developer.chrome.com/feeds info page acknowledging the issue, and even creating unofficial feeds.

You could phrase this as “someone in Google management who decided that RSS could be broken”, but relative to the big decision of whether to spend effort maintaining your own custom infrastructure or just focus on the content, the presence or absence of RSS support is probably just not a big factor.

[One could imagine a culture of "never migrate to a new system unless it fully supports every single functionality of the old system", but that (just like "never launch a product/feature unless you're confident you're going to support it forever") is simply not in Google's culture, where there are always ongoing migrations between "the old system that is deprecated and the new system that is not ready yet" — but that is "just" a cultural problem rather than anyone consciously deciding that RSS could be broken.]

[lapcat]

> relative to the big decision of whether to spend effort maintaining your own custom infrastructure or just focus on the content, the presence or absence of RSS support is probably just not a big factor.

This is a false dichotomy. I wasn't questioning the decision to migrate platforms, I was questioning "the deadlines, feature freezes, and project reshuffling".

> there are always ongoing migrations between "the old system that is deprecated and the new system that is not ready yet" — but that is "just" a cultural problem rather than anyone consciously deciding that RSS could be broken.

I disagree, because whenever you migrate, some features are considered essential and others inessential. Someone consciously decided that RSS was among the inessential features in this specific case. The "culture" did not make that specific decision.

This is the developer relations team. How can you have relations with developers when they don't even see your announcements? The essential part is the communication with outside developers, not the internal CMS.

> they've done the best they can in the meantime, filing a bug with the platform, creating the https://developer.chrome.com/feeds info page acknowledging the issue, and even creating unofficial feeds.

How were developers supposed to know any of this? I had no idea until now.

[listmaking]

The freeze "until after the new year" is just the end-of-year freeze to avoid production breakage when a lot of people are on vacation: it's an extension of the principle of not deploying on Friday evenings / weekends; lots of companies have such a freeze. Once you've decided a couple of months earlier to do a migration, doing it "before the freeze" is also a natural deadline to pick, for migrating to the new infrastructure, and for people working on the old infrastructure to complete the migration and move to other projects. I'm not on the team but these all seem like logical choices.

And yes, in the decision between "keep maintaining a custom infrastructure" and "switch to a common infrastructure", someone must have decided that RSS support is not an essential feature whose lack should block (or indefinitely postpone) the migration; this seems reasonable and what my previous post was about, including the "probably just not a big factor" bit you quoted above. It looks like they're planning to add this support though.

[lapcat]

> The freeze "until after the new year" is just the end-of-year freeze to avoid production breakage when a lot of people are on vacation

There was production breakage! The RSS feeds broke. That's the entire point of this HN submission and discussion.

> Once you've decided a couple of months earlier to do a migration, doing it "before the freeze" is also a natural deadline to pick, for migrating to the new infrastructure

Why? Migrations almost always break stuff, right? So why would you break stuff when "a lot of people are on vacation" and thus can't fix the breakage? It seems to me the natural and logical choice would be to wait until after the new year to migrate. What sense does it make to break stuff and then go on vacation?

> RSS support is not an essential feature whose lack should block (indefinitely postpone) the migration; this seems natural (especially if you think you can add it back in a few weeks / months)

It's interesting that you say "indefinitely" postpone but then turn around right away and say "a few weeks/ months".

[freedomben]

I don't really disagree with you, but I've been on the other end of this before and there was a major incentive to get it in before the break: all the context in our heads.

If we waited several weeks until after the christmas break, we'd lose a lot of mental context. It's also a horrible dark cloud hanging over your head. When dealing with a big migration, it's really ideal to do it while everything is still fresh. Context switching can be very expensive

[listmaking]

Sorry that this conversation is going in circles. At first, I was talking about the culture of migrating to a new system when it supports ~75% of the features (by importance) of the old, rather than closer to 100%. I would find it reasonable for some team to judge that RSS support is not in the crucial 75% (and its lack would not constitute production breakage); clearly you disagree. That's fine.

As for the rest, I was just explaining the general idea of a production freeze. If you're going to stop trying to make changes by a certain date "to be safe"; then that's the freeze date. Equivalently: people keep trying (and sometimes rushing) to do things until the actual freeze date. The date is early enough (quite a bit earlier than Dec 24) so that there's still enough time and people left to fix things or roll back, if there are genuine emergencies. This replaces the risk of production breakage with the risk of embarrassment/questions from asking for approval for an emergency fix during the freeze period, so people will still only do things they're fairly confident will be safe. Anyway, none of this is relevant unless lack of RSS support is considered a production breakage, which is the very point of disagreement here.

Sorry about the "few weeks / months" comment; I was editing it out while you were posting your comment. But yes, when deciding whether something is a blocker, it's safer to assume that it can take indefinitely long (until it actually exists), even if you think (or have been promised) that it will be quick. It's the difference between taking the mean versus the 95th percentile of the distribution of time estimates.

[dagurp]

There was a bug in the old RSS implementation (the last-updated date was always Jan 1st 1980) so it would be great if you fixed that when you re-add it

[gred]

My first quick scan of your comment gave me the impression that you were sarcastically asking for the date bug to be replicated in the new system for "backwards compatibility" purposes. Glad to see, upon reviewing, that I was wrong :-)