forked from hardaker/makerelease
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathDOCUMENTATION.html
865 lines (619 loc) · 20.4 KB
/
DOCUMENTATION.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"
lang="en" xml:lang="en">
<head>
<title>Make Release</title>
<meta http-equiv="Content-Type" content="text/html;charset=iso-8859-1"/>
<meta name="generator" content="Org-mode"/>
<meta name="generated" content="2011-02-04 10:19:20 PST"/>
<meta name="author" content="Wes Hardaker"/>
<meta name="description" content=""/>
<meta name="keywords" content=""/>
<style type="text/css">
<!--/*--><![CDATA[/*><!--*/
html { font-family: Times, serif; font-size: 12pt; }
.title { text-align: center; }
.todo { color: red; }
.done { color: green; }
.tag { background-color: #add8e6; font-weight:normal }
.target { }
.timestamp { color: #bebebe; }
.timestamp-kwd { color: #5f9ea0; }
p.verse { margin-left: 3% }
pre {
border: 1pt solid #AEBDCC;
background-color: #F3F5F7;
padding: 5pt;
font-family: courier, monospace;
font-size: 90%;
overflow:auto;
}
table { border-collapse: collapse; }
td, th { vertical-align: top; }
dt { font-weight: bold; }
div.figure { padding: 0.5em; }
div.figure p { text-align: center; }
textarea { overflow-x: auto; }
.linenr { font-size:smaller }
.code-highlighted {background-color:#ffff00;}
.org-info-js_info-navigation { border-style:none; }
#org-info-js_console-label { font-size:10px; font-weight:bold;
white-space:nowrap; }
.org-info-js_search-highlight {background-color:#ffff00; color:#000000;
font-weight:bold; }
/*]]>*/-->
</style>
<script type="text/javascript">
<!--/*--><![CDATA[/*><!--*/
function CodeHighlightOn(elem, id)
{
var target = document.getElementById(id);
if(null != target) {
elem.cacheClassElem = elem.className;
elem.cacheClassTarget = target.className;
target.className = "code-highlighted";
elem.className = "code-highlighted";
}
}
function CodeHighlightOff(elem, id)
{
var target = document.getElementById(id);
if(elem.cacheClassElem)
elem.className = elem.cacheClassElem;
if(elem.cacheClassTarget)
target.className = elem.cacheClassTarget;
}
/*]]>*///-->
</script>
</head>
<body>
<div id="content">
<h1 class="title">Make Release</h1>
<div id="table-of-contents">
<h2>Table of Contents</h2>
<div id="text-table-of-contents">
<ul>
<li><a href="#sec-1">1 Project Details </a></li>
<li><a href="#sec-2">2 Introduction and History </a>
<ul>
<li><a href="#sec-2_1">2.1 Release Pain </a></li>
<li><a href="#sec-2_2">2.2 The solution: makerelease </a></li>
</ul>
</li>
<li><a href="#sec-3">3 Usage </a>
<ul>
<li><a href="#sec-3_1">3.1 Step by Step </a></li>
<li><a href="#sec-3_2">3.2 Structured in XML </a></li>
<li><a href="#sec-3_3">3.3 makerelease -n: dry-run and produce documentation </a></li>
<li><a href="#sec-3_4">3.4 makerelease: </a></li>
</ul>
</li>
<li><a href="#sec-4">4 Writing Steps </a>
<ul>
<li><a href="#sec-4_1">4.1 Global Attributes and Data </a>
<ul>
<li><a href="#sec-4_1_1">4.1.1 <text>foo</text> </a></li>
<li><a href="#sec-4_1_2">4.1.2 title="Title for the Step" </a></li>
<li><a href="#sec-4_1_3">4.1.3 stepname="name" </a></li>
<li><a href="#sec-4_1_4">4.1.4 pause="true" </a></li>
</ul>
</li>
<li><a href="#sec-4_2">4.2 Step Types </a>
<ul>
<li><a href="#sec-4_2_1">4.2.1 Informational </a></li>
<li><a href="#sec-4_2_2">4.2.2 Section </a></li>
<li><a href="#sec-4_2_3">4.2.3 Include </a></li>
<li><a href="#sec-4_2_4">4.2.4 Command </a></li>
<li><a href="#sec-4_2_5">4.2.5 Prompt </a></li>
<li><a href="#sec-4_2_6">4.2.6 Modify </a></li>
<li><a href="#sec-4_2_7">4.2.7 Perl </a></li>
</ul></li>
</ul>
</li>
<li><a href="#sec-5">5 Examples </a>
<ul>
<li><a href="#sec-5_1">5.1 Projects that are making use of makerelease scripts </a></li>
<li><a href="#sec-5_2">5.2 Included example scripts </a></li>
</ul>
</li>
</ul>
</div>
</div>
<div id="outline-container-1" class="outline-2">
<h2 id="sec-1"><span class="section-number-2">1</span> Project Details </h2>
<div class="outline-text-2" id="text-1">
<p class="verse">
Download: <a href="http://github.com/hardaker/makerelease">only via GIT on github right now</a><br/>
</p>
</div>
</div>
<div id="outline-container-2" class="outline-2">
<h2 id="sec-2"><span class="section-number-2">2</span> Introduction and History </h2>
<div class="outline-text-2" id="text-2">
</div>
<div id="outline-container-2_1" class="outline-3">
<h3 id="sec-2_1"><span class="section-number-3">2.1</span> Release Pain </h3>
<div class="outline-text-3" id="text-2_1">
<p>
One of the issues with releasing software is that you need to do
mind-numbing tasks over and over and it is a barrier to "release
early, release often". Not only that, releasing a particular
package becomes an art-form to do all the right steps in the right
order without forgetting anything.
</p>
<p>
The result of this problem is usually one of:
</p>
<ol>
<li>
1-2 knowledgeable people and if they perished someone else
would be bound to repeat the undocumented mistakes they made.
</li>
<li>
A hand-crafted shell script of some kind that automates at
least some of the tasks. (somewhere in the middle there is
invariably a human step that needs to be done that requires "do
this and press enter".)
</li>
<li>
Documentation describing the release-steps that need to be performed.
</li>
</ol>
<p>
For projects I've worked on in the past, there is often been all
three. The scripts get you "so far" but there is still a lot of
operator knowledge. Sometimes that knowledge is encoded into a
documentation file, but I've found that typically the
documentation lags behind the script, the expert operator or both.
</p>
</div>
</div>
<div id="outline-container-2_2" class="outline-3">
<h3 id="sec-2_2"><span class="section-number-3">2.2</span> The solution: makerelease </h3>
<div class="outline-text-3" id="text-2_2">
<p>
It is, of course, impossible to take <b>all</b> the fun out of the
process and make everything totally automated. The goal of
makerelease is a few fold:
</p>
<ul>
<li>
Ensure the documentation and the automated systems are combined
and thus always in sync
</li>
<li>
Automattable instructions (commands to be run) can be included
directly and run automatically.
</li>
<li>
The user can be prompted for values that need to be entered by a
human (like a version number for the release).
</li>
<li>
It can be run interactively, prompting the administrator
at each step if each step should be done or not.
</li>
<li>
Steps can be grouped together (e.g. "preparing", "packaging",
"uploading", …)
</li>
</ul>
</div>
</div>
</div>
<div id="outline-container-3" class="outline-2">
<h2 id="sec-3"><span class="section-number-2">3</span> Usage </h2>
<div class="outline-text-2" id="text-3">
</div>
<div id="outline-container-3_1" class="outline-3">
<h3 id="sec-3_1"><span class="section-number-3">3.1</span> Step by Step </h3>
<div class="outline-text-3" id="text-3_1">
<p>
makerelease divides up your release steps into pieces. Each step
contains documentation and instructions (automatically done or not)
that need to be done. There are a number of different types of steps.
</p>
</div>
</div>
<div id="outline-container-3_2" class="outline-3">
<h3 id="sec-3_2"><span class="section-number-3">3.2</span> Structured in XML </h3>
<div class="outline-text-3" id="text-3_2">
<p>
All the steps are documented and defined using a simple xml syntax.
This provides easy editing using any common text editor, but still
allows for documentation to be easily embedded and displayable by
the makerlease tool. The most basic step structure looks like:
</p>
<pre class="example"><makerelease>
<steps>
<step type="informational">
<text>
Advertise: NEWS upload to sf, publish on -announce, freshmeat,
and the GNU FSF directory
(http://directory.fsf.org/)...
(send mail to [email protected])
</text>
</step>
</steps>
</makerelease>
</pre>
<p>
This example step (an <i>informational</i> step) simply prints the text to the screen for the user to read.
</p>
</div>
</div>
<div id="outline-container-3_3" class="outline-3">
<h3 id="sec-3_3"><span class="section-number-3">3.3</span> makerelease -n: dry-run and produce documentation </h3>
<div class="outline-text-3" id="text-3_3">
<p>
You can test running makerelease on a defined xml file using the
-n switch. This produces documentation about the steps to be
done. For example, running makerelease -n on the previous example
would produce:
</p>
</div>
</div>
<div id="outline-container-3_4" class="outline-3">
<h3 id="sec-3_4"><span class="section-number-3">3.4</span> makerelease: </h3>
<div class="outline-text-3" id="text-3_4">
<p>
By default, makerelease looks for a makerelease.xml file in the
current directory. Use the <i>-c FILE</i> flag to specify a particular
file to load. It will then proceed to iterate through each step
and act accordingly. See the <a href="#sec-3_4">Writing Steps</a> section below
for details.
</p>
<pre class="example"># makerelease -c example.xml -n
STEP: 1:
Advertise: NEWS upload to sf, publish on -announce, freshmeat, and
the GNU FSF directory (http://directory.fsf.org/)... (send mail to
</pre>
<p>
Note: by default it wraps all text nicely to fit into the screen
for you.
</p>
</div>
</div>
</div>
<div id="outline-container-4" class="outline-2">
<h2 id="sec-4"><span class="section-number-2">4</span> Writing Steps </h2>
<div class="outline-text-2" id="text-4">
<p>
There are a large number of step types, each with their own purpose.
Some flags for them work globally (on any step type) and some are
Step specific.
</p>
</div>
<div id="outline-container-4_1" class="outline-3">
<h3 id="sec-4_1"><span class="section-number-3">4.1</span> Global Attributes and Data </h3>
<div class="outline-text-3" id="text-4_1">
</div>
<div id="outline-container-4_1_1" class="outline-4">
<h4 id="sec-4_1_1"><span class="section-number-4">4.1.1</span> <text>foo</text> </h4>
<div class="outline-text-4" id="text-4_1_1">
<p>
The <i><text></i> section is used to describe a particular step for
documentational purposes. It is output both to the operator
doing an actual release as well as when using the <i>-n</i> flag to
simply produce documentation.
</p>
</div>
</div>
<div id="outline-container-4_1_2" class="outline-4">
<h4 id="sec-4_1_2"><span class="section-number-4">4.1.2</span> title="Title for the Step" </h4>
<div class="outline-text-4" id="text-4_1_2">
<p>
A step with the /title="something"/ attribute to the step will
"name" the step when displaying it to the user.
</p>
<pre class="example"><step type="informational" title="Call Bob">
<text>
Call Bob and have him commit all his outstanding changes.
</text>
</step>
</pre>
<p>
Produces:
</p>
<pre class="example"># makerelease -c example.xml
[...]
STEP: 2: Call Bob
Call Bob and have him commit all his outstanding changes.
</pre>
</div>
</div>
<div id="outline-container-4_1_3" class="outline-4">
<h4 id="sec-4_1_3"><span class="section-number-4">4.1.3</span> stepname="name" </h4>
<div class="outline-text-4" id="text-4_1_3">
<p>
The stepname will eventually be used to control auto-skipping of
things. It is most useful when used with a structured naming
scheme like "build:configure".
</p>
</div>
</div>
<div id="outline-container-4_1_4" class="outline-4">
<h4 id="sec-4_1_4"><span class="section-number-4">4.1.4</span> pause="true" </h4>
<div class="outline-text-4" id="text-4_1_4">
<p>
Creating a step with <i><step pause="true" …></i> will tell
makerelease to stop after the text is displayed and wait for the
user to acknowledge the screen.
</p>
<pre class="example"><step type="informational" pause="true" title="Call Bob">
<text>
Call Bob and have him commit all his outstanding changes.
</text>
</step>
</pre>
<p>
Produces:
</p>
<pre class="example"># makerelease -c example.xml
[...]
STEP: 2: Call Bob
Call Bob and have him commit all his outstanding changes.
---- PRESS ENTER TO CONTINUE (q=quit) ----
</pre>
</div>
</div>
</div>
<div id="outline-container-4_2" class="outline-3">
<h3 id="sec-4_2"><span class="section-number-3">4.2</span> Step Types </h3>
<div class="outline-text-3" id="text-4_2">
</div>
<div id="outline-container-4_2_1" class="outline-4">
<h4 id="sec-4_2_1"><span class="section-number-4">4.2.1</span> Informational </h4>
<div class="outline-text-4" id="text-4_2_1">
<p>
Informational steps simply present information to the
administrator and do not perform any specific action. They're
there just to document a step. They can be used to tell an
administrator to do something that can't be automated by
including the <i>prompt</i> flag to ensure the user sees it.
</p>
<pre class="example"><step type="informational" pause="true">
<text>
Call Bob and have him commit all his outstanding changes.
</text>
</step>
</pre>
<p>
Produces:
</p>
<pre class="example"># makerelease -c example.xml
[...]
STEP: 2:
Call Bob and have him commit all his outstanding changes.
---- PRESS ENTER TO CONTINUE (q=quit) ----
</pre>
</div>
</div>
<div id="outline-container-4_2_2" class="outline-4">
<h4 id="sec-4_2_2"><span class="section-number-4">4.2.2</span> Section </h4>
<div class="outline-text-4" id="text-4_2_2">
<p>
The <i>section</i> type lets you group various sub-steps together.
It allows for entire sections to be skipped when using the <i>-i</i>
p flag and documentation to be divided up into sections.
</p>
<pre class="example"><step type="section" title="Setup Steps" mandatory="1">
<text>These steps do preliminary work for making a release.</text>
<steps>
<step type="command">
<commands>
<command>echo "hello world"</command>
</commands>
</step>
<step type="informational">
<text>Also, Hello Universe</text>
</step>
</steps>
</step>
</pre>
<p>
Produces:
</p>
<pre class="example"># makerelease -c example.xml -n
STEP: 1: Setup Steps
These steps do preliminary work for making a release.
===== Entering Step: 1 =====
STEP: 1.1:
Commands to execute:
echo "hello world"
STEP: 1.2:
Also, Hello Universe
(Leaving Step: 1)
</pre>
</div>
</div>
<div id="outline-container-4_2_3" class="outline-4">
<h4 id="sec-4_2_3"><span class="section-number-4">4.2.3</span> Include </h4>
<div class="outline-text-4" id="text-4_2_3">
<p>
An <i>include</i> directive is functionally the same as a <i>section</i>
directive, but the sections are specified in another
makerelease xml file (which must be a fully qualified xml file
with the top level <i><makerelease></i> tag in place.
</p>
<pre class="example"><step type="include" title="Super extra steps">
<file>/path/to/foo.xml</file>
</step>
</pre>
</div>
</div>
<div id="outline-container-4_2_4" class="outline-4">
<h4 id="sec-4_2_4"><span class="section-number-4">4.2.4</span> Command </h4>
<div class="outline-text-4" id="text-4_2_4">
<p>
Command steps are designed to run a particular set of commands
via system() calls. All the commands must succeed or the user
will be prompted for what to do next (continue, retry or quit).
</p>
<pre class="example"><step type="command">
<commands>
<command>echo "hello world"</command>
<command>rm /</command>
</commands>
</step>
</pre>
<p>
Produces:
</p>
<pre class="example">STEP: 3:
running 'echo "hello world"'
hello world
running 'rm /'
rm: cannot remove `/': Is a directory
failed: status=256 what now (c,r,q)?
</pre>
</div>
</div>
<div id="outline-container-4_2_5" class="outline-4">
<h4 id="sec-4_2_5"><span class="section-number-4">4.2.5</span> Prompt </h4>
<div class="outline-text-4" id="text-4_2_5">
<pre class="example"><step type="prompt" prompt="Enter the version number:"
title="Pick a Version Number for this release"
parameter="VERSION">
</step>
</pre>
<p>
Asks the user for a version number and assigns the result to the
VERSION parameter. The VERSION parameter can be used in future
system commands, text, etc by wrapping the parameter name in {} brackets.
</p>
<pre class="example"><step type="command">
<text>We're going to produce {VERSION}
<commands>
<command>echo Hello World version {VERSION}</command>
</commands>
</step>
</pre>
<p>
You can also add a <i>values=</i> attribute to specify the legal
values that can be chosen based on a regular expression. For
example, the following enforces a strict NUM.NUM format:
</p>
<pre class="example"><step type="prompt" prompt="Enter the version number:"
title="Pick a Version Number for this release"
parameter="VERSION"
values="^\d+\.\d+$">
</step>
</pre>
</div>
</div>
<div id="outline-container-4_2_6" class="outline-4">
<h4 id="sec-4_2_6"><span class="section-number-4">4.2.6</span> Modify </h4>
<div class="outline-text-4" id="text-4_2_6">
<p>
The modify step lets you make regexp based modifications to files
within the distribution. Files are passed through glob() so can
include wildcards (*) characters.
</p>
<pre class="example"><step type="modify" title="Update the version number">
<text>
We will now modify files through the code to replace the
version number with the newer one.
</text>
<modifications>
<modify
find="VERSION = '(.*)'"
replace="VERSION = \'{VERSION}\'">
<files>
<file>lib/MyModule.pm</file>
<file>lib/SubDir/*.pm</file>
</files>
</modify>
</modifications>
</step>
</pre>
<p>
Note: You may specify multiple <i><modify></i> sections within the
<i><modifications></i> tag too.
</p>
</div>
</div>
<div id="outline-container-4_2_7" class="outline-4">
<h4 id="sec-4_2_7"><span class="section-number-4">4.2.7</span> Perl </h4>
<div class="outline-text-4" id="text-4_2_7">
<p>
A wise man once said "when all else fails, resort to perl". Ok, I
don't know that anyone said that actually. But I bet someone did
because it seems wise to me. Sometimes it's necessary to do extra
processing of user-entered data or files or the moon. Embedding
perl code directly lets you accomplish these sorts of things.
</p>
<p>
The $self variable will be to the current Makerelease::Step::Perl
module, and within that is a reference to the parameters hash in
$self->{'parameters'}.
</p>
<p>
Here's an example that takes the VERSION parameter and creates a
new one called VERSIONDASHES with the dots replaced by dashes.
</p>
<pre class="example"><step type="perl" title="Defining a second internal version string"
mandatory="1">
<perl>
<code>
# version number with dashes instead of dots
$self->{'parameters'}{'VERSIONDASHES'} =
$self->{'parameters'}{'VERSION'};
$self->{'parameters'}{'VERSIONDASHES'} =~ s/\./-/g;
</code>
</perl>
</step>
</pre>
</div>
</div>
</div>
</div>
<div id="outline-container-5" class="outline-2">
<h2 id="sec-5"><span class="section-number-2">5</span> Examples </h2>
<div class="outline-text-2" id="text-5">
</div>
<div id="outline-container-5_1" class="outline-3">
<h3 id="sec-5_1"><span class="section-number-3">5.1</span> Projects that are making use of makerelease scripts </h3>
<div class="outline-text-3" id="text-5_1">
<p>
(scripts are located in the "dist" subdirectory if not otherwise
specified):
</p>
<ul>
<li>
<a href="http://www.net-snmp.org/">Net-SNMP</a>
</li>
<li>
<a href="http://www.dnssec-tools.org/">DNSSEC-Tools</a>
</li>
<li>
<a href="http://www.geoqo.org/">GeoQO</a>
</li>
<li>
<a href="http://search.cpan.org/search?query=qwizard&mode=all">QWizard</a>
</li>
</ul>
</div>
</div>
<div id="outline-container-5_2" class="outline-3">
<h3 id="sec-5_2"><span class="section-number-3">5.2</span> Included example scripts </h3>
<div class="outline-text-3" id="text-5_2">
<ul>
<li>
dist/makerelease.xml: the release script for this package!
</li>
</ul>
<hr/>
</div>
</div>
</div>
<div id="postamble">
<p class="date"> Date: 2011-02-04 10:19:20 PST</p>
<p class="creator">HTML generated by org-mode 6.36trans in emacs 23</p>
</div>
</div>
</body>
</html>