Improving the LiveCode release notes

[Peter Haworth]

I  guess this next thought would be dealt with if we had the search
capability that's been mentioned but I'd prefer the release notes to be
ordered primarily by the release (DP!, DP2, etc) and within that the
various sections for that release (Engine Changes, IDE Changes, Bug Fixes,
etc).

I agree with Monte that the whole section on Platform Support,
Installation, etc should be in a separate document with the release notes
only documenting any changes that apply to that document.

The LC8 Release notes also include several pages of information about
widgets which I think should be in a separate document, referred to by the
release notes where necessary.  But then that gets into the whole issue of
getting the User Guide updated (or having a separate Widgets Guide), which
is where the Widget information should be.

Having said all that, I think LC8 is not a typical release since there have
been so many DP releases and presumably there'll be RC releases too before
we're done.

Going back to the search issue, I'd be willing to spend some time creating
a database and an LC app to query, sort and extract.  Creating the DB and
the app won't be difficult, populating the db will be the hard part since I
think everything is in pdf format.

Pete
lcSQL Software <http://www.lcsql.com>
Home of lcStackBrowser <http://www.lcsql.com/lcstackbrowser.html> and
SQLiteAdmin <http://www.lcsql.com/sqliteadmin.html>

On Tue, Dec 15, 2015 at 9:16 AM, Mark Wieder <mwieder at ahsoftware.net> wrote:

> On 12/15/2015 01:00 AM, Peter TB Brett wrote:
>
> How about alphabetizing the Dictionary Additions and Dictionary Changes
>>> lists?
>>>
>>
>> Good plan.
>>
>> How useful are those sections?  Does anyone actually rely on them for
>> anything?
>>
>
> Well, *I* do, but maybe it's just me. When we do weekly releases at work I
> do the same for historical tracking. Otherwise it's really hard to query a
> bug-tracking tool (I'm talking at you, bugzilla) to get a list of the bugs
> that were fixed/features added for a given release. If a bug that was fixed
> in a previous release pops up again in a later one, I can go back in the
> release notes and see when it was fixed, and that narrows the window for
> finding the code changes. But if I'm the only one who cares about this
> stuff then I'm ok with dropping the sections from the release notes.
>
> --
>  Mark Wieder
>  ahsoftware at gmail.com
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>