[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [emacs-wiki-discuss] Re: Planner stable release
From: |
Thomas Gehrlein |
Subject: |
Re: [emacs-wiki-discuss] Re: Planner stable release |
Date: |
Thu, 25 Mar 2004 13:47:37 +0100 |
User-agent: |
Gnus/5.1002 (Gnus v5.10.2) Emacs/21.3 (gnu/linux) |
Sacha Chua <address@hidden> writes:
> address@hidden (Thomas Gehrlein) writes:
>
>> what do you think of a stable release of planner?
> I would like that.
>
> Of course, that means I need to resist the temptation to hack new
> features into emacs-wiki--sacha--1.0. Perhaps I should just branch off
> planner--stable--1.0.
Good idea.
> To keep the code neat and clean, I should only commit quick bugfixes when the
> original reporter has confirmed that the development branch is working, and
> add new features only when other people have confirmed no problems with a
> patch (and added whatever documentation they wanted).
Something like that.
> (Or something like that; I might be a poor judge of "stable".)
I'm not sure if "stable" is the right word for what I mean. But you got the
idea.
> Or I can just feature-freeze until all the existing features are
> documented, commit new features to the development branch, and commit
> them to stable only when people understand the features added. <grin>
Feature-freeze the stable version. If you branch off from today's planner
code, remove undocumented/experimental features. (i.e. planner-diary for
stable would not (yet) contain the code for schedule/apps and no code for
public/private diaries).
Maybe we should start by defining the feature scope of planner stable:
- Links (Gnus, BBDB, files)
- Tasks
- planner-diary
- remember ? (I don't use it)
- a stable version of emacs-wiki
BTW: Is this the right time to change the legacy key-bindings? Planner has
grown a lot since John started it, and while the key-bindings made sense for
early version of planner, they don't leave much room for new features.
Thomas