EVOLUTION-MANAGER

Edit File: ReleaseGuide.html

<!doctype html>

<html  xml:lang="en" lang="en">
        <head>
    <meta charset="UTF-8" />
    <title>Apache OpenMeetings Project &#x2013; Release Guide</title>
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <meta name="description" content="" />
    <meta name="author" content="Apache OpenMeetings Team" />
      <meta http-equiv="content-language" content="en" />
                                                        <link href="./css/themes/cerulean/bootstrap.min.css" rel="stylesheet" />
    <link href="./css/fontawesome/all.min.css" rel="stylesheet" />
    <link href="./css/reflow-skin.css" rel="stylesheet" />
    
    <link rel="stylesheet" href="./js/styles/github.min.css" />

SET https://github.com/apache/openmeetings/tree/4.0.0
						</pre> 
    </div> </li> 
   <li> Create a TAG and commit it to the Git<br> 
    <div class="source"> 
     <pre>git commit -a -m "4.0.0 Release Candidate 1"
git tag -s 4.0.0-RC1 -m "4.0.0 Release Candidate 1 tag"
git push origin 4.0.0-RC1
						</pre> 
    </div> </li> 
   <li> <p>Deploy release artifacts to Maven</p> 
    <div class="source"> 
     <pre>mvn clean &amp;&amp; mvn deploy -Pdeploy,rc</pre> 
    </div> </li> 
   <li> <p>Run the command: </p> 
    <div class="source"> 
     <pre>mvn clean &amp;&amp; mvn install -PallModules,rc</pre> 
    </div> </li> 
   <li> <p>Test building the source on windows and OSx or Linux</p> <p>Test running the binary's</p> </li> 
   <li> <p> Commit artifacts you have created with KEYS file to the <code>https://dist.apache.org/repos/dist/dev/openmeetings/</code> Proposed file structure for "Release Candidate 1" of 4.0.0 will be: </p> 
    <div class="source"> 
     <pre>4.0.0
4.0.0/rc1
4.0.0/rc1/src
4.0.0/rc1/src/apache-openmeetings-4.0.0-src.zip
4.0.0/rc1/src/apache-openmeetings-4.0.0-src.tar.gz
4.0.0/rc1/src/apache-openmeetings-4.0.0-src.zip.sha
4.0.0/rc1/src/apache-openmeetings-4.0.0-src.zip.asc
4.0.0/rc1/src/apache-openmeetings-4.0.0-src.tar.gz.sha
4.0.0/rc1/src/apache-openmeetings-4.0.0-src.tar.gz.asc
4.0.0/rc1/bin
4.0.0/rc1/bin/apache-openmeetings-4.0.0.zip
4.0.0/rc1/bin/apache-openmeetings-4.0.0.tar.gz
4.0.0/rc1/bin/apache-openmeetings-4.0.0.zip.sha
4.0.0/rc1/bin/apache-openmeetings-4.0.0.zip.asc
4.0.0/rc1/bin/apache-openmeetings-4.0.0.tar.gz.sha
4.0.0/rc1/bin/apache-openmeetings-4.0.0.tar.gz.asc
4.0.0/rc1/CHANGELOG
						</pre> 
    </div> <p><b>NOTE</b> KEYS file is located at https://www.apache.org/dist/openmeetings/KEYS and should be just updated</p> </li> 
  </ul> 
 </section> 
 <section> 
  <h3 id="step2---vote-and-result-emails">Step2 - VOTE and RESULT emails</h3> 
  <p> Send a "VOTE" to the developer mailing list including links to release artifacts.<br> A VOTE always contains two parts:<br> Send an email to the developer mailing list with the subject line:<br> [VOTE] Apache OpenMeetings x.xx release<br> An example for such an email: <a class="externalLink" href="https://mail-archives.apache.org/mod_mbox/openmeetings-dev/201701.mbox/%3CCAJmbs8jZ7EiXoeBbG4ynvg30FPx2nAOJMypE2Qp-v-c63ayO9A%40mail.gmail.com%3E">example Vote email</a> <a class="externalLink" href="https://s.apache.org/vote-2.0.0RC4">example Vote email (Incubator)</a> <br> After the vote is over, send a "RESULT" email to the list with the subject line:<br> [RESULT][VOTE] Apache OpenMeetings x.xx release<br> An example for such an email: <a class="externalLink" href="https://mail-archives.apache.org/mod_mbox/openmeetings-dev/201701.mbox/%3CCAJmbs8gyvHuarzdVma%2BF6ap7RHBhhVciZp5Oi5JogQdLR6o0NA%40mail.gmail.com%3E">example Result email</a> <br> Votes on whether a package is ready to be released use majority approval -- i.e., at least three PMC members must vote affirmatively for release, and there must be more positive than negative votes. Releases may not be vetoed. Before voting +1 PMC members are required to download the signed source code package, compile it as provided, and test the resulting executable on their own platform, along with also verifying that the package meets the requirements of the ASF policy on releases. </p> 
 </section> 
 <section> 
  <h3 id="step3---sign-web-start-application">Step3 - Sign web start application</h3> 
  <p>If VOTEs positive: Sign screen sharing web application and re-pack the release</p> 
  <ul> 
   <li>Go to the folder you check out your $BRANCHORTAG</li> 
   <li> <p>Run the command: </p> 
    <div class="source"> 
     <pre>cd openmeetings-screenshare
