Location: /localsite//hudson/project-info/hudson-release-plan.xml
Meta-data Tag: projectplanurl
Raw:

	<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<?xml-stylesheet type="text/xsl" href="http://www.eclipse.org/projects/project-plan.xsl"?>
<plan plan-format="1.0" xmlns="http://www.eclipse.org/project/plan"
	xmlns:html="http://www.w3.org/1999/xhtml" name="Project Name">
	<release projectid="technology.hudson" version="3.0.0" />
	<introduction>
		<html:div>
			This plan covers the transition of the core of the Hudson Project into Eclipse and 
			covers both non-Eclipse and Eclipse versions for completeness. Once 
			<html:strong>3.0.0</html:strong>
		</html:div>
	</introduction>
	<release_deliverables>
		<html:div>
			The Hudson deliverables for any particular release are are:
			<html:ul>
				<html:li>The Hudson WAR file representing the actual Hudson tool
				</html:li>
				<html:li>O/S Specific installers for the WAR file</html:li>
				<html:li>Key Plug-ins compatible with Hudson 3.0 (maintained and down-loaded on demand from outside of Eclipse) including: 
					<html:ul>
					    <html:li>Birt Support for Charting</html:li>
					    <html:li>JNA Native Access Support</html:li>
					    <html:li>XPATH Provider</html:li>
					    <html:li>Groovy Support</html:li>
						<html:li>GIT Source Control</html:li>
						<html:li>Subversion Source Control</html:li>
						<html:li>CVS Source Control</html:li>
						<html:li>SSH Slave Management</html:li>
						<html:li>Rest Support</html:li>
						<html:li>Legacy Maven 2 support</html:li>
						<html:li>Maven 3 support</html:li>
					</html:ul>
				</html:li>
				<html:li>Infrastructure and web-site updates as required</html:li>
			</html:ul>
		</html:div>
	</release_deliverables>
	<release_milestones>
		<preamble>
			<html:div>The Milestones below represent the transition period
				leading up to the first Eclipse release. The dates for the regular
				Hudson production releases are predictable. The dates for the
				Eclipse-Hudson releases will be dependent on the IP process around
				the initial code contribution.
			</html:div>
		</preamble>
		<milestone date="8/30/2011" milestone="Hudson 2.1.1">
			<html:div>Regular Hudson production release (5 week cycle) - Non
				Eclipse
			</html:div>
		</milestone>
		<milestone date="10/06/2011" milestone="Hudson 2.1.2">
			<html:div>Regular Hudson production release (5 week cycle) - Non
				Eclipse
			</html:div>
		</milestone>
		<milestone date="12/09/2011" milestone="Hudson 2.2.0">
			<html:div>Regular Hudson production release (5 week cycle) - Non
				Eclipse
			</html:div>
		</milestone>		
		<milestone date="01/15/2012" milestone="Eclipse-Hudson 3.0.0M0">
			<html:div>Initial internal proving milestone release of Hudson from the
				Eclipse Infrastructure 
			</html:div>
		</milestone>
		<milestone date="02/17/2012" milestone="Eclipse-Hudson 3.0.0M1">
			<html:div>Internal milestone 1 for Hudson 3.0.0 release
			</html:div>
		</milestone>
		<milestone date="05/31/2012" milestone="Hudson 2.2.1">
			<html:div>Regular Hudson production release (delayed) - Non
				Eclipse
			</html:div>
		</milestone>		
		<milestone date="04/20/2012" milestone="Eclipse-Hudson 3.0.0M2">
			<html:div>Internal milestone 2 for Hudson 3.0.0 release
			</html:div>
		</milestone>		
		<milestone date="06/19/2012" milestone="Eclipse-Hudson 3.0.0M3">
			<html:div>Internal milestone 3 for Hudson 3.0.0 release
			</html:div>
		</milestone>	
		<milestone date="07/30/2012" milestone="Eclipse-Hudson 3.0.0M4">
			<html:div>Milestone 4 for Hudson 3.0.0 release - (Feature Freeze)
			</html:div>
		</milestone>	
		<milestone date="08/21/2012" milestone="Eclipse-Hudson 3.0.0RC2">
			<html:div>Release Candidate milestone for Hudson 3.0.0
			</html:div>
		</milestone>
		<milestone date="12/21/2012" milestone="3.0.0">
			<html:div>First full production release of Hudson (3.0.0) at Eclipse
			</html:div>
		</milestone>
		<milestone milestone="3.0.1">
			<html:div>First regular patchset release
			</html:div>
		</milestone>
		<milestone milestone="3.1.0">
			<html:div>Next feature bearing release (for planning purposes)
			</html:div>
		</milestone>		
		<postamble>
			<html:div>
				Schedule for Hudson 3.0.0 releases is based on monthly bugfix patches (patch release) and quarterly feature bearing releases (minor release). Hudson version numbering is as follows [Major Release].[Minor Release].[Patch Release]
			</html:div>
		</postamble>
	</release_milestones>
	<target_environments>
		<html:div>
			Hudson is a Java EE application which will run a variety of Java EE containers. The following distributions are targeted:
			<html:ul>
                <html:li>Generic (WAR) distribution for any O/S</html:li>		
				<html:li>Ubuntu / Debian</html:li>
				<html:li>openSUSE</html:li>
				<html:li>Oracle Enterprise Linux</html:li>
				<html:li>Red Hat / Fedora / CentOS</html:li>
                <html:li>Generic WAR + Common Plugins distribution for any O/S</html:li>		
			</html:ul>
		</html:div>
		<internationalization>
			<html:div>The Hudson project endevors to support multiple languages
				and has the infrastructure in the code to support translations given
				contributions from the community.
			</html:div>
		</internationalization>
	</target_environments>
	<compatibility_with_previous_releases>
		<html:div>The Hudson project aims to ensure plug-in compatibilty with
			earlier releases, however, upgrade to Hudson 3.0.0 from an earlier version is a significant step for organizations and should be undertaken with a suitable job and environment backup strategy in place. 
		</html:div>
	</compatibility_with_previous_releases>
	<themes_and_priorities>
		<preamble>
			<html:div>These are the current themes in play for the Eclipse 3.0.0 realease and next few beyond that as discussed at the public Hudson meeting on Aug-15 2011. The intent is to revisit and revise these and prioritize as appropriate once Hudson 3.0.0 is released. 
			</html:div>
		</preamble>
		<theme name="Performance / Memory Management">
			<description>
				<html:div>We need to review the way that Hudson holds it's internal Memory model to optimize the memory usage on large, enterprise systems 
				</html:div>
			</description>
		</theme>
		<theme name="Improved Class-loading Strategy">
			<description>
				<html:div>We need to develop a more sofisticated classloader infrastructure that can allow plugins to ship with their full set of requirements, rather than having Hudson Core polluted with JARs that it does not use directly  
				</html:div>
			</description>
		</theme>		
		<theme name="Project Visualization">
			<description>
				<html:div>Add diagrammatic visualization of a project's build steps
					and provision for cross project orchestration
				</html:div>
			</description>
		</theme>
		<theme name="UI Technology Modernization">
			<description>
				<html:div>Migration away from Jelly onto a more standard technology
					such as Facelets and or JSF and clean up and modernization of the UI generally.
				</html:div>	
			</description>
		</theme>
		<theme name="Enterprise Support">
			<description>
				<html:div>
					One of the stated aims of Hudson is to provide the power and
					stability demmanded of a tool that is going to be used in a large
					enterprise environment. Several additional feature areas bolster
					this aim:
					<html:ul>
						<html:li>Performance
						</html:li>					
						<html:li>Improvements of LDAP, Active Directory and other SSO
							technologies
						</html:li>
						<html:li>Tools to manage complex build pipelines e.g. cascading
							project setup inheritance and others
						</html:li>
						<html:li>Support for text markup beyond html to improve security
							and usability
						</html:li>
					</html:ul>
				</html:div>
			</description>
		</theme>
		<theme name="More Native Installer Support">
			<description>
				<html:div>Although platforms such as Windows and Mac OS/X are
					supported very well using the generic WAR file install it would be
					good to produce a set of native installers for these platforms as
					well
				</html:div>
			</description>
		</theme>
		<theme name="Enterprise Groups">
			<description>
				<html:div>An additional feature area in the enterprise space, but large enough to justify a theme of it's own. This will cover the whole area of resource management in an single enterprise wide instance of Hudson that is used by multiple teams with different resource constraints and security requirements. We'll need to consider job partitioning, resource throttling and many other features related to this
				</html:div>
			</description>
		</theme>
	</themes_and_priorities>
	<!--appendix name="Eclipse Migration">
		<html:div>
			The issues around migration to Eclipse are covered in the
			<html:a href="http://wiki.eclipse.org/hudson-ci">Eclipse Hudson Wiki</html:a>
		</html:div>
	</appendix-->
</plan>