On Thu, Mar 5, 2009 at 6:16 AM, TL <[email protected]> wrote:

>
> Speaking of Leo's feature explosion, is there a 'changes' list which
> chronologically itemizes new and changed _features_ ?


Yes.  See the 'Projects' section of leoPy.leo.  This becomes the basis for
the 'What's New in Leo' documents in LeoDocs.leo and on the web site.

>
> Case in point, 2 weeks from now I will forget that the name
> of this cool feature is 'nodeActions', I will search my mail
> guessing at keywords etc, find this email maybe quickly,
> maybe slowly, maybe give up.


The proper place for any info re plugins is in leoPlugins.leo

>
> It seems this list should be somehow created via filtering
> commit messages, don't know if that's possible. It probably
> won't work if it requires an additional task.


I understand that this is a frequently requested feature, but it's a dubious
project at best.

It reminds me of another P.J. Plauger saying: "The only thing worse than no
Standard (for C) would be two standards".

Imo, any kind of "system" for tracking bugs, features, whatever, has the
same defect.  There *already is* a way of tracking what has been done,
namely the entries I (or others) make in various .leo files.  This way is
natural, and better than any other way, because for this kind of thing the
Leo way is best.

I tolerate the bug tracker on launchpad because it allows others to provide
bug reports without doing bzr commits.  But I have absolutely no interest in
duplicating the work that I already do in documenting what has been done
recently.

Each new official release contains a "What's New" section.  I suspect few
pay it much attention, but I do it because it would be strange not to do
it.  It doesn't take much work: the project entries remind me of everything
that needs to be said.

Edward

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to