added mention of the new "minimal" template...

...and cleaned up Admin links in classic

Author: Richard Jones

doc/announcement.txt

@@ -1,58 +1,76 @@
-=====================================================
-SC-Track Roundup 0.5 beta2 - an issue tracking system
-=====================================================
+=================================================================
+SC-Track Roundup 0.5 final pre-release - an issue tracking system
+=================================================================
 
-Note: This is the first of two beta releases of the newest version of Roundup.
-It is strongly recommended that you maintain your existing 0.4 installation if
-you have one, and run 0.5 on a copy of the database. If you are upgrading from
-0.4, you must read doc/upgrading.txt!
+Note: This is the final pre-release of the newest version of Roundup. It is
+      strongly recommended that you maintain your existing 0.4 installation if
+      you have one, and run 0.5 on a copy of the database. If you are
+      upgrading from 0.4, you must read doc/upgrading.txt!
 
 Roundup requires python 2.1.1 for correct operation. Support for dumbdbm
 requires python 2.1.2 or 2.2. 2.1.3 and 2.2.1 are recommended.
 
 This beta release fixes the following specific problems:
 
-- all backends now have a .close() method, and it's used everywhere
-- fixed bug in detectors __init__
-- switched the default issue item display to only show issue summary (added
-  instructions to doc to make it display entire content)
-- MANIFEST.in was missing a lot of template files
-- added generic item editing
-- much nicer layout of template rendering errors
-- added context/is_edit_ok and context/is_view_ok convenience methods and
-  implemented use of them in the classic template
+- fixes to import/export
+- password edit now has a confirmation field
+- cleanups and fixes to the shipped classic template
+- new backend for sqlite (and it rocks :)
+- many performance improvements in dbm and sql backends
+- cgi.client base URL is now obtained from the config TRACKER_WEB (as a result
+  request.url has gone away - there's too much magic in trying to figure
+  what it should be)
+- cgi-bin script redirects to https now if the request was https
+- FileClass "content" property wasn't being returned by getprops() in most
+  backends
+- we now verify instance attributes on instance open and throw a useful error
+  if they're not all there
+- sf bug 611217 ] menu() has problems when labelprop==None
+- verify contents of tracker module when the tracker is opened
+- fixes to value parsing from edit forms
+- mailgw was missing an "import sys" (!)
+- setup now installs scripts with python -O flag, doubling performance in some
+  cases (there's a lot of __debug__ use)
+- added getItem to HTMLClass so you can access arbitrary items in templates
+- replaced the content() callback ickiness with Page Template macro usage
+- changed the default CSS style to be less offensive to some ;)
+- better handling of Page Template compilation errors
+- sf bug 614188 ] Exception in mailgw.py
+- sf bug 613310 ] traceback on onexistant items
+- sf bug 613291 ] typos in nosy list
+- handle stupid mailers that QUOTE their Re; 'Re: "[issue1] bla blah"'
+- giving a user a Role that doesn't exist doesn't break stuff any more
+- revamped user guide, customisation guide, added basic maintenance guide
+- merge Zope Collector #580 fix from ZPT CVS trunk
+- added the "minimal" template
 
 A lot has been done since 0.4:
 
 - new backend for metakit (thanks Gordon McMillan)
+- new backend for sqlite
 - new backend for gadfly (it's as done as it's going to get)
 - further split the dbm backends from the core code, allowing easier
   non-dict-like backends (eg metakit, RDB)
-- implemented and used the new access control mechanisms (Permissions, Roles)
-- switched templating to use Zope's PageTemplates (yay!)
-- switched to sessions for web authentication
 - added Boolean and Number types
-- full-text search may also search certain String properties
 - fixed the journal bloat
-- updated design document for new access controls
-- updated customisation document, including more examples
+- full-text search may also search certain String properties
 - entire database export and import (incl files)
