geronimo-scm mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r893032 [21/21] - in /websites/production/geronimo/content: GMOxPMGT/ cache/
Date Mon, 06 Jan 2014 18:52:27 GMT
Modified: websites/production/geronimo/content/GMOxPMGT/release-manager-checklist.html
==============================================================================
--- websites/production/geronimo/content/GMOxPMGT/release-manager-checklist.html (original)
+++ websites/production/geronimo/content/GMOxPMGT/release-manager-checklist.html Mon Jan 
6 18:52:26 2014
@@ -84,20 +84,19 @@
 
       <div class="pagecontent">
         <div class="wiki-content">
-          <div class="wiki-content maincontent"><h3><a shape="rect" name="ReleaseManagerChecklist-MilestoneEntry"></a>Milestone
Entry</h3>
+          <div class="wiki-content maincontent"><h3 id="ReleaseManagerChecklist-MilestoneEntry">Milestone
Entry</h3>
 
-<ul class="alternate" type="square"><li>Clearly declare a milestone release mgr
at beginning of the milestone.</li><li>Post to the devlist the target delivery
schedule of the milestone.&#160;&#160; Get consensus from the community early.</li><li>Nail
the must-have function from the community that is required to be delivered in this milestone.</li><li>Target
(or reTarget) all of the Jira defects and new function that is required for the milestone.&#160;
Move non-critical items to the next milestone early.</li></ul>
+<ul class="alternate"><li>Clearly declare a milestone release mgr at beginning
of the milestone.</li><li>Post to the devlist the target delivery schedule of
the milestone.&#160;&#160; Get consensus from the community early.</li><li>Nail
the must-have function from the community that is required to be delivered in this milestone.</li><li>Target
(or reTarget) all of the Jira defects and new function that is required for the milestone.&#160;
Move non-critical items to the next milestone early.</li></ul>
 
 
-<h3><a shape="rect" name="ReleaseManagerChecklist-MilestoneMiddle"></a>Milestone
Middle</h3>
+<h3 id="ReleaseManagerChecklist-MilestoneMiddle">Milestone Middle</h3>
 
-<ul class="alternate" type="square"><li>Keep Jiras under control during the milestone.&#160;&#160;
Make sure new opened ones are targeted for the appropriate milestone, and the backlog is decreasing.</li><li>Make
sure the new function Jira are marked appropriately (since they will be used in the ReadMe
file creation).</li><li>Look for Jira's that have patches attached to them and
get the code integrated early in the cycle.&#160;&#160; Don't wait until the last
minute.</li><li>Make sure that you begin to obtain clean versions for all SNAPSHOTs
in the build.&#160; This can sometimes be a lengthy process as dependent packages are
sometimes not available.</li><li>Double check that the TCK machines are ready
for executing the TCK.&#160;&#160; Lay out a plan for the distributed execution of
the suite.</li><li>Now is the time to ensure that all of the licenses are valid
and replacements/remediation should be done.</li><li>Declare a candidate build
to the community.</li><li>Make sure that y
 ou remind the community that all modules should have the appropriate header file with the
appropriate copyright statement. <a shape="rect" class="external-link" href="http://www.apache.org/legal/src-headers.html#headers">http://www.apache.org/legal/src-headers.html#headers</a></li></ul>
+<ul class="alternate"><li>Keep Jiras under control during the milestone.&#160;&#160;
Make sure new opened ones are targeted for the appropriate milestone, and the backlog is decreasing.</li><li>Make
sure the new function Jira are marked appropriately (since they will be used in the ReadMe
file creation).</li><li>Look for Jira's that have patches attached to them and
get the code integrated early in the cycle.&#160;&#160; Don't wait until the last
minute.</li><li>Make sure that you begin to obtain clean versions for all SNAPSHOTs
in the build.&#160; This can sometimes be a lengthy process as dependent packages are
sometimes not available.</li><li>Double check that the TCK machines are ready
for executing the TCK.&#160;&#160; Lay out a plan for the distributed execution of
the suite.</li><li>Now is the time to ensure that all of the licenses are valid
and replacements/remediation should be done.</li><li>Declare a candidate build
to the community.</li><li>Make sure that you remind the 
 community that all modules should have the appropriate header file with the appropriate copyright
statement. <a shape="rect" class="external-link" href="http://www.apache.org/legal/src-headers.html#headers">http://www.apache.org/legal/src-headers.html#headers</a></li></ul>
 
 
-<h3><a shape="rect" name="ReleaseManagerChecklist-MilestoneExit"></a>Milestone
Exit</h3>
+<h3 id="ReleaseManagerChecklist-MilestoneExit">Milestone Exit</h3>
 
