168057 - RFE: Apply fixed and improvements for OEM branch to 1.0.2-branch, too...

Status: RESOLVED WONTFIX

(Core Graveyard :: Tracking, defect)

Description

[Roland Mainz]

[Per discussion with jesup a few mins ago:]
I noticed that we have _tons_ of bugs (the example BugZilla query URL currrently
lists 68 bugs(!!)) where many usefull patches are created for the OEM-branch -
but they are usually _not_ applied to the 1.0.2-branch.
IMHO this is silly - most of these fixes&&improvements should be part of the
1.0.2-branch, too...

Comment 1

[Roland Mainz]

prabhat/katakai:
Can you provide all required bugids to get the CTL extension working on the
1.0.2-branch (e.g. all those patches which have been approved for the OEM
branch), please ?

Comment 2

[Roland Mainz]

OK, from my side the patches from the following bugs should be applied to the
1.0.2-branch (they are all fixed in the OEM branch):
- bug 161556 ("Arabic bitmap fonts are printed too small")
- bug 161634 ("[ps] envvar should not be freed after PR_SetEnv")
- bug 147605 ("Printing / Page settings reset themselves after print (no
landscape printing)")
- bug 166217 ("Print settings on Linux are saved at shutdown but not rea...")

Comment 3

[Masaki Katakai]

I have checked in the following to OEM branch, but not into 1.0.1 branch.

How about you, Pete?
I belive Sun China team also has many bugfixes for OEM branch.

7965 [converter] need ISO-2022-CN converters
52416 Editor does not accept NS_TEXT_EVENT while losing input f...
152521 XIM is disabled by bad font lookup
167040 CTL: caret does not move to next/prev line on text area
133212 --enable-ctl bustage
149692 Japanese font is displayed ugly on linux RH7.2
163962 Extend CTL extension to support multiple CTL scripts

Comment 4

[XandreX]

This bug is blocking the "Make 1.0.2 not suck" bug :
<URL:http://bugzilla.mozilla.org/show_bug.cgi?id=161807> .

Moreover, this bug is not anymore depending on another bug.
Is this bug going to change state/target ?

Comment 5

[Jim Dunn]

FYI there is no plan on my (oem'ers in general) to move OEM_BRANCH
specific patches to the 1.0.2 branch.  My guess is that if you want
them moved forward, then you will have to do it yourself.  The good 
news is that ALL of these fixes are in the trunk, have been reviewed
and sr= as well as verified as being 'good'.  So getting them in
really only requires getting a= for 1.0.2

Comment 6

[XandreX]

I am just someone eager to see 1.0.2 released :)
Therefore I think I can't do much here. Who can (and will) ?
It has been 3 months since the last comment, so I was wondering if the bug could
be change somehow so 1.0.2 can be released (preferably before 1.3a).

Comment 7

[Vedran Miletic]

retargeting

Comment 8

[Randell Jesup [:jesup] (needinfo me)]

No longer relevant