-- better mailgw help message (feature request #558562)
-- re-enabled link backrefs from messages (feature request #568714)
-- the page layout is now templatable
+- implemented and used the new access control mechanisms (Permissions, Roles)
+- switched templating to use Zope's PageTemplates giving much more flexibility
+- revamped look and feel in web interface including cleaned up CSS usage
 - re-worked cgi interface to abstract out the explicit "issue" interface
-- have index page handle mid-page errors better so header and footer are
-  still visible
+- switched to sessions for web authentication
 - saving of named search queries
+- updated design document for new access controls
+- updated customisation document, including more examples
+- added maintenance guide
+- better mailgw help message (feature request #558562)
 - we handle "not found", access and item page render errors better
 - fixed double-submit by having new-item-submit redirect at end
-- daemonify roundup-server (fork, logfile, pidfile)
-- modify cgitb to display PageTemplate errors better
-- rename to "instance" to "tracker"
-- have roundup.cgi pick up tracker config from the environment 
-- revamped look and feel in web interface
-- cleaned up stylesheet usage
-- several bug fixes and documentation fixes
+- roundup-server may be a daemon now (fork, logfile, pidfile)
+- renamed "instance" to "tracker" everywhere, and "node" to "item" in most
+  places
+- many more bug fixes, cleanups and minor improvements
 
 Source and documentation is available at the website:
      http://roundup.sourceforge.net/
@@ -87,6 +105,6 @@ doesn't even need to be "installed" to be operational, though a
 disutils-based install script is provided.
 
 It comes with two issue tracker templates (a classic bug/feature tracker and
-a help desk) and five database back-ends (anydbm, bsddb, bsddb3, metakit and
-gadfly). 
+a minimal skeleton) and six database back-ends (anydbm, bsddb, bsddb3, sqlite,
+metakit and gadfly). 
 

doc/installation.txt

@@ -2,7 +2,7 @@
 Installing Roundup
 ==================
 
-:Version: $Revision: 1.26 $
+:Version: $Revision: 1.27 $
 
 .. contents::
 
@@ -148,6 +148,14 @@ The classic template is the one defined in the `Roundup Specification`_. It
 holds issues which have priorities and statuses. Each issue may also have a
 set of messages which are disseminated to the issue's list of nosy users.
 
+Minimal Template
+~~~~~~~~~~~~~~~~
+
+The minimal template has the minimum setup required for a tracker
+installation. That is, it has the configuration files, defines a user database
+and the basic HTML interface to that. It's a completely clean slate for you to
+create your tracker on.
+
 
 Choosing Your Backend
 ---------------------

doc/upgrading.txt

@@ -18,8 +18,8 @@ This has been a fairly major revision of Roundup:
    transition. Please don't hesitate to ask on roundup-users for help (or
    complete conversions if you're completely stuck)!
 2. The database backed got a lot more flexible, allowing Metakit and SQL
-   databases! The only SQL database implemented at present is gadfly, but
-   others shouldn't be a whole lot more work.
+   databases! The only decent SQL database implemented at present is sqlite,
+   but others shouldn't be a whole lot more work.
 3. A brand new, highly flexible and much more robust security system including
    a system of Permissions, Roles and Role assignments to users. You may now
    define your own Permissions that may be checked in CGI transactions.
@@ -177,7 +177,7 @@ like so::
                     messageid=String(),  inreplyto=String())
 
 Nosy list link event journalling is actually turned off by default now. If you
-want to turn it onn, change to your issue class' nosy list, change its
+want to turn it on, change to your issue class' nosy list, change its
 definition from::
 
     issue = IssueClass(db, "issue",

roundup/__init__.py

@@ -15,7 +15,7 @@
 # BASIS, AND THERE IS NO OBLIGATION WHATSOEVER TO PROVIDE MAINTENANCE,
 # SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.
 # 
-# $Id: __init__.py,v 1.12 2002-09-13 04:14:07 richard Exp $
+# $Id: __init__.py,v 1.13 2002-09-26 04:19:53 richard Exp $
 
 __doc__ = '''
 This is a simple-to-use and -install issue-tracking system with
@@ -65,6 +65,6 @@
 much prettier cake :)
 '''
 
-__version__ = '0.5.0b2'
+__version__ = '0.5.0pr1'
 
 # vim: set filetype=python ts=4 sw=4 et si

roundup/templates/classic/html/page

@@ -48,11 +48,15 @@
   </p>
 
   <p class="classblock"
-       tal:condition="python:request.user.hasPermission('Edit', None)">
-   <b>Admin</b><br>
-   <a href="home?:template=classlist">Class List</a><br>
-   <a href="user">User List</a><br>
-   <a href="user?:template=item">Add User</a>
+       tal:condition="python:request.user.username != 'anonymous'">
+   <b>Administration</b><br>
+   <a tal:condition="python:request.user.hasPermission('Edit', None)"
+      href="home?:template=classlist">Class List</a><br>
+   <a tal:condition="python:request.user.hasPermission('View', 'user')
+                            or request.user.hasPermission('Edit', 'user')"
+      href="user" >User List</a><br>
+   <a tal:condition="python:request.user.hasPermission('Edit', 'user')"
+      href="user?:template=item">Add User</a>
   </p>
 
   <p class="userblock" tal:condition="python:request.user.username=='anonymous'">