Skip to content

Commit 4c81a62

Browse files
author
Richard Jones
committed
pre-b3 stuff
1 parent a58810b commit 4c81a62

File tree

4 files changed

+79
-30
lines changed

4 files changed

+79
-30
lines changed

doc/announcement.txt

Lines changed: 22 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,23 @@
11
This is the second beta release of Roundup version 0.7. It fixes some bugs
22
in the previous beta release:
33

4-
- Boolean, Date and Link HTML templating was broken
5-
- fix reporting of test inclusion in postgresql test
6-
- EditAction was confused about who "self" was
7-
- edit collision detection was broken for index-page edits
8-
- sqlite backend wasn't migrating multilink tables correctly
9-
- use SimpleCookie instead of Cookie (is an alias for the evil SmartCookie)
10-
- handle older sessions in session dbm
11-
- make presetunread more resilient to status Class changes
12-
- HTMLDatabase classes() was broken
4+
- mysql and postgresql schema mutation now handle added Multilinks
5+
- web CSV export was busted (as was any action returning a result)
6+
- MultiMapping deviated from the Zope C implementation in a number of
7+
places (thanks Toby Sargeant)
8+
- MySQL and Postgresql use BOOL/BOOLEAN for Boolean types
9+
- OTK generation was busted (thanks Stuart D. Gathman)
10+
- export and import now include journals (incompatible with export < 0.7)
11+
- added "download_url" method to generate a correctly quoted URL for file
12+
download links (sf bug 927745)
13+
- all uses of TRACKER_WEB now ensure it ends with a '/'
14+
- roundup-admin install checks for existing tracker in target home
15+
- grouping (and sorting) by multilink in RDBMS backends (sf bug 655702)
16+
- roundup scripts may now be asked for their version (sf rfe 798657)
17+
- sqlite backend had stopped using the global lock
18+
- better check for anonymous viewing of user items (sf bug 933510)
19+
- stop Interval from displaying an empty string (sf bug 934022)
20+
- fixed storage of some datatypes in some RDBMS backends
1321

1422
If you're upgrading from an older version of Roundup you *must* follow
1523
the "Software Upgrade" guidelines given in the maintenance documentation.
@@ -30,12 +38,13 @@ together a What's New page:
3038
Some highlights:
3139

3240
- added postgresql backend
33-
- RDBMS backends have no external locking requirements
41+
- trackers using postgresql or mysql backends may have many users
3442
- new "actor" automatic property (user who caused the last "activity")
3543
- RDBMS backends have data typed columns and indexes on several columns
36-
- we support confirming registration by replying to the email
37-
- all HTML templating methods now automatically check for permissions,
38-
greatly simplifying templates
44+
- registration may be concluded by replying to the confirmation email
45+
- HTML templating permission checks are greatly simplified
46+
- database exports now include full journals
47+
- IMAP support in the mail gateway
3948

4049
Roundup requires python 2.1.3 or later for correct operation.
4150

doc/whatsnew-0.7.txt

Lines changed: 52 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -155,26 +155,16 @@ text/html. This is done with::
155155
if you were returning a PNG image.
156156

157157

158-
Added CSV export action
159-
-----------------------
160-
161-
A new action has been added which exports the current index page or search
162-
result as a comma-separated-value (CSV) file.
163-
164-
To use it, add this to your "index" templates::
165-
166-
<a tal:attributes="href python:request.indexargs_url('issue',
167-
{'@action':'export_csv'})">Download as CSV</a>
168-
169-
Making sure that the ``'issue'`` part matches the class name of the page
170-
you're editing.
171-
172158
Roundup server
173159
--------------
174160

175161
The roundup-server web interface now supports setgid and running on port
176162
< 1024.
177163

164+
It also forks to handle new connections, which means that trackers using
165+
the postgresql or mysql backends will be able to have multiple users
166+
accessing the tracker simultaneously.
167+
178168

179169
HTML templating made easier
180170
---------------------------
@@ -238,6 +228,33 @@ may use the new ``utils.url_quote(url)`` and ``utils.html_quote(html)``
238228
methods.
239229

240230

231+
CSV download of search results
232+
------------------------------
233+
234+
A new CGI action, ``export_csv`` has been added which exports a given
235+
index page query as a comma-separated-value file.
236+
237+
To use this new action, just add a link to your ``issue.index.html``
238+
page::
239+
240+
<a tal:attributes="href python:request.indexargs_url('issue',
241+
{'@action':'export_csv'})">Download as CSV</a>
242+
243+
You may use this for other classes by adding it to their index page and
244+
changing the ``'issue'`` part of the expression to the new class' name.
245+
246+
247+
Other changes
248+
-------------
249+
250+
- we serve up a favicon now
251+
- the page titles have the tracker name at the end of the text instead
252+
of the start
253+
- added url_quote and html_quote methods to the utils object
254+
- added isset method to HTMLProperty
255+
- added search_checkboxes as an option for the search form
256+
257+
241258
Email Interface
242259
===============
243260

@@ -285,6 +302,10 @@ In addition, the ``IssueClass`` methods ``nosymessage()`` and
285302
message id parameter. This means that change notes with no associated
286303
change message may now be generated much more easily.
287304

305+
The roundupdb nosymessage() method also accepts a ``bcc`` argument which
306+
specifies additional userids to send the message to that will not be
307+
included in the To: header of the message.
308+
288309

289310
Registration confirmation by email
290311
----------------------------------
@@ -293,6 +314,23 @@ Users may now reply to their registration confirmation email, and the
293314
roundup mail gateway will complete their registration.
294315

295316

317+
``roundup-mailgw`` now supports IMAP
318+
------------------------------------
319+
320+
To retrieve from an IMAP mailbox, use a *cron* entry similar to the
321+
POP one::
322+
323+
0,10,20,30,40,50 * * * * /usr/local/bin/roundup-mailgw /opt/roundup/trackers/support imap <imap_spec>
324+
325+
where imap_spec is "``username:password@server``" that specifies the roundup
326+
submission user's IMAP account name, password and server. You may
327+
optionally include a mailbox to use other than the default ``INBOX`` with
328+
"``imap username:password@server mailbox``".
329+
330+
If you have a secure (ie. HTTPS) IMAP server then you may use ``imaps``
331+
in place of ``imap`` in the command to use a secure connection.
332+
333+
296334
Database configuration
297335
======================
298336

roundup/__init__.py

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@
1515
# BASIS, AND THERE IS NO OBLIGATION WHATSOEVER TO PROVIDE MAINTENANCE,
1616
# SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
1717
#
18-
# $Id: __init__.py,v 1.28 2004-03-26 06:38:48 richard Exp $
18+
# $Id: __init__.py,v 1.29 2004-04-18 06:14:26 richard Exp $
1919

2020
'''Roundup - issue tracking for knowledge workers.
2121
@@ -68,6 +68,6 @@
6868
'''
6969
__docformat__ = 'restructuredtext'
7070

71-
__version__ = '0.7.0b2'
71+
__version__ = '0.7.0b3'
7272

7373
# vim: set filetype=python ts=4 sw=4 et si

test/test_mailgw.py

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,9 @@
88
# but WITHOUT ANY WARRANTY; without even the implied warranty of
99
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
1010
#
11-
# $Id: test_mailgw.py,v 1.67 2004-04-09 01:32:58 richard Exp $
11+
# $Id: test_mailgw.py,v 1.68 2004-04-18 06:14:26 richard Exp $
12+
13+
# TODO: test bcc
1214

1315
import unittest, tempfile, os, shutil, errno, imp, sys, difflib, rfc822
1416

0 commit comments

Comments
 (0)