From: Till Kamppeter <till.kamppeter@gmail.com>
To: printing-architecture@lists.linux-foundation.org
Subject: [Printing-architecture] OpenPrinting has a bug and feature tracking system now!
Date: Fri, 16 May 2008 11:09:59 +0200 [thread overview]
Message-ID: <482D4F67.9070300@gmail.com> (raw)
Hi,
OpenPrinting has a Bugzilla-based bug/feature tracking system now. This
way we will assure that bug reports and feature requests do not get
forgotten under tons of postings on the forum or on mailing lists. In
the system all bug reports get registered with priority, state, package
they affect, they can get assigned to the developer who is supposed to
fix it, ...
So if you think something is going wrong with Foomatic, the
OpenPrinting, database, the web site, or anything else coming from
OpenPrinting, please do not post on the forum, nor on any mailing list.
Post on our new bug tracker [1], under the product "OpenPrinting". This
way your problem will not get forgotten. Please report also feature
requests here.
Please do not report small issues (like typos) on Wiki pages, you can
fix them by yourself. Also do not report missing printer models in the
database. Please add them via the printer input form [2]. We are
currently developing a facility to let user-contributed printer entries
get more quickly into the Foomatic database [3].
See all current open bug reports and feature requests concerning
OpenPrinting here [4].
Till
[1]http://bugs.linux-foundation.org/
[2]http://openprinting.org/edit_printer.cgi?newentry=1
[3]http://code.google.com/soc/2008/linux/appinfo.html?csaid=1897A851CAC216AC
[4]http://bugs.linux-foundation.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=OpenPrinting&component=Common+Printing+Dialog&component=foomatic-db&component=foomatic-db-engine&component=foomatic-filters&component=OpenPrinting+database+maintenance+web+app&component=OpenPrinting+web+site&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&remtype=asdefault&field0-0-0=noop&type0-0-0=noop&value0-0-0=
reply other threads:[~2008-05-16 9:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=482D4F67.9070300@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=printing-architecture@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.