Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

Updated CHANGELOG for 1.1.0rc3

  • Loading branch information...
commit e786ea368e989c4a0dd15ae502f4cb45fa52c435 1 parent 2d4d3da
Jacob Helwig authored
Showing with 13 additions and 4 deletions.
  1. +4 −0 CHANGELOG
  2. +4 −4 README.markdown
  3. +5 −0 RELEASE_NOTES.md
4 CHANGELOG
View
@@ -1,3 +1,7 @@
+v1.1.0rc3
+=========
+2d4d3da Updated VERSION for 1.1.0rc3
+
v1.1.0rc2
=========
af1a006 (#6835) Handle malformed facts from Puppet 2.6.7 & storedconfigs
8 README.markdown
View
@@ -95,13 +95,13 @@ Installation
git clone git://github.com/puppetlabs/puppet-dashboard.git
cd puppet-dashboard
- git checkout v1.1.0rc1
+ git checkout v1.1.0rc3
3. Download the most recent release of Puppet Dashboard, extract it and move it to your install location (this may be different on your system). This options makes upgrading more difficult since you'll have to manually manage files when upgrading, but may be a good option if you want to avoid repository setup or using git and just want to try out dashboard.
- wget http://puppetlabs.com/downloads/dashboard/puppet-dashboard-1.1.0rc1.tar.gz
- tar -xzvf puppet-dashboard-1.1.0rc1.tar.gz
- mv puppet-dashboard-1.1.0rc1 /usr/share/puppet-dashboard
+ wget http://puppetlabs.com/downloads/dashboard/puppet-dashboard-1.1.0rc3.tar.gz
+ tar -xzvf puppet-dashboard-1.1.0rc3.tar.gz
+ mv puppet-dashboard-1.1.0rc3 /usr/share/puppet-dashboard
2. Create a `config/database.yml` file to specify Puppet Dashboard's database configuration. Please see the `config/database.yml.example` file for further details about database configurations and environments. These files paths are relative to the path of the Puppet Dashboard software containing this `README.markdown` file.
5 RELEASE_NOTES.md
View
@@ -1,6 +1,11 @@
Puppet Dashboard Release Notes
==============================
+v1.1.0rc3
+---------
+
+* Updated VERSION for 1.1.0rc3
+
v1.1.0rc2
---------
Please sign in to comment.
Something went wrong with that request. Please try again.