Issue 22148 - New Ximian artwork
Summary: New Ximian artwork
Status: CLOSED FIXED
Alias: None
Product: gsl
Classification: Code
Component: code (show other issues)
Version: OOo 1.1 RC5
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: OOo 2.0
Assignee: mmeeks
QA Contact: issues@installation
URL:
Keywords:
Depends on: 22149
Blocks:
  Show dependency tree
 
Reported: 2003-11-05 12:47 UTC by mmeeks
Modified: 2005-06-08 17:28 UTC (History)
5 users (show)

See Also:
Issue Type: FEATURE
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description mmeeks 2003-11-05 12:47:01 UTC 
We'd very much like to merge our new high-colour artwork into OO.o, and work
from your CVS to get coverage and completeness to 100% finally.

Is it possible to have a cws to do the merge into ?
Comment 1 mmeeks 2003-11-05 12:54:31 UTC 
need the alpha blending code to make it really useful.
Comment 2 Olaf Felka 2003-11-05 12:59:15 UTC 
of -> mh: Please have a look. I've changed from 'defect' to 'task'. I
think it's appropriate.
Comment 3 Martin Hollmichel 2003-11-05 13:07:10 UTC 
flagged this as feature and target 2.0 and component gsl to get a
solid basis. start creating cws alphaart.
Comment 4 Martin Hollmichel 2004-02-07 10:12:07 UTC 
mh->ka:reassigned to you as you have taken action on this.
Comment 5 ooo 2004-02-09 14:23:51 UTC 
accepted
Comment 6 ooo 2004-07-20 10:39:41 UTC 
Martin, I'd like to hand this task over to you for clarifying appropriate handling.
Comment 7 Martin Hollmichel 2004-12-03 04:06:03 UTC 
as I understood, almost all technical prerequistes are fulfilled to commit to
the repository ?!
Comment 8 mmeeks 2005-01-06 16:09:23 UTC 
Ok - the vast majority of these icons are committed - jimmac is working on
making the set complete though.
Comment 9 quetschke 2005-01-16 19:40:11 UTC 
ooo_custom_images is not tagged for industrial01 but mentioned there.
Comment 10 quetschke 2005-01-16 19:45:59 UTC 
$ cwsadd ooo_custom_images
cwsadd -- version: 1.6
        Updating 'ooo_custom_images' ...
cwsadd: Tagging module 'ooo_custom_images'.
cwsadd: Tag with branch tag 'cws_src680_industrial01'.
..........................................
cwsadd: ERROR: Tagging module 'ooo_custom_images' failed.
cwsadd: ERROR: Adding and/or registering module 'ooo_custom_images' failed!

FAILURE: cwsadd aborted.

Hrmpf, this fails because it is not yet tagged for the master SRC680.
Comment 11 Martin Hollmichel 2005-01-17 10:26:18 UTC 
mh->hr: do RE need to do something to recognize this module ?
Comment 12 jens-heiner.rechtien 2005-01-17 12:16:08 UTC 
New modules are not part of the CWS process. Just commit the stuff top level and
send release engineering a mail that a CWS is accompanied by a new module. We'll
do the necessary magic to make the new module a full member of the MWS on
integration day and after that day the module can be handled like every other
module.
Comment 13 Martin Hollmichel 2005-03-21 15:50:49 UTC 
I consider the cws problems as solved.
Comment 14 Martin Hollmichel 2005-05-12 08:52:08 UTC 
mark as resolved.
Comment 15 jens-heiner.rechtien 2005-06-08 17:28:38 UTC 
Closing issue since the CWS is integrated and ooo_custom_images is now an
"official" module.