14.0: truncate the schedule for the upcoming release

An updated 14.0-RELEASE schedule is being discussed, and following
no objections and/or concerns, should be expected to be made public
within the next few days.

Sponsored by:	GoFundMe https://www.gofundme.com/f/gjbbsd

2 files changed, 13 insertions, 13 deletions

diff --git a/website/content/en/releases/14.0R/schedule.adoc b/website/content/en/releases/14.0R/schedule.adoc
index bd449139ce..aa1f72fcfe 100644
--- a/website/content/en/releases/14.0R/schedule.adoc
+++ b/website/content/en/releases/14.0R/schedule.adoc
@@ -33,18 +33,18 @@ Announcements regarding the availability of the ALPHA snapshots will be sent to
 |===
 |Action |Expected |Actual |Description
 |Initial release schedule announcement |- |19 August 2022 |Release Engineers send announcement email to developers with a rough schedule.
-|Release schedule reminder |17 April 2023|17 April 2023 |Release Engineers send reminder announcement e-mail to developers with updated schedule.
-|Code slush begins / KBI freeze |25 April 2023 |delayed |Release Engineers announce that all further commits to the {localBranchHead} branch will not require explicit approval, however new features should be avoided. Additionally, there can be no changes to the KBI until {localBranchHead} is branched to {localBranchStable}.
-|{localBranchStable} branch |12 May 2023 |- |{localBranchStable} branch created; release engineering continues on this branch.
-|{localBranchReleng} branch |26 May 2023 |- |{localBranchReleng} branch created; future release engineering proceeds on this branch. Commits to this branch require explicit approval from the Release Engineers.
-|BETA1 builds begin |26 May 2023 |- |First beta test snapshot.
-|BETA2 builds begin |2 June 2023 |- |Second beta test snapshot.
-|BETA3 builds begin* |9 June 2023 |- |Third beta test snapshot.
-|RC1 builds begin |16 June 2023 |- |First release candidate.
-|RC2 builds begin |23 June 2023 |- |Second release candidate.
-|RC3 builds begin* |7 July 2023 |- |Third release candidate.
-|RELEASE builds begin |14 July 2023 |- |{localRel}-RELEASE builds begin.
-|RELEASE announcement |17 July 2023 |- |{localRel}-RELEASE press release.
+|Release schedule reminder |- |- |Release Engineers send reminder announcement e-mail to developers with updated schedule.
+|Code slush begins / KBI freeze |- |- |Release Engineers announce that all further commits to the {localBranchHead} branch will not require explicit approval, however new features should be avoided. Additionally, there can be no changes to the KBI until {localBranchHead} is branched to {localBranchStable}.
+|{localBranchStable} branch |- |- |{localBranchStable} branch created; release engineering continues on this branch.
+|{localBranchReleng} branch |- |- |{localBranchReleng} branch created; future release engineering proceeds on this branch. Commits to this branch require explicit approval from the Release Engineers.
+|BETA1 builds begin |- |- |First beta test snapshot.
+|BETA2 builds begin |- |- |Second beta test snapshot.
+|BETA3 builds begin* |- |- |Third beta test snapshot.
+|RC1 builds begin |- |- |First release candidate.
+|RC2 builds begin |- |- |Second release candidate.
+|RC3 builds begin* |- |- |Third release candidate.
+|RELEASE builds begin |- |- |{localRel}-RELEASE builds begin.
+|RELEASE announcement |- |- |{localRel}-RELEASE press release.
 |Turn over to the secteam |- |- |{localBranchReleng} branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement.
 |===
 
diff --git a/website/content/en/releng/_index.adoc b/website/content/en/releng/_index.adoc
index 45cc3b6e6e..c4643c1cfc 100644
--- a/website/content/en/releng/_index.adoc
+++ b/website/content/en/releng/_index.adoc
@@ -32,7 +32,7 @@ Note: Release dates are approximate and may be subject to schedule slippage.
 [cols=",,",options="header",]
 |===
 |Date |Event |Information
-|July 2023 |FreeBSD 14.0 |link:../releases/14.0R/schedule/[Target Schedule]
+|TBD (schedule should be available soon) |FreeBSD 14.0 |link:../releases/14.0R/schedule/[Target Schedule]
 |===
 
 [[freeze]]