NewRelease - Revision history

Infrastation: /* updating demo */ use "git add -p"

2022-02-16T13:06:39Z

updating demo: use "git add -p"

Infrastation: The CI was Travis, but it isn't anymore.

2022-02-15T20:30:27Z

The CI was Travis, but it isn't anymore.

Infrastation: /* updating demo */ I had retired Google Analytics from this job a while ago.

2020-10-05T18:03:18Z

updating demo: I had retired Google Analytics from this job a while ago.

Infrastation: /* updating demo */ add a missing parameter

2019-11-17T20:56:30Z

updating demo: add a missing parameter

Infrastation: /* producing and publishing deliverables */ SF downloads no longer have buttons

2019-11-17T20:52:06Z

producing and publishing deliverables: SF downloads no longer have buttons

Infrastation: /* producing and publishing deliverables */ remove unnecessary export

2019-11-17T20:28:22Z

producing and publishing deliverables: remove unnecessary export

Infrastation: /* part 1 */ simplify the git command

2019-06-12T14:12:09Z

part 1: simplify the git command

Infrastation: /* part 1 */ fixup some language

2019-06-12T13:51:32Z

part 1: fixup some language

Infrastation: /* part 2 (unit testing) */ also run the large group of tests

2017-10-28T15:05:12Z

part 2 (unit testing): also run the large group of tests

Infrastation: /* updating the main web-site */ update the steps after the switch from SF

2017-10-05T16:46:03Z

updating the main web-site: update the steps after the switch from SF

@@ Line 131: / Line 131: @@
 ** Make an SQL dump of this new installation like this: <tt>mysqldump --extended-insert=FALSE --order-by-primary racktables_db > init-full-X.Y.z.sql</tt>
 ** Edit permissions like [https://github.com/RackTables/racktables-contribs/commit/0354001ce16e937cfc5ae555fe73dc3c351a6556 this].
-** <tt>git add -i</tt> the new file again (note interactive add). Use patch mode to add relevant chunks. Quit.
+** <tt>git add -p</tt> the new file again (note the flag). Add relevant chunks only. Quit.
 ** <tt>git commit; git push</tt>
 * Update demo.racktables.org to the current release (<tt>$demorelease</tt> will need an update). Below is a sample CLI session of updating the demo to 0.20.3:

@@ Line 30: / Line 30: @@
 </pre></li>
-<li>The application must be able to install itself using its own installer (only some of the involved code is in the Travis CI script). Once this is found working, dump the database:
+<li>The application must be able to install itself using its own installer (only some of the involved code is in the CI script). Once this is found working, dump the database:
 <pre>
 mysqldump --extended-insert=FALSE --order-by-primary racktables_db > ~/tmp/dump-fresh.sql
 </pre></li>
-<li>Demo data must be loadable without any errors (this is likely to be OK since this check is now in the Travis CI script):
+<li>Demo data must be loadable without any errors (this is likely to be OK since this check is now in the CI script):
 <pre>
 mysql racktables_db < scripts/init-sample-racks.sql

@@ Line 141: / Line 141: @@
 ln -s racktables RackTables-0.20.3
 # the symlink to ~/secret.php is already in wwwroot/inc/
 cd ~/racktables-contribs/
 git pull

@@ Line 145: / Line 145: @@
 git pull
 cd
-~/racktables-contribs/demo.racktables.org/demoreload.sh 0.20.3 rackdemo
+~/racktables-contribs/demo.racktables.org/demoreload.sh 0.20.3 rackdemo yes
 crontab -e
 # ../../racktables/wwwroot/index.php is already linked as www/demo/index.php
 </pre>

@@ Line 102: / Line 102: @@
 ** Open properties form (round "(i)" sign) of the previous release tar.gz.
 ** Unset all "default download for" checkboxes.
 ** Save.
 ** Open properties form (round "(i)" sign) of the previous release zip.
 ** Unset Windows "default download for" checkbox.
 ** Save.
 ** In the latest tarball properties form, set all "default download for" checkboxes except Windows.
 ** Save.
 ** In the latest zipfile properties form, set Windows "default download for" checkbox.
 ** Save.
 ** Hover the big green "download" button and watch the mouse hint featuring the right version number (sometimes it takes several minutes to see the update).

@@ Line 94: / Line 94: @@
 * Make two archives:
 <pre>
-export TAG='RackTables-X.Y.z'
+TAG='RackTables-X.Y.z'
 git archive --prefix=$TAG/ -o $TAG.tar.gz $TAG
 git archive --prefix=$TAG/ -o $TAG.zip $TAG

@@ Line 18: / Line 18: @@
 <li>Produce a commit with all changes pending thus far:
 <pre>
-git status
+git add ChangeLog wwwroot/inc/config.php
 git commit
 </pre>

@@ Line 1: / Line 1: @@
 == pre-release checklist ==
 === part 1 ===
-First make sure that all necessary changes are already committed into the repository:
+Make sure all necessary changes have been committed into the repository:
 <ul>
-<li>Make sure you have the right branch checked out and that no pending changes are in the working copy:
+<li>Make sure you have the right branch checked out and no pending changes are in the working copy:
 <pre>
 git status
@@ Line 12: / Line 12: @@
 <li>Update <tt>ChangeLog</tt> file to have the current date on the to-be version line.</li>
-<li>Make sure that <tt>upgrade.php</tt> has the to-be version listed in <tt>$versionhistory</tt> and <tt>getUpgradeBatch()</tt>. It is normal to accumulate updates in <tt>getUpgradeBatch()</tt> long before the release, this way on the release day you will have nothing to do in <tt>upgrade.php</tt>. But if you had no changes to DB since the last release, you are likely to see there changes missing. Just make sure the new version is in both places anyway.</li>
+<li>Make sure <tt>upgrade.php</tt> has the to-be version listed in <tt>$versionhistory</tt> and <tt>getUpgradeBatch()</tt>. It is normal to accumulate updates in <tt>getUpgradeBatch()</tt> long before the release, this way on the release day you will have nothing to do in <tt>upgrade.php</tt>. But if you had no changes to DB since the last release, you are likely to see there changes missing. Just make sure the new version is in both places anyway.</li>
 <li>Bump up <tt>CODE_VERSION</tt> in <tt>wwwroot/inc/config.php</tt>. DON'T do this unless you really intend to make a release right now.</li>

@@ Line 72: / Line 72: @@
 <li>Run the unit tests. Fix any failures.</li>
 <pre>
-./tests/express.sh
+cd tests
 </pre>

@@ Line 122: / Line 122: @@
 === updating the main web-site ===
-* Log into SF shell service:
+* In racktables-htdocs repository modify and commit <tt>header.php</tt>.
-<pre>
+* On the web-server run <tt>git pull</tt>.
-$ cat ~/.ssh/config
+* Open https://racktables.org and test the "download" link to work.
 === updating other news feeds ===