[Laszlo-dev] how we're gonna track 3.4 vs 4.1 doc mismatches

[Benjamin Shine]

Missing wrapper pages should be handled as individual bugs; this  
omnibus bug is designed only to cover *api* discrepancies.

API discrepancies must be reviewed by the API quorum, whereas missing  
data in wrapper pages need only be ported by toolsmith or doc author.

On Oct 31, 2007, at 4:00 PM, John Sundman wrote:

> Does this bug pertain to information from the old "wrappers" that  
> did not get ported, or only to the automagically generated fields?
>
> (By "wrapper" info, I mean the pararaph(s), sometimes containing  
> example(s), that appears at the top of each reference page.)
>
> jrs
>
> On Oct 31, 2007, at 6:21 PM, Benjamin Shine wrote:
>
>>
>> Tucker and I discussed this and came to the conclusion that we  
>> should have a single giant bug to track tons of 3.4 vs 4.1 doc  
>> mismatches. They will almost all end up needing to be reviewed by  
>> the API quorum anyways, and that is better done en masse than  
>> individually.
>>
>> LPP-5011 Reference Incosistencies between 3.4 Reference and 4.1  
>> Reference for the LFC
>> is our new friend. Append additional inconsistencies here.
>>
>> When we get up to paying attention to things-beyond-the-LFC then  
>> we might want to make separate bugs for "all things components"  
>> and "all things data". For now let's just focus on the LFC.
>>
>> -ben
>