public inbox for printing-architecture@lists.linux.dev
 help / color / mirror / Atom feed
From: Till Kamppeter <till.kamppeter@gmail.com>
To: Open Printing <printing-architecture@lists.linux-foundation.org>,
	Zdenek Dohnal <zdohnal@redhat.com>,
	"jsmeix@suse.de" <jsmeix@suse.de>,
	Thorsten Alteholz <debian@alteholz.de>,
	Frederik Feichtmeier <frederik.feichtmeier@gmail.com>,
	Michael Sweet <msweet@msweet.org>,
	Sebastien Bacher <sebastien.bacher@canonical.com>,
	Ken VanDine <ken.vandine@canonical.com>
Subject: [Printing-architecture] Forth beta of the cups-browsed in the second generation of cups-filters released!
Date: Tue, 21 Mar 2023 22:19:32 +0100	[thread overview]
Message-ID: <c56818cd-9ac8-a512-a3da-81ca91ca6230@gmail.com> (raw)

Hi,

I have done the forth beta release of the new, separated cups-browsed 
package, one of the new components of the former cups-filters.

Central part of this release isa new test script, to be used both for 
build tests ( "make check") and tests on the packages installed into a 
system (like autopkgtests of Debian and Ubuntu).

This is not only for general QA but also a requirement for the package 
being accepted in the core part ("Main") of the Ubuntu operating system. 
See also

https://openprinting.github.io/OpenPrinting-News-February-2023/#the-new-architecture-is-going-into-ubuntu-and-red-hat

Developing of such a script naturally involves a lot of testing of 
cups-browsed itself, making us find several bugs and fix them. These 
fixes are also included in the new release.

Here we go:

https://openprinting.github.io/cups-browsed-Second-Generation-Forth-Beta-Release/

There are also GitHub discussions set up for each release now.

    Till

                 reply	other threads:[~2023-03-21 21:19 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=c56818cd-9ac8-a512-a3da-81ca91ca6230@gmail.com \
    --to=till.kamppeter@gmail.com \
    --cc=debian@alteholz.de \
    --cc=frederik.feichtmeier@gmail.com \
    --cc=jsmeix@suse.de \
    --cc=ken.vandine@canonical.com \
    --cc=msweet@msweet.org \
    --cc=printing-architecture@lists.linux-foundation.org \
    --cc=sebastien.bacher@canonical.com \
    --cc=zdohnal@redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox