Skip to content

Commit fcf73b1

Browse files
author
Richard Jones
committed
pre-release stuff
1 parent 7f8d24b commit fcf73b1

File tree

3 files changed

+7
-4
lines changed

3 files changed

+7
-4
lines changed

BUILD.txt

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -2,10 +2,11 @@ Building Releases
22
=================
33

44
Roundup is currently a source-only release - it has no binary components. I
5-
want it to stay that way, too.
5+
want it to stay that way, too. This document describes how to build a
6+
source release. Users of Roundup should read the doc/installation.txt file
7+
to find out how to install this software.
68

7-
This means that we only need to ever build source releases. This is done by
8-
running:
9+
Building a release of Roundup is done by running:
910

1011
1. Make sure the unit tests run! "./run_tests.py"
1112
2. Edit roundup/__init__.py and doc/announcement.txt to reflect the new

CHANGES.txt

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
This file contains the changes to the Roundup system over time. The entries
22
are given with the most recent entry first.
33

4-
2004-??-?? 0.8.0b2
4+
2005-01-13 0.8.0b2
55
Fixed:
66
- note about how to run roundup demo in Windows (sf bug 1082090)
77
- fix API for templating utils extensions - remove "utils" arg (sf bug 1081981)

doc/announcement.txt

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -22,6 +22,8 @@ This is a bugfix release, fixing:
2222
- fix port number as int in mysql connection info (sf bug 1082530)
2323
- fix setup.py to work with <Python2.3 (sf bug 1082801)
2424
- fix permissions checks in cgi templating (sf bug 1082755)
25+
- fix "Users may only edit their issues" example in docs
26+
- handle ~/.my.cnf files for MySQL defaults (sf bug 1096031)
2527

2628
If you're upgrading from an older version of Roundup you *must* follow
2729
the "Software Upgrade" guidelines given in the maintenance documentation.

0 commit comments

Comments
 (0)