ad_agency 0.1.1 → 0.1.2
Sign up to get free protection for your applications and to get access to all the features.
- data/History.txt +4 -0
- data/README.rdoc +20 -0
- data/VERSION +1 -1
- metadata +2 -2
data/History.txt
CHANGED
data/README.rdoc
CHANGED
@@ -26,6 +26,26 @@ require 'lib/ad_agency'
|
|
26
26
|
|
27
27
|
or you can replace that line since ad_agency requires jeweler itself
|
28
28
|
|
29
|
+
=== Updating History.txt from your git log
|
30
|
+
|
31
|
+
To regenerate your History.txt file from your git log run
|
32
|
+
|
33
|
+
rake advertise:gen_history
|
34
|
+
|
35
|
+
This will produce a history file from your git commit history, in reverse chronological order
|
36
|
+
|
37
|
+
The commit matching each git tag will be preceded by a line like this
|
38
|
+
|
39
|
+
=== <tag> <date>
|
40
|
+
|
41
|
+
In addition if a tag for the version in the VERSION file doesn't exist, the History file will start as if the tag
|
42
|
+
v<version> existed.
|
43
|
+
|
44
|
+
This allows the history file to reflect what it will be if rake release were issued next, since jeweler tags the
|
45
|
+
the commit this way.
|
46
|
+
|
47
|
+
=== Generating an announcement
|
48
|
+
|
29
49
|
To produce an announcement run the rake task:
|
30
50
|
|
31
51
|
rake advertise:email_body -s
|
data/VERSION
CHANGED
@@ -1 +1 @@
|
|
1
|
-
0.1.
|
1
|
+
0.1.2
|