Refreshes the Gitlab Releases page

README.md

@@ -47,9 +47,9 @@ properties.
 [How to update the comparison pages.](doc/features.md#create-or-update-the-comparison-pages-under-comparison)
-### Update the release list page (under `/release-list`)
-[How to update the release list page.](doc/release-list.md)
+### Update the releases page (under `/releases`)
+[How to update the releases page.](doc/releases.md)
 ### Update the projects page (under `/handbook/engineering/projects`)
@@ -83,12 +83,12 @@ The above command builds the static files and PDFs into the folder `public`.
 There are a few custom, static generators specified in `config.rb`. For
 example, there are generators that produce the direction issue list,
-release list, and organization chart dynamically.
+releases list, and organization chart dynamically.
 These pages cannot be viewed directly via the Middleman server
 (e.g. http://localhost:4567) because there are explicit rules that
 tell Middleman to defer the generation to other scripts. These
-special URLs (e.g. /release-list/index.html) usually have two
+special URLs (e.g. /releases/index.html) usually have two
 Middleman keywords:
 1. [`proxy`](https://middlemanapp.com/advanced/dynamic_pages/)
@@ -133,7 +133,7 @@ Beware that:
   deploy a Review App (hence MRs from contributors). For that case, you should
   have at least Developer access to the `www-gitlab-com` project or
   `gitlab-com` group.
-- The generation of the direction, wishlist and release list pages is omitted
+- The generation of the direction, wishlist and releases pages is omitted
   in branches and is run only on master. This helps to shave off some time from
   the build process. That means you won't be able to preview these pages with
   Review Apps.
@@ -151,13 +151,13 @@ internet connection available.
    ```
    git clone git@gitlab.com:gitlab-com/www-gitlab-com.git
    ```
-   
+
 2. Create a Docker container
    ```
    docker create --name middleman -v "$PWD/www-gitlab-com":/site -w /site -p 4567:4567 \
      -e LC_ALL=C.UTF-8 ruby /bin/bash -c 'bundle install && bundle exec middleman'
    ```
-   
+
 3. Start the container
    ```
    docker start middleman
@@ -168,7 +168,7 @@ internet connection available.
 5. Change your original content as usual, and see the changes in the browser as soon as
 you save the new version of the file (otherwise, just restart the container)
-6. When you have finished, stop the container 
+6. When you have finished, stop the container
    ```
    docker stop middleman
    ```

config.rb

 require 'generators/direction'
-require 'generators/release_list'
+require 'generators/releases'
 require 'generators/org_chart'
 require 'extensions/breadcrumbs'
 require 'lib/homepage'
@@ -65,7 +65,7 @@ configure :build do
   activate :minify_javascript
   activate :minify_html
-  # Populate the direction and release list pages only on master.
+  # Populate the direction and releases pages only on master.
   # That will help shave off some time of the build times on branches.
   if ENV['CI_BUILD_REF_NAME'] == 'master' || !ENV.key('CI_BUILD_REF_NAME')
     ## Direction page
@@ -73,9 +73,9 @@ configure :build do
       proxy "/direction/index.html", "/direction/template.html", locals: { direction: generate_direction, wishlist: generate_wishlist }, ignore: true
     end
-    ## Release list page
+    ## Releases page
     releases = ReleaseList.new
-    proxy "/release-list/index.html", "/release-list/template.html", locals: { list: releases.generate }, ignore: true
+    proxy "/releases/index.html", "/releases/template.html", locals: { list: releases.generate }, ignore: true
   end
 end
@@ -109,7 +109,7 @@ page '/404.html', directory_index: false
 ignore '/direction/template.html'
 ignore '/includes/*'
-ignore '/release-list/template.html'
+ignore '/releases/template.html'
 ignore '/team/structure/org-chart/template.html'
 ignore '/source/stylesheets/highlight.css'
 ignore '/category.html'

doc/release-list.md → doc/releases.md

-# Update the release list page (under `/release-list`)
-The release list page grabs its content automatically by crawling the blog and
+# Update the releases page (under `/releases`)
+The releases page grabs its content automatically by crawling the blog and
 retrieving the headers from the blog post.
-Edit `/generators/release_list.rb` and modify two elements:
+Edit `/generators/releases.rb` and modify two elements:
 1. Add the new version to the table listing the versions
     ```
@@ -25,4 +25,4 @@ the 22th is 8.12, the month should be 8 (i.e August for 8.11), not 9.
 3. Commit the changes.
-The release-list page will be updated after `bundle exec rake build`.
+The releases page will be updated after `bundle exec rake build`.

generators/release_list.rb → generators/releases.rb

@@ -4,12 +4,14 @@ require 'yaml'
 # Don't generate for versions prior to 8.0
 CUTOFF = Date.new(2015, 9, 22)
-# Generates the Markdown used by the `/release-list/` page based on monthly
+# Generates the Markdown used by the `/releases/` page based on monthly
 # release blog posts in this repository
 class ReleaseList
   def generate(output = StringIO.new)
     release_posts.each do |post|
-      output.puts "## [#{post.version}](#{post.relative_url})"
+      output.puts "## [GitLab #{post.version}](#{post.relative_url})"
+      output.puts "#{post.date.to_time.strftime '%A, %B %e, %Y'}"
+      output.puts "{: .date}"
       output.puts
       post.highlights.each do |highlight|

source/category.html.haml

@@ -3,12 +3,14 @@ layout: default
 ---
 - content_for :title do
   = categories.to_s.capitalize
-.blog-index.blog-entry
-  %ul.post-list
-    - page_articles.each do |post|
-      %li.post-list-item
-        = link_to post.url do
-          = post.title
-        - if post.date
-          %time
-            = post.date.to_time.strftime '%b %e, %Y'
+.blog.archives
+  .wrapper
+    .section
+      %ul
+        - page_articles.each do |post|
+          %li
+            = link_to post.url do
+              = post.title
+            - if post.date
+              %time
+                = post.date.to_time.strftime '%b %e, %Y'

source/direction/template.html.md.erb

@@ -37,7 +37,7 @@ or two months.
 ## Previous releases
-On our [release list page](/release-list/) you can find an overview of the most
+On our [releases page](/releases/) you can find an overview of the most
 important features of recent releases and links to the blog posts for each
 release.

source/handbook/marketing/blog/release-posts/index.html.md

@@ -32,7 +32,7 @@ category [release](/blog/categories/release/).
 - For a list of security releases, please check
 the category [security release](/blog/categories/security-release/).
 - For a list of features per release, please check
-the [release list](/release-list/).
+the [releases](/releases/).
 - For all named changes, please check the changelog
 for [GitLab CE](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG.md)
 and [GitLab EE](https://gitlab.com/gitlab-org/gitlab-ee/blob/master/CHANGELOG.md).

source/includes/layout/footer.html.haml

@@ -27,6 +27,7 @@
           %li= link_to('Community Edition',  '/downloads')
           %li= link_to('GitLab.com',         '/gitlab-com/')
           %li= link_to('Pricing',  '/products')
+          %li= link_to('Releases',  '/releases')
       .col-sm-6.col-md-3.col-lg-2.footer-link-holder
         %h3.footer-link-title Services
         %ul.animated.footer-links

source/posts/2017-03-22-gitlab-9-0-released.html.md

@@ -18,7 +18,7 @@ extra_js:
 <section class="release-post-section">
-Today we are releasing **GitLab 9.0**, 18 months after [releasing 8.0](/2015/09/22/gitlab-8-0-released/). We've made [significant advances to GitLab during this period](/release-list/), shipping a version every single month on the 22nd. Let's quickly recap how far we've come since 8.0, and see those features dovetailing into today's 9.0 release. Or [jump ahead](#subgroups-ce-ee) to 9.0 features.
+Today we are releasing **GitLab 9.0**, 18 months after [releasing 8.0](/2015/09/22/gitlab-8-0-released/). We've made [significant advances to GitLab during this period](/releases/), shipping a version every single month on the 22nd. Let's quickly recap how far we've come since 8.0, and see those features dovetailing into today's 9.0 release. Or [jump ahead](#subgroups-ce-ee) to 9.0 features.
 <!-- more -->
@@ -52,7 +52,7 @@ We've continued to improve code review and code collaboration in GitLab since 8.
 ### Continuous Integration
-[8.0](/2015/09/22/gitlab-8-0-released/#continuous-integration-in-gitlab) was a pivotal release as it fully integrated continuous integration (CI) into GitLab itself. Subsequently, new CI features were implemented into the API ([8.4](/2016/01/22/gitlab-8-4-released/#new-ci-features-in-api)) and pipeline events were exposed through webhooks ([8.11](/2016/08/22/gitlab-8-11-released/#pipelines-web-hooks)). Pipelines were also integrated into merge requests ([8.11](/2016/08/22/gitlab-8-11-released/#pipelines-in-mrs), [8.17](/2017/02/22/gitlab-8-17-released/#additional-pipeline-details-included-in-merge-request-workflow)) and commits ([8.13](/2016/10/22/gitlab-8-13-released/#pipelines-for-commits)), as well as its own visual graph ([8.11](/2016/08/22/gitlab-8-11-released/#pipelines-graph)). GitLab runner was improved in every release from [8.10 to 8.17](/release-list/). We released review apps ([8.12](/2016/09/22/gitlab-8-12-released/#review-apps-experimental), [8.13](/2016/10/22/gitlab-8-13-released/#ability-to-stop-review-apps), [8.14](/2016/11/22/gitlab-8-14-released/#review-apps)) and auto deploy ([8.15](/2016/12/22/gitlab-8-15-released/#auto-deploy)) to automatically deploy code into automatically created environments. And now with GitLab 9.0, we are shipping [deploy boards](#deploy-boards-eep), allowing you track how your app is being deployed to multiple servers.
+[8.0](/2015/09/22/gitlab-8-0-released/#continuous-integration-in-gitlab) was a pivotal release as it fully integrated continuous integration (CI) into GitLab itself. Subsequently, new CI features were implemented into the API ([8.4](/2016/01/22/gitlab-8-4-released/#new-ci-features-in-api)) and pipeline events were exposed through webhooks ([8.11](/2016/08/22/gitlab-8-11-released/#pipelines-web-hooks)). Pipelines were also integrated into merge requests ([8.11](/2016/08/22/gitlab-8-11-released/#pipelines-in-mrs), [8.17](/2017/02/22/gitlab-8-17-released/#additional-pipeline-details-included-in-merge-request-workflow)) and commits ([8.13](/2016/10/22/gitlab-8-13-released/#pipelines-for-commits)), as well as its own visual graph ([8.11](/2016/08/22/gitlab-8-11-released/#pipelines-graph)). GitLab runner was improved in every release from [8.10 to 8.17](/releases/). We released review apps ([8.12](/2016/09/22/gitlab-8-12-released/#review-apps-experimental), [8.13](/2016/10/22/gitlab-8-13-released/#ability-to-stop-review-apps), [8.14](/2016/11/22/gitlab-8-14-released/#review-apps)) and auto deploy ([8.15](/2016/12/22/gitlab-8-15-released/#auto-deploy)) to automatically deploy code into automatically created environments. And now with GitLab 9.0, we are shipping [deploy boards](#deploy-boards-eep), allowing you track how your app is being deployed to multiple servers.
 ### Feedback and Insight

source/release-list/template.html.md.erb

----
-layout: markdown_page
-title: List of all GitLab releases
----
-
-<%= list %>
-
-[See the changelog archive for changes before 8.0.](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/changelogs/archive.md)

source/releases/template.html.md.erb

+---
+layout: markdown_page
+title: GitLab releases
+---
+
+For a list of release posts including patch releases, please check the blog category [release](/blog/categories/release/).
+
+<%= list %>
+
+---
+
+Please check out the changelog to see all the named changes:
+- [GitLab Community Edition](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG.md)
+- [GitLab Enterprise Edition](https://gitlab.com/gitlab-org/gitlab-ee/blob/master/CHANGELOG.md)
+- [GitLab Runner](https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/blob/master/CHANGELOG.md)
+
+Changes prior to GitLab 8.0 can be seen [here](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/changelogs/archive.md)