mvn clean install -Prc,release
						</pre> 
    </div> </li> 
   <li>Go to <a class="externalLink" href="https://securesigning.pki.digicert.com/csportal">https://securesigning.pki.digicert.com/csportal</a></li> 
   <li>Select "Signing Sets"</li> 
   <li>Select "Add signing set"</li> 
   <li>Enter "Signing set name" (must include "Apache OpenMeetings" and version) for ex. "Apache OpenMeetings 4.0.0-RELEASE"</li> 
   <li>Enter "Version" for ex. "4.0.0-RELEASE"</li> 
   <li>Select "Java Signing Sha256" as "Signing service"</li> 
   <li>Select "Upload files" and add all <b>jar</b> files from <code>target/jnlp</code></li> 
   <li>Select "Sign now"</li> 
   <li>Select "Type of signing" -&gt; "Production"</li> 
   <li>Select "Sign"</li> 
   <li>Select "Download set"</li> 
   <li>Open binary artifacts of OM created on previous step (both <b>tar.gz</b> and <b>zip</b>)</li> 
   <li>Replace jar files inside artifacts <code>webapps/openmeetings/screenshare</code> with the signed ones</li> 
   <li> Re-create artifact signatures <p>Create sha512sum checksums</p> 
    <div class="source"> 
     <pre>#On OSX you might use this command to make a SHA checksum and store it to a file
shasum -a 512 -r apache-openmeetings-XXX-src.zip &gt;apache-openmeetings-XXX-src.zip.sha512
						</pre> 
    </div> 
    <div class="source"> 
     <pre>#To create SHA hashes On Ubuntu:
for f in `ls -1 *.tar.gz *.zip`; do sha512sum $f &gt; $f.sha512; done

#To check SHA hashes On Ubuntu:
for f in `ls -1 *.tar.gz *.zip`; do sha512sum -c $f.sha512; done

</pre> 
    </div> <p> Create signatures with the your KEY for every file, the KEY must be available at:<br> <a class="externalLink" href="https://github.com/apache/openmeetings/blob/master/KEYS"> https://github.com/apache/openmeetings/blob/master/KEYS </a> </p> 
    <div class="source"> 
     <pre>#To create signatures On Ubuntu:
for f in `ls -1 *.tar.gz *.zip`; do gpg --armor --output $f.asc --detach-sig $f; done

#To check signatures On Ubuntu:
for f in `ls -1 *.tar.gz *.zip`; do gpg --verify $f.asc; done

</pre> 
    </div> </li> 
  </ul> 
  <p>NOTE: "Type of signing" can be selected as "Test" to check everything works as expected</p> 
 </section> 
 <section> 
  <h3 id="step4---create-release-tag">Step4 - Create release tag</h3> 
  <p>Release tag based on RCXX should finally be created</p> 
  <div class="source"> 
   <pre>git checkout 5.0.0-M1-RC1
git tag 5.0.0-M1
git push origin 5.0.0-M1