-<ul class="alternate" type="square"><li>Declare a candidate build for the TCK
testing to the community and work any issues that are voiced.</li><li>Update the
Readme file with the important New Function and Total defects.&#160;&#160; Put the
delivery date of the milestone in the top of the readme.</li><li>Ensure that tooling
is verified with the specific milestone candidate build (late changes can break tooling, don't
ignore this step).</li><li>Double check to make sure that the Graphical Installer
works with the build candidate.</li><li>Get some to verify that all of the samples
pass without issues.</li><li>Complete TCK testing for the build (this normally
can take 2-3 weeks).</li><li>Near the end of the TCK testing, create a new branch
in the build tree for the milestone.&#160; Remind the community that only milestone defects
should be integrated to that branch.</li><li>Declare the TCK testing has been
completed, and request for a vote from the community to make this build public.
 &#160;&#160; Allow at least 3 days for the vote to complete.</li><li>After
3 days, summarize the vote and declare the milestone build as the public milestone build.</li><li>Make
approved build available in source and binary form.&#160; Declare this to the community
with excitement <img align="middle" class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/smile.gif"
height="20" width="20" alt="" border="0">.</li><li>Create Service Branch for
the milestone or release (if appropriate).</li><li>Post a congratulation note
to the devlist thanking the entire team, and calling out any extraordinary efforts that were
done to make it happen.</li></ul>
-</div>
+<ul class="alternate"><li>Declare a candidate build for the TCK testing to the
community and work any issues that are voiced.</li><li>Update the Readme file
with the important New Function and Total defects.&#160;&#160; Put the delivery date
of the milestone in the top of the readme.</li><li>Ensure that tooling is verified
with the specific milestone candidate build (late changes can break tooling, don't ignore
this step).</li><li>Double check to make sure that the Graphical Installer works
with the build candidate.</li><li>Get some to verify that all of the samples pass
without issues.</li><li>Complete TCK testing for the build (this normally can
take 2-3 weeks).</li><li>Near the end of the TCK testing, create a new branch
in the build tree for the milestone.&#160; Remind the community that only milestone defects
should be integrated to that branch.</li><li>Declare the TCK testing has been
completed, and request for a vote from the community to make this build public.&#160;&#160;
A
 llow at least 3 days for the vote to complete.</li><li>After 3 days, summarize
the vote and declare the milestone build as the public milestone build.</li><li>Make
approved build available in source and binary form.&#160; Declare this to the community
with excitement <img class="emoticon emoticon-smile" src="https://cwiki.apache.org/confluence/s/en_GB-1988229788/4109/76e0dbb30bc8580e459c201f3535d84f9283a9ac.1/_/images/icons/emoticons/smile.png"
data-emoticon-name="smile" alt="(smile)">.</li><li>Create Service Branch for
the milestone or release (if appropriate).</li><li>Post a congratulation note
to the devlist thanking the entire team, and calling out any extraordinary efforts that were
done to make it happen.</li></ul></div>
         </div>
 
         

Modified: websites/production/geronimo/content/GMOxPMGT/unassigned-jiras.html
==============================================================================
--- websites/production/geronimo/content/GMOxPMGT/unassigned-jiras.html (original)
+++ websites/production/geronimo/content/GMOxPMGT/unassigned-jiras.html Mon Jan  6 18:52:26
2014
@@ -18,6 +18,17 @@
 
     <script src="http://geronimo.apache.org/functions.js" type="text/javascript"></script>
 
+  <link href='http://geronimo.apache.org/resources/highlighter/styles/shCoreGeronimo.css'
rel='stylesheet' type='text/css' />
+  <link href='http://geronimo.apache.org/resources/highlighter/styles/shThemeGeronimo.css'
rel='stylesheet' type='text/css' />
+  <script src='http://geronimo.apache.org/resources/highlighter/scripts/shCore.js' type='text/javascript'></script>
+  <script src='http://geronimo.apache.org/resources/highlighter/scripts/shBrushJava.js'
type='text/javascript'></script>
+  <script src='http://geronimo.apache.org/resources/highlighter/scripts/shBrushXml.js'
type='text/javascript'></script>
+  <script src='http://geronimo.apache.org/resources/highlighter/scripts/shBrushPlain.js'
type='text/javascript'></script>
+  
+  <script type="text/javascript">
+  SyntaxHighlighter.defaults['toolbar'] = false;
+  SyntaxHighlighter.all();
+  </script>
 
     <title>Apache Geronimo Project Management : Unassigned JIRAs</title>
 

Modified: websites/production/geronimo/content/cache/GMOxPMGT.pageCache
==============================================================================
Binary files - no diff available.



Mime
View raw message