Foxy is now EOL

[moriarty]

It is June 1 2023 and Foxy has reached EOL

[fujitatomoya]

@moriarty thanks for the contribution.

can you add the following changes?

• .mergify.yml foxy backport rule can be removed. (refer to Mark ROS 2 Galactic as end-of-life #3243)

• ros2_documentation/source/Releases.rst

  Line 52 in 6de7fb9

  .rst-content tr:nth-child(4) {background-color: #33cc66;}

  should be removed to turn the background into gray.

• ros2_documentation/source/Releases.rst

  Line 109 in 6de7fb9

  - May 2023

  should be updated to exact E.O.L date.

[fujitatomoya]

@cottsay @audrow @Yadunund can you have another review?
CC: @clalancette

[clalancette]

We have not officially EOLed Foxy yet, so we should hold off on this. It is coming soon.

[moriarty]

We have not officially EOLed Foxy yet, so we should hold off on this. It is coming soon.

Why is it not official yet?

The original EOL date has passed.

[clalancette]

Why is it not official yet?

We haven't done the final sync. The work is in progress. In general, we don't guarantee an EOL date, just have an approximate end.

[moriarty]

Why is it not official yet?

We haven't done the final sync. The work is in progress. In general, we don't guarantee an EOL date, just have an approximate end.

I've set the date in that line to the last day of May 2023.
It seems odd to extend the EOL into June after it's been documented for a long time as May 2023.

https://www.ros.org/reps/rep-2000.html#foxy-fitzroy-may-2020-may-2023

For any projects which want to support current EOL versions this is effects things like resource planning and scheduling, and continuous integration budgets. I understand that the sync sometimes happens when the sync happens and that the last sync can easily get delayed due to Iron, but other non-core ROS 2 projects have already started assuming Foxy is EOL and dropping CI etc

[clalancette]

I understand that the sync sometimes happens when the sync happens and that the last sync can easily get delayed due to Iron

Yes, that's generally the reason. It's not impossible to do it at the same time as releasing a new release, but it can be hard at times. That was the case this year.

[moriarty]

used GitHub UI to fixup conflicts and remove .rst extension from #3723

[moriarty]

@clalancette I've updated the date to match https://twitter.com/OpenRoboticsOrg/status/1666484720585277443

[moriarty]

@moriarty thanks for the contribution.

can you add the following changes?

• .mergify.yml foxy backport rule can be removed. (refer to Mark ROS 2 Galactic as end-of-life #3243)

• ros2_documentation/source/Releases.rst

  Line 52 in 6de7fb9

  .rst-content tr:nth-child(4) {background-color: #33cc66;}

  
  should be removed to turn the background into gray.

• ros2_documentation/source/Releases.rst

  Line 109 in 6de7fb9

  - May 2023

  
  should be updated to exact E.O.L date.

I Applied your feedback, could you re-review?

[clalancette]

@Mergifyio backport foxy

[mergify]

backport foxy

✅ Backports have been created

• #3752 Foxy is now EOL (backport #3700) has been created for branch foxy