diff --git a/development/plans/freeze_plan_4_26.php b/development/plans/freeze_plan_4_26.php
new file mode 100644
index 0000000..8c9dec7
--- /dev/null
+++ b/development/plans/freeze_plan_4_26.php
@@ -0,0 +1,215 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
+
+<?php  																														require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/app.class.php");	require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/nav.class.php"); 	require_once($_SERVER['DOCUMENT_ROOT'] . "/eclipse.org-common/system/menu.class.php"); 	$App 	= new App();	$Nav	= new Nav();	$Menu 	= new Menu();		include($App->getProjectCommon());    # All on the same line to unclutter the user's desktop'
+
+	#*****************************************************************************
+	#
+	# index.php
+	#
+	# Author: 		Sravan Kumar Lakkimsetti
+	# Date:			2022-11-08
+	#
+	# Description: Eclipse project 4.26 release freeze plan
+	#
+	#
+	#****************************************************************************
+	
+	#
+	# Begin: page-specific settings.  Change these. 
+	$pageTitle 		= "Eclipse 2022-12 (4.26) Endgame Plan";
+	$pageKeywords	= "eclipse, 4.26, 2022-12, milestone, schedule, endgame";
+	$pageAuthor		= "Sravan Kumar Lakkimsetti";
+	
+	# Add page-specific Nav bars here
+	# Format is Link text, link URL (can be http://www.someothersite.com/), target (_self, _blank), level (1, 2 or 3)
+	# $Nav->addNavSeparator("My Page Links", 	"downloads.php");
+	# $Nav->addCustomNav("My Link", "mypage.php", "_self", 3);
+	# $Nav->addCustomNav("Google", "http://www.google.com/", "_blank", 3);
+
+	# End: page-specific settings
+	#
+		
+	# Paste your HTML content between the markers!
+ob_start();
+?>		
+	<style type="text/css">
+		table.schedule td {font-weight:bold; padding-left:10px;}
+		table.schedule td.date {font-weight:normal; }
+		table.schedule td.spacer {padding-top:10px; padding-bottom:10px; }
+		table.schedule tr.current td {
+			background-color: #F4EEFF;
+		}
+	</style>
+
+	<div id="midcolumn">
+		<h1><?= $pageTitle ?></h1>
+		<div class="homeitem3col">
+			<h3>Status</h3>
+			<p><b>Two daily I-builds towards RC1</b></p>
+      	</div>
+		<div class="homeitem3col">
+			<h3>Detailed Timeline</h3>
+	        <table class="schedule" border="0" cellspacing="0" align="center" width=100%>
+	          <tr>
+	            <td>November 2022</td>
+	          </tr>
+	          <tr>
+	            <td></td>
+	            <td></td>
+	            <td></td>
+	            <td></td>
+	            <td>Two daily I-builds towards RC1</td>
+	            <td></td>
+	          </tr>
+			  <tr>
+	            <td class="spacer">&nbsp;</td>
+	          </tr>
+	          <tr>
+	            <td></td>
+	            <td class="date">16</td>
+	            <td class="date">Wed 18:00 ET</td>
+	            <td></td>
+	            <td>API and feature freeze</td>
+	            <td></td>
+	          </tr>
+	          <tr>
+	            <td></td>
+	            <td class="date">16</td>
+	            <td class="date">Wed 18:00 ET</td>
+	            <td></td>
+	            <td>Release Candidate 1 build</td>
+	            <td></td>
+	          </tr>
+	          <tr>
+	            <td></td>
+	            <td class="date">18</td>
+	            <td class="date">Fri</td>
+	            <td></td>
+	            <td>Submit RC1 to release train</td>
+	            <td></td>
+	          </tr>
+	          <tr>
+	            <td></td>
+	            <td class="date">25</td>
+	            <td class="date">Wed 18:00 ET</td>
+	            <td></td>
+	            <td>Release Candidate 2 build</td>
+	            <td></td>
+	          </tr>
+	          <tr>
+	            <td></td>
+	            <td class="date">26</td>
+	            <td class="date">Thu</td>
+	            <td></td>
+	            <td>1-day test pass against RC2 and sign-off</td>
+	            <td></td>
+	          </tr>
+	          <tr>
+	            <td></td>
+	            <td class="date">27</td>
+	            <td class="date">Fri</td>
+	            <td></td>
+	            <td>Submit RC2 to release train</td>
+	            <td></td>
+	          </tr>
+	          <tr>
+	            <td>December 2022</td>
+	          </tr>
+	          <tr>
+	            <td class="spacer">&nbsp;</td>
+	          </tr>
+			  <tr class="current">
+	            <td></td>
+	            <td class="date">07</td>
+	            <td class="date">Wed</td>
+	            <td></td>
+	            <td>GA</td>
+	            <td></td>
+	          </tr>
+	        </table>
+      	</div>
+		<div class="homeitem3col">
+			<h3>Useful Links</h3>
+			<ul>
+			<li><a href="http://www.eclipse.org/eclipse/platform-releng/buildSchedule.html">Build Schedule</a> - details on build times.</li>
+			<li><a href="http://wiki.eclipse.org/Eclipse/Release_checklist">Eclipse Release Checklist</a> - lists various things that need to be checked before each release.</li>
+			<li><a href="https://www.eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/development/plans/eclipse_project_plan_4_26.xml">Eclipse Project 4.26 Plan</a></li>
+			<li><a href="https://wiki.eclipse.org/Category:SimRel-2022-12">2022-12 Simultaneous Release</a></li>
+			</ul>
+      	</div>
+		<div class="homeitem3col">
+			<h3>What is the game plan?</h3>
+			<p> 
+	 		The Eclipse 2022-12 (4.26) release endgame involves building 
+	        a series of release candidates leading to the Eclipse project's contribution to the
+	        2022-12 (4.26) release. The Eclipse project version number for this release is 4.26.
+			As always, we welcome help from the 
+	        community with testing the release candidates. All new features and problems fixed in 2022-12 (4.26) are in the Eclipse github database.
+	        </p> 
+
+	        <p>General announcements during the 2022-12 (4.26) endgame are posted to the 
+	        <a href="http://dev.eclipse.org/mailman/listinfo/platform-releng-dev">platform-releng-dev@eclipse.org</a> 
+		    developer mailing list. Anyone participating in the endgame should be subscribed 
+			to this list, and should direct any general questions and comments about the process 
+			there as well.</p>
+			
+			<strong>API change approval</strong>
+	        <p>
+			No API changes are expected after RC1. Any exception must be
+			approved by the PMC. No changes are to be released without prior approval
+			and associated bug report. Please send the request for approval to the eclipse-pmc
+			mailing list. If a change is made to API to make it binary compatible with
+			a previous release, technically this is still an API change, and thus it should be treated
+			in the same way as any other API change requests.	
+			</p>
+
+			<strong>Feature work approval</strong>
+	        <p>
+			Any feature work after RC1 must be approved by the PMC. No changes are to be released without prior approval
+			and associated bug report. Please send the request for approval to the eclipse-pmc
+			mailing list.
+			</p>
+
+
+		   <strong>RC1</strong>
+		   <p>
+		   All fixes submitted must have a project lead or PMC vote on the bug report,
+		   and the fix must be reviewed by an additional committer (any committer other than
+		   the one who made the fix). A positive review from a project lead or PMC member means
+		   implicit approval and no vote is needed on the bug report.
+		   Ongoing changes to documentation, tests or examples do not require approval.
+		   </p>
+
+		   <strong>RC2</strong>
+		   <p>
+	        Release candidate containing fixes for the majority of known outstanding 
+	        defects that we intend to fix for 2022-12 (4.26). At the end of RC2 build, 
+	        there should not be any open defects tagged 4.26. All fixes submitted 
+	        must have a project lead or PMC vote on the bug report,
+	        and the fix must be reviewed by an additional committer (any committer other than
+	        the one who made the fix). A positive review from a project lead or PMC member means
+		    implicit approval and no vote is needed on the bug report.
+		    Ongoing changes to documentation, tests or examples do not require approval.
+	        </p>      
+	
+	        <strong>Test pass using RC2</strong>
+	        <p>Concerted 1-day testing effort using RC2 involving entire community including 
+	        all component teams. The goal is to verify all the fixes and check for any regressions.
+			</p>
+	
+			<strong>2022-12 (4.26) Release</strong>
+			<p>The 2022-12 (4.26) release should be complete and available for download by 
+	              December 07, 2022 as part of the <a href="https://wiki.eclipse.org/Category:SimRel-2022-12">2022-12 Simultaneous Release</a>. If product teams intending 
+	              to ship on 2022-12 (4.26) uncover further serious defects during the endgame, 
+	              we may schedule additional release candidate builds to incorporate fixes.
+			</p>    
+		</div>
+	</div>
+
+<?php
+	$html = ob_get_contents();
+	ob_end_clean();
+
+	# Generate the web page
+	$App->generatePage($theme, $Menu, $Nav, $pageAuthor, $pageKeywords, $pageTitle, $html);
+?>