You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@forrest.apache.org by ji...@apache.org on 2006/01/15 11:32:38 UTC

[jira] Subscription: FOR-open-with-patch

Issue Subscription
Filter: FOR-open-with-patch (13 issues)
Subscriber: rgardler


Key         Summary
FOR-756     Citations Plugin
            http://issues.apache.org/jira/browse/FOR-756
FOR-559     FAQ+TOC problem: force-toc option
            http://issues.apache.org/jira/browse/FOR-559
FOR-540     Typo/reader editing for View HowTos
            http://issues.apache.org/jira/browse/FOR-540
FOR-534     Skin sample donation
            http://issues.apache.org/jira/browse/FOR-534
FOR-525     Making views XHTML compliant
            http://issues.apache.org/jira/browse/FOR-525
FOR-518     Change toolbox font in skinconf.xml for pelt
            http://issues.apache.org/jira/browse/FOR-518
FOR-413     PDF: rendering fails when graphics too big - workaround inside
            http://issues.apache.org/jira/browse/FOR-413
FOR-412     use CSS for displaying list of Changes
            http://issues.apache.org/jira/browse/FOR-412
FOR-368     Add ihtml to "Deprecation of .ehtml and .ihtml" reference
            http://issues.apache.org/jira/browse/FOR-368
FOR-311     OOo Headings bug causes Forrest to fail
            http://issues.apache.org/jira/browse/FOR-311
FOR-280     gather index terms from documents to create index page with links
            http://issues.apache.org/jira/browse/FOR-280
FOR-275     front-piece title page for pdf-output
            http://issues.apache.org/jira/browse/FOR-275
FOR-15      supporting xhtml/css (as per validator.w3.org) in project directory tree
            http://issues.apache.org/jira/browse/FOR-15

Nags from Jira (was Re: [jira] Subscription: FOR-open-with-patch)

Posted by Ross Gardler <rg...@apache.org>.

jira@apache.org wrote:
> Issue Subscription
> Filter: FOR-open-with-patch (13 issues)
> Subscriber: rgardler

David set this filter up to make it easier for us Devs. I've made it so 
that it sends to the mailing list once a week (Sundays). We got two 
today because I did a test run.

It is disheartening for potential committers to take the time to create 
a patch and then it gets forgotten about.

Committers should try their hardest to ensure that no item in this list 
appears in two consequative nag mails (i.e. the maximum time a patch 
should stay withiout being applied would be 13 days).

Ross