[Dev] HISTORY.txt

[Ted Leung]

In the long run, we'll probably need a pair of history/changelog 
documents.  One for end users detailing end user functionality 
improvements/changes, and one for developers that describes changes 
relevant to their interests.

Ted

On Nov 9, 2004, at 2:27 PM, Chih-Chao Lam wrote:

> I don't think end users are going to care too much about history.txt 
> directly. At the least, we'll need to synthesize the info and present 
> it a more user friendly manner.
>
> chao
>
> On Nov 9, 2004, at 2:22 PM, Ducky Sherwood wrote:
>
>> At Heikki's request, I've started maintaining HISTORY.txt.  Neither 
>> of us are really sure who HISTORY.txt's customers are -- end users or 
>> developers? -- so it's unclear how much detail to put in.
>>
>> For example, in this release, we didn't put in that Chandler now 
>> always runs RefCounted so pinning isn't required.  That's clearly an 
>> implementation detail, something that end-users wouldn't care about.  
>> However, if we had a third-party parcel developer who was pinning 
>> code,  s/he might want to know about that.
>>
>> So: what do we collectively want from HISTORY.txt?
>>
>> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>>
>> Open Source Applications Foundation "Dev" mailing list
>> http://lists.osafoundation.org/mailman/listinfo/dev
>
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
>
> Open Source Applications Foundation "Dev" mailing list
> http://lists.osafoundation.org/mailman/listinfo/dev
>
----
Ted Leung                 Open Source Applications Foundation (OSAF)
PGP Fingerprint: 1003 7870 251F FA71 A59A  CEE3 BEBA 2B87 F5FC 4B42