Is the the foomatic-db-engine  the only intended consumer for the files 
exported by this case?

if so, is there a reason for delivering these cases separate from each other

    Kais.

On 09/15/08 18:20, Wendy Phillips wrote:
> Template Version: @(#)sac_nextcase %I% %G% SMI
> This information is Copyright 2008 Sun Microsystems
> 1. Introduction
>     1.1. Project/Component Working Name:
>        foomatic-db
>     1.2. Name of Document Author/Supplier:
>        Author:  Wendy Phillips
>     1.3  Date of This Document:
>       15 September, 2008
> 4. Technical Description
>
> I am creating this self-review on behalf of myself. Though there are not
> current plans to backport this technology, it is for patch/micro release 
> binding
> in the event that a backport is requested.
>
> I think this qualifies for self-review, but if anyone disagrees, let me know 
> and
> I'll promote it to fasttrack.
>
> -Wendy
>
> 1. Introduction
>   1.1. Project/Component Working Name:
>       foomatic-db
>   1.2. Name of Document Author/Supplier:
>       Author: Wendy Phillips
>   1.3. Date of This Document:
>       09/15/2008
>
> 4. Technical Description
>
> Summary
>
>  This is a collection of files that contain knowledge about printers,
>  drivers and driver options. It is utilized by the foomatic-db-engine
>  to generate PPD files. Note: the foomatic-db-engine is slated to be
>  delivered at the same time as this package.
>
>  This project seeks micro/patch binding.
>
> Interfaces
>
>  Exported Interfaces
>    Interface          Classification          Comment
>    ---------          --------------          -------
>    SUNWfoo-db         Uncommitted             Package name
>
> 5. Reference Documents:
>
>   http://www.linuxfoundation.org/en/OpenPrinting/Database/Foomatic
>   LSARC 2004/262 Printer RIP                                
>
> 6. Resources and Schedule:
>   6.4. Product Approval Committee requested information:
>    6.4.1. Consolidation or Component Name:
>       SFW
>   6.5. ARC review type:
>       SelfReview
>   6.6. ARC Exposure:
>       Open
>
> 7. Prototype Availability:
>   7.1. Prototype Availability:
>    Now
>
>
>
> 6. Resources and Schedule
>     6.4. Steering Committee requested information
>       6.4.1. Consolidation C-team Name:
>               sfw
>     6.5. ARC review type: Automatic
>     6.6. ARC Exposure: open
>
>
>   


Reply via email to