Switching Early Access Space to be the Production Space

This page explains the process of changing an existing Early Access space to become the Production space (i.e. making the "upcoming" version the "current" version, at the time of the GA release).

Outside the scope of this procedure:
From time to time, a new Early Access space needs to be created - this process is not covered on this page - see Creating a New Early Access Version of the Documentation for details.

Switching the Early Access documentation space to become the Production Space, involves the following steps (to be done in this order):

The following steps are all written with the example of switching the 7.1.X Early Access space to be the Production space, instead of the current version 7.0.X., (and a new Early Access version 8.0). The same process applies however, whatever the version number of the new Production space.

Edit the Current Version Home Pages (XAP and XAP.NET)

STEP 1: Change the Footer

  1. For each Home page of the current version (e.g. XAP 7.0 and XAP.NET 7.0), click Space>Pages. The List Pages Tree View opens.
  2. Go to the Internal pages, and open the Footer page, which is under the Navigation page.
  3. Change the footer to show that this is now an old version of GigaSpaces XAP. The exact text that you should enter in the footer is shown as follows:
    IMPORTANT: This is an old version of GigaSpaces XAP. Click here for the latest version.
    Note that the link to the latest product version will be wrong until the default space page is changed.

Change the Early Access Version Pages (XAP and XAP.NET)

STEP 2: Edit the Home Page Title and Quick Links

  1. For each space of the Early Access version (there are currently two spaces, one for Java and one for .NET), go to the Home page (e.g. XAP 7.1 and XAP.NET 7.1), and click Edit.
  2. Remove the words Early Access from the page title, which is found in the first h1. heading e.g. h1. XAP 7.1 Early Access Documentation becomes h1. XAP 7.1 Documentation and h1. XAP.NET 7.1 Early Access Documentation becomes h1. XAP.NET 7.1 Documentation .
  3. Delete the Early Access Program and Milestones Quick Links - e.g. delete h5. • [Early Access Program|RN:GigaSpaces Early Access Program] and h5. • [7.1.X Milestones|RN:GigaSpaces 7.1.X Early Access].

STEP 3: Edit the Space Details (Change the Breadcrumbs)

  1. For each space, under Space, click Space Admin.
  2. Click Edit Space Details.
  3. Remove the words Early Access from the first box on the page, which is the space Name e.g. XAP 7.1 Early Access Documentation becomes XAP 7.1 Documentation and XAP.NET 7.1 Early Access Documentation becomes XAP.NET 7.1 Documentation.

STEP 4: Change the Footer

  1. For each space/Home page of the Early Access version e.g. XAP 7.1 and XAP.NET 7.1, click Space>Pages. The List Pages Tree View opens.
  2. Go to the Internal pages, and open the Footer page, which is under the Navigation page.
  3. Change the footer to show that this is now the current version of GigaSpaces XAP. The exact text that you should enter in the footer is shown as follows (using the example of XAP 7.1 becoming the Production version):
    This documentation refers to product version 7.1

STEP 5: Remove all New in X.X.X images from the Early Access version XAP and XAP.NET pages

  1. Search for the image name in the left hand Search box. Generally, searching for newin shows all the pages where there is an orange New in X.X.X star or banner. However, you may need to search for newinX, NewInX, and NewinX !! e.g. newin7, so that pages with the string newin e.g. newinstance dont show up. You should also search for newX, NewX e.g. new7, New7 since some images are labelled this way.
  2. Go to each page that shows up in the search, and edit the page to remove the star or banner.
  3. Look also at the text near the star or banner - e.g. if it says New in 7.1.1 is the ability to..., this also needs to be deleted.

Update the Release Note Pages

STEP 6: Update the GigaSpaces Release Notes page

  1. Go to http://www.gigaspaces.com/wiki/display/RN/GigaSpaces+Release+Notes
  2. There is a list of product versions on this page. Remove the words Early Access from the Early Access version title e.g. GigaSpaces 7.1.X (Early Access) becomes GigaSpaces 7.1.X.

STEP 7: Update the GigaSpaces Early Access Program page

  1. Go to http://www.gigaspaces.com/wiki/display/RN/GigaSpaces+Early+Access+Program.
  2. Update the version number in the second blue info box e.g.
    The latest early access version is XAP 7.1.X.

    becomes

    The next early access version is XAP 8.0, which will be made available in the coming weeks.

STEP 8: Update the GigaSpaces X.X.X Early Access page

  1. Go to the existing Early Access page of the version you want to switch to Production status e.g. http://www.gigaspaces.com/wiki/display/RN/GigaSpaces+7.1.X+Early+Access.
  2. Change the first note to show that this page now only relates to previous milestones of the new GA version. e.g.
    This page relates to the Early Access release of GigaSpaces 7.1.X only. A new Early Access version will be available soon.

    becomes

    This page relates to previous 7.1.X milestones only. If you are interested in GigaSpaces 7.1.X GA, see the Release Notes or Download. A new Early Access version will be available soon.
    The download link to the latest product version will be wrong until the developers change the download links to the new Production version.
  3. Add RC2 to the first heading e.g. h1. GigaSpaces XAP 7.1.X becomes h1. GigaSpaces XAP 7.1.X RC2.
  4. Change the text under the first heading:
    GigaSpaces XAP 7.1.X is an Early Access release. becomes GigaSpaces XAP 7.1.X RC2 is a milestone release of version 7.1.X of GigaSpaces' product line.
  5. Remove the second sentence under the first heading, which starts with With this Early Access version, you'll get a taste of what's coming.....

STEP 9: Update the GigaSpaces X.X.X Release Notes page

  1. Go to the existing Release Notes page of the Early Access version you want to switch to Production status e.g. http://www.gigaspaces.com/wiki/display/RN/GigaSpaces+7.1.X+Release+Notes
  2. In the first blue info box, add the build version of the GA e.g. The latest version is 7.1.0 b4300 released on April 14th, 2010.
  3. Change the download link, so that the user is directed to the GigaSpaces website latest product version download e.g. [Download GigaSpaces 7.1|GigaSpaces 7.1.X Early Access] becomes [Download GigaSpaces 7.1|http://www.gigaspaces.com/LatestProductVersion].
  4. Change the following info about what version to use for compiling:
    When upgrading any GigaSpaces version (including previous 7.1.X milestones) to version 7.1.X, compile your application code with the latest 7.1.X milestone.
    becomes
    When upgrading any GigaSpaces version (including previous 7.1.X milestones) to version 7.1.X, compile your application code with the 7.1.0 b4300 version.

STEP 10: Update the What's New in GigaSpaces X.X.X page

  1. Go to the existing What's New in GigaSpaces page of the Early Access version you want to switch to Production status e.g. http://www.gigaspaces.com/wiki/display/RN/What's+New+in+GigaSpaces+7.1.X.
  2. Remove any info about the target date for release e.g.
    1. Summary: This page overviews the new and noteworthy features in GigaSpaces XAP 7.1.X branch. The target date for this release is the end of Q1 2010.

      becomes

      Summary: This page overviews the new and noteworthy features in GigaSpaces XAP 7.1.X branch.
    2. Version 7.1 will include becomes Version 7.1 includes.
    3. GA is expected at the end of Q1 2010 is removed.
  3. Add any relevant info about the GA release e.g.
    Version 7.1 Released!

    The first GA release of this branch, 7.0.0 b4300, has been released on April 14, 2010. You can download it here.

    • You can read our official release announcement here.
    • You may also find it useful to watch the following Webinar, hosted by Nati Shalom, GigaSpaces CTO, and Uri Cohen, product manager, which explains the concepts and details of the elastic data grid capabilities:

Other Steps

STEP 11: Update the Quick Links on the SBP Home Page

  1. Go to the Solutions and Best Practices home page. http://www.gigaspaces.com/wiki/display/SBP/Solutions+and+Best+Practices+Home
  2. Update the Release Notes and What's New in XAP Quick Links e.g.
    [7.0.X Release Notes|RN:GigaSpaces 7.0.X Release Notes]
    [What's new in XAP 7.0|RN:What's New in GigaSpaces 7.0.X]
    becomes
    [7.1.X Release Notes|RN:GigaSpaces 7.1.X Release Notes]
    [What's new in XAP 7.1.X|RN:What's New in GigaSpaces 7.1.X]

STEP 12: Edit the Choose a GigaSpaces Version page

  1. Go to http://www.gigaspaces.com/wiki/display/ALL/Choose+a+GigaSpaces+Version
  2. Remove the words Early Access from the versions you want to be the Production versions e.g.
    [XAP 7.1 Early Access|XAP71:7.1 Documentation Home] - For Java and C++ users
    becomes
    [XAP 7.1|XAP71:XAP 7.1 Documentation Home] - For Java and C++ users
    and
    [XAP.NET 7.1 Early Access|XAP71NET:XAP.NET 7.1 Documentation Home] - For Java and C++ users
    becomes
    [XAP.NET 7.1|XAP71NET:XAP.NET 7.1 Documentation Home] - For Java and C++ users

STEP 13: Update the Google and Internal Wiki Site Maps

See Procedure for updating Google Site Map
and Procedure for Updating Internal Wiki Site Map

WIKI UPDATES ON THE DAY OF THE GA RELEASE

The next steps will make the latest version documentation live and everyone will view it by default. Before you do that, make sure the new space, particularly its homepage, has all the right content and no embarrassing errors or omissions. WAIT UNTIL THE DAY OF THE GA RELEASE TO MAKE THESE CHANGES!

STEP 14: Remove Navigation Links to old versions

  1. Place the mouse over your name, and click Administration. The Confluence Administration page opens (you have to be a Confluence Administrator to do this).
    Becoming a Confluence Administrator
    If you are not currently a Confluence Administrator, ask whoever already is, to give you this permission. They can do this by putting the mouse over their name, and clicking Administration. They should then click Manage Users and Show all users. From the user list, they need to select your username, then click Edit groups. In the left hand list, click Confluence-Administrators and Join. This includes you in the list of Confluence Administrators.
  2. Click Layouts, then click Edit in the Main Layout box. The Edit Site Layouts>Main Layout box opens.
  3. Copy the entire contents of this box to Notepad++ and save into a new file so that you have the original, and a copy to work on.
    Changes are made to the copy in Notepad++, and then pasted into the site layout box. This avoids editing the site layout box directly, which tends to cause errors if left open too long.
  4. In Notepad++, go to the section labelled NEW GLOBAL NAV.
  5. Remove the first two lines (one for each space of the current product version) e.g. remove
    #if ($spaceKey == "XAP7")<b>#end<a href="$req.contextPath/display/XAP71/" class="version-link">XAP 7</a>#if ($spaceKey == "XAP7")</b>#end  | 
    #if ($spaceKey == "XAP7NET")<b>#end<a href="$req.contextPath/display/XAP71NET/" class="version-link">XAP.NET 7</a>#if ($spaceKey == "XAP7NET")</b>#end  | 
  6. This removes the navigation links for the current version (e.g. XAP7.0 and XAP.NET 7.0) at the top of each documentation page, leaving only links to the new product versions (e.g. XAP7.1 and XAP.NET 7.1), the Cloud products, and All Versions.
  7. Make sure that the navigation links to the new versions do not include the letters EA e.g. change class="version-link">XAP 7.1 EA to class="version-link">XAP 7.1.

STEP 15: Change the Default page/space of the Wiki so that Users See the New Version by default

  1. Go to the Confluence Administration Console by clicking on your name > Administration. (You must be a Confluence Administrator to do this. If you are not, see above on how to become one.)
  2. Click on General Configuration in the nav bar.
  3. Under Site Configuration, click Edit.
  4. From the Site Homepage dropdown, select the space of the new version. For example, if the new version is XAP 7.1, and the space key is XAP71, select XAP71 from the dropdown. This way anyone who visits the wiki will go to the home page of the XAP71 space by default.
    We generally set the Java space of the latest version, NOT the .NET space, as the default space of the wiki.
  5. Scroll to the bottom of the page and click Save.
  6. Send an e-mail to marketing with the following text (inserting the correct version name and space key):
    Subject: Links from corporate website to new documentation version on the wiki
    
    To all concerned at marketing,
    
    We have just updated the documentation wiki, so that the new version of the product, [INSERT NAME OF NEW VERSION], is now the default documentation version. All previous versions are now considered out of date. This e-mail is to inform you what needs to be done to ensure that the corporate website does not link to old pages on the outdated version of the documentation.
    
    You do not need to be concerned about links from the corporate website to the wiki documentation in general, because these links go to the wiki root, http://www.gigaspaces.com/wiki, which automatically points users to the new version. However, you *do* need to change any links from the corporate site to *specific documentation pages*. 
    
    For each of these links, you need to do the following:
    1. Edit the link
    2. The URL is structured like this: http://www.gigaspaces.com/wiki/display/XAP71/Page+Name -- in this example "XAP71" is the space key. You need to replace this with the space key for the new version, which is [INSERT SPACE KEY OF NEW VERSION] -- so in this example, the updated URL will be http://www.gigaspaces.com/wiki/display/XAP8/Page+Name [UPDATE THE SPACE KEY IN THE PRECEDING EXAMPLE]
    3. Now click the new link and see if the page exists. Usually it will exist. If not, see if the wiki suggests a page with a very similar name in the new product version. If so, click through to that page, copy its link, and use that on the site. If you can't find a similar page, the page you are linking to is deprecated and you should remove it from the corporate site.
    
    Here is a partial list of places on the site which might be affected:
    * "documentation" items in the main menu
    * "read more" in the xap page (when you click each of the tabs and scroll down, there is a "read more" section)
    * Go in-depth tabs related to documentation, tutorials or examples, on the following pages: /xap, /cloud, /datagrid, /j2ee, /oem
    * In the developer zone dashboard, the link to "Tutorials and Screencasts".
    
    
    Regards,
    Product team
    

STEP 16: Change the Latest Product Version Download on the Website

The developers need to provide the download links for the new Product version, and have them placed on the company website.

STEP 17: Change the Automatic Redirect pages

  1. Update the default redirection when accessing the dashboard of the wiki.
    1. Go to the Wiki dashboard page, which is http://www.gigaspaces.com/wiki/display/GEN/Wiki+Dashboard.
    2. Update the redirection macro to the latest release.
  2. Update the default redirection when accessing a page that does not exist.
    When you try to go to a page that does not exist, the Wiki redirects you to the current documentation Home page. This needs to be changed to redirect to the new Home page - e.g. to go to http://www.gigaspaces.com/wiki/display/XAP71/7.1+Documentation+Home, instead of http://www.gigaspaces.com/wiki/display/XAP7/7.0+Documentation+Home.
    1. Log in to the server using ssh.
    2. Edit the file /opt/j2ee/domains/gigaspaces.com/www/test/webapps/atlassian-confluence/deployments/current/exploded_war/404.vm and change the first two lines to reflect the new default version (you need root permissions for that).

Labels

 
  1. Jan 23

    Anonymous says:

    Difference Between Coaching And Mentoring And this that I have at missile Alvare...

    Difference Between Coaching And Mentoring And this that I have at missile Alvarez for a while ago.Shoe exterior locality 49 to inhale new new oxygen apertures, details reveals spending water vapor (the leatherbased component belonging in the main heading of your top and center constituents belonging however heading in the toes furthermore opened apertures, glimpse Figure 1). http://tropicalconsulting.com/OutletStore/?Page=Beaver+Coach He likes the dispute and he likes a great amount of danger and game and suspense.Applying simplified criminal rules of practice in electronic format, revised manual of court procedures, and refreshed investigation modes, computerization, digitalization of crime records might help to enhance speedy justice system. Coach Shortline KGWVFvVyTI

  2. Mar 04

    Anonymous says:

    discount christian louboutin shoes with red bottoms cheap louboutin shoes ...
  3. Mar 10

    Anonymous says:

    michael kors handbags outlet onlinereplica cheap purses fake michael kors purses...
  4. Mar 11

    Anonymous says:

    escarpins louboutin pas cher louboutin pas cher homme louboutin homme pas ch...
  5. Mar 28

    Anonymous says:

    cheap replica michael kors handbagscheap knock off michael kors watchesmichael k...

    cheap replica michael kors handbagscheap knock off michael kors watchesmichael kors bags outlet philippinescheap imitation michael kors watchescheap fake michael kors shoes http://t.cn/8sVuMjY http://126.am/sRxFJ0 http://985.so/wBD http://126.am/RXYvb3 http://t.cn/8sVufqBbRaBsqNLzt

  6. Apr 18

    Anonymous says:

    discount michael kors bags When talking about any occupation either online or of...

Add Comment