</pre> 
  </div> 
 </section> 
 <section> 
  <h3 id="step5---distribute-and-announce">Step5 - Distribute and announce</h3> 
  <p>If VOTEs positive: Upload the release </p> 
  <ul> 
   <li>Upload Artifacts with signatures created on the previous steps to https://dist.apache.org/repos/dist/release/openmeetings/CURRENT_VERSION </li> 
   <li>Close staging repo: 
    <ul> 
     <li>Go to: <a class="externalLink" href="https://repository.apache.org/#stagingRepositories">Staging Repositories</a></li> 
     <li>Select openmeetings staging repo and Close it with valid message:<br> for ex. "The VOTE about 3.1.2 release was successful" </li> 
     <li>Select openmeetings staging repo and Release it with valid message:<br> for ex. "The VOTE about 3.1.2 release was successful" </li> 
    </ul> </li> 
   <li> Wait 24 hours (until all Apache mirrors have synced the packages) and send an announcement to the mailing list + blog and any other channel. </li> 
   <li> Email announcements should have the subject line:<br> [ANNOUNCE] Apache OpenMeetings x.xx released </li> 
   <li> Update release section of DOAP file <code>openmeetings-site/doap.rdf (https://github.com/apache/openmeetings-site/blob/asf-site/doap.rdf)</code> </li> 
   <li> Add a section to <a href="downloads.html">downloads</a> website.<br> Make sure that the binary packages are linked using the mirror URL as base path ( <b>not</b> http://www.apache.org/dist):<br> Mirror URL: <a class="externalLink" href="http://www.apache.org/dyn/closer.lua/openmeetings/">http://www.apache.org/dyn/closer.lua/openmeetings/</a> </li> 
   <li> Release candidates should be deleted from <code>https://dist.apache.org/repos/dist/dev/openmeetings/</code><br> Old releases should be deleted from <code>https://dist.apache.org/repos/dist/release/openmeetings/</code> </li> 
  </ul> 
 </section> 
</section>        </main>
        <div class="d-none d-sm-none d-md-none d-lg-none d-xl-block col-xl-2">
            <div id="m-toc-sidebar" class="d-print-none m-toc-sidebar-enabled m-toc-sidebar-expanded m-toc-sidebar-autoexpandable toc-sidebar-fixed">
                <nav id="m-toc-sidebar-nav flex-column">
                <ul class="m-nav--sidebar nav flex-column flex-nowrap">
    <li class="h2">
        <a class="nav-link" href="#how-to-build-a-release-of-openmeetings" title="How to Build a Release of OpenMeetings">How to Build a Release of OpenMeetings</a>
    </li>
    <ul class="nav flex-column flex-nowrap nav-collapsible">
            <li class="h3">
        <a class="nav-link" href="#required-tools" title="Required tools">Required tools</a>
    </li>
    <li class="h3">
        <a class="nav-link" href="#prepare-your-apache-id" title="Prepare your Apache ID">Prepare your Apache ID</a>
    </li>
    <li class="h3">
        <a class="nav-link" href="#step1---prepare-files" title="Step1 - Prepare files">Step1 - Prepare files</a>
    </li>
    <li class="h3">
        <a class="nav-link" href="#step2---vote-and-result-emails" title="Step2 - VOTE and RESULT emails">Step2 - VOTE and RESULT emails</a>
    </li>
    <li class="h3">
        <a class="nav-link" href="#step3---sign-web-start-application" title="Step3 - Sign web start application">Step3 - Sign web start application</a>
    </li>
    <li class="h3">
        <a class="nav-link" href="#step4---create-release-tag" title="Step4 - Create release tag">Step4 - Create release tag</a>
    </li>
    <li class="h3">
        <a class="nav-link" href="#step5---distribute-and-announce" title="Step5 - Distribute and announce">Step5 - Distribute and announce</a>
    </li>
    </ul>
                    </ul>
                </nav>
           </div>
        </div>
    </div> 
</div> 
    <div id="m_scrolltop" class="m-scrolltop">
		<i class="fa fa-arrow-up"></i>
    </div>
  
<footer class="footer-light bg-light">
    <div class="container">
        <div class="row">
                        <div class="col bottom-nav">
                <ul class="nav flex-column nav-list">
                    <li class="nav-header">
General
                    </li>
                    <li class="nav-item "><a  href="index.html"  title="Home"  class="nav-link" >Home</a></li>
                    <li class="nav-item "><a  href="https://www.apache.org/licenses/"  title="License"   class="externalLink nav-link" >License</a></li>
                    <li class="nav-item "><a  href="https://www.apache.org/"  title="ASF"   class="externalLink nav-link" >ASF</a></li>
                    <li class="nav-item "><a  href="https://www.apache.org/foundation/sponsorship"  title="Sponsorship"   class="externalLink nav-link" >Sponsorship</a></li>
                    <li class="nav-item "><a  href="https://www.apache.org/foundation/thanks"  title="Thanks"   class="externalLink nav-link" >Thanks</a></li>
                    <li class="nav-item "><a  href="CallForLogo.html"  title="Call For Logo"  class="nav-link" >Call For Logo</a></li>
                    <li class="nav-item "><a  href="NewsArchive.html"  title="News archive"  class="nav-link" >News archive</a></li>
                    <li class="nav-item "><a  href="security.html"  title="Security"  class="nav-link" >Security</a></li>
                    <li class="nav-item "><a  href="commercial-support.html"  title="Commercial Support"  class="nav-link" >Commercial Support</a></li>
                </ul>
            </div>
            <div class="col bottom-nav">
                <ul class="nav flex-column nav-list">
                    <li class="nav-header">
Installation
                    </li>
                    <li class="nav-item "><a  href="installation.html"  title="Installation"  class="nav-link" >Installation</a></li>
                    <li class="nav-item "><a  href="Upgrade.html"  title="Upgrade"  class="nav-link" >Upgrade</a></li>
                    <li class="nav-item "><a  href="InstallMediaServer.html"  title="Media Server Installation"  class="nav-link" >Media Server Installation</a></li>
                    <li class="nav-item "><a  href="https://cwiki.apache.org/confluence/display/OPENMEETINGS/Tutorials+for+installing+OpenMeetings+and+Tools"  title="Tutorials"   class="externalLink nav-link" >Tutorials</a></li>
                    <li class="nav-item "><a  href="CommandLineAdmin.html"  title="Command Line Admin"  class="nav-link" >Command Line Admin</a></li>
                </ul>
            </div>
            <div class="col bottom-nav">
                <ul class="nav flex-column nav-list">
                    <li class="nav-header">
Community
                    </li>
                    <li class="nav-item "><a  href="get-involved.html"  title="Get Involved"  class="nav-link" >Get Involved</a></li>
                    <li class="nav-item "><a  href="team.html"  title="Committers"  class="nav-link" >Committers</a></li>
                    <li class="nav-item "><a  href="OurUsers.html"  title="Our Users"  class="nav-link" >Our Users</a></li>
                    <li class="nav-item "><a  href="mailing-lists.html"  title="Mailing Lists"  class="nav-link" >Mailing Lists</a></li>
                    <li class="nav-item "><a  href="https://cwiki.apache.org/confluence/display/OPENMEETINGS/"  title="Wiki"   class="externalLink nav-link" >Wiki</a></li>
                </ul>
            </div>
            <div class="col bottom-nav">
                <ul class="nav flex-column nav-list">
                    <li class="nav-header">
Development
                    </li>
                    <li class="nav-item "><a  href="scm.html"  title="Source Code"  class="nav-link" >Source Code</a></li>
                    <li class="nav-item "><a  href="issue-management.html"  title="Bugs / Issues"  class="nav-link" >Bugs / Issues</a></li>
                    <li class="nav-item "><a  href="dependencies.html"  title="Dependencies"  class="nav-link" >Dependencies</a></li>
                    <li class="nav-item "><a  href="ci-management.html"  title="Continuous Integration"  class="nav-link" >Continuous Integration</a></li>
                    <li class="nav-item "><a  href="BuildInstructions.html"  title="Build Instructions"  class="nav-link" >Build Instructions</a></li>
                    <li class="nav-item "><a  href="JUnitTesting.html"  title="JUnit Testing"  class="nav-link" >JUnit Testing</a></li>
                    <li class="nav-item "><a  href="ManualTesting.html"  title="Manual Testing"  class="nav-link" >Manual Testing</a></li>
                    <li class="nav-item active"><a  href=""  title="Release Guide"  class="nav-link" >Release Guide</a></li>
                    <li class="nav-item "><a  href="WebsiteGuide.html"  title="Website Guide"  class="nav-link" >Website Guide</a></li>
                </ul>
            </div>
        </div> 
    </div> 
</footer>
  <div class="container subfooter text-center">
    <div class="row">
      <div class="col-md-12">
        <p class="copyright">Copyright &copy;2012-2020
                 <a href="https://apache.org">Apache Software Foundation</a>
. All Rights Reserved.</p>
      </div>
    </div>
  </div>

<script src="./js/jquery.min.js" crossorigin="anonymous"></script>
    <script src="./js/popper.min.js" crossorigin="anonymous"></script>
    <script src="./js/bootstrap.min.js" crossorigin="anonymous"></script>