[dev] Release plan

[Roel Gloudemans]

I like the tabs. It could be a useful feature to add to the interface. The
"iconbar" on top now contacts icons which call up other pages (e.g. in IMP
Inbox; Folders; Options) and icons which call up popup windows (e.g. Help;
Compose (depends on setting))

We could make the Icons that call up other pages within the same application
show up as tabs and the icons that call popups as icons.

This also means that the icons should be sorted before displaying, to 
make sure
that there is an unbroken row of tabs.

How does this sound?

Cheers,
Roel.

> I use a really heavily hacked version of Horde/Imp taken from CVS a 
> year or two
> ago when work started on Horde3/IMP4.  I still find it much nicer to use than
> the current versions interface-wise and would like to apply my 
> facelift to the
> current codebase to bring it back to current.
>
> But it was quite a hack the first time round and might involve some 
> code change,
> is this the right time to do it, or wait until a beta/RC is released?
>
> Screenshots here:
> http://willow.ijichi.org/imp/
>
> dom
>
> Quoting Jan Schneider <jan at horde.org>:
>
>> So, this is my release plan:
>>
>> Note that this matters only for the applications of the first release round,
>> i.e. Horde, IMP, Turba, Ingo, Chora, Kronolith, Nag, and Mnemo.
>>
>> I'm going to release the BETA versions next week. We will then enter the
>> "major feature freeze mode". That means that only bug fixes and small
>> feature enhancements and completions are allowed to be committed.
>>
>> After one to two weeks I'll start the release candidate phase. Release
>> candidates will be released once per week until we think they are stable
>> enough to release the final versions. During this period we are in complete
>> feature freeze mode, i.e. only bug fixes, documentation and translations are
>> allowed to be committed.
>>
>> I reconsidered the original branching plan and will now try to avoid
>> branching as long as possible, ideally until the final releases, for two
>> reasons: To avoid the hassle of merging as long as possible, and to force
>> us to spend our time on bug fixes. This goes a bit beyond the nature of
>> volunteer oss development but this phase will only last for a few weeks and
>> we won't get the releases out of the door in this life otherwise.
>>
>> Comments?
>>
>> Jan.
>>
>> --
>> Do you need professional PHP or Horde consulting?
>> http://horde.org/consulting/
>>
>> --
>> Horde developers mailing list - Join the hunt: http://horde.org/bounties/
>> Frequently Asked Questions: http://horde.org/faq/
>> To unsubscribe, mail: dev-unsubscribe at lists.horde.org
>
>
> ------------------------------------------
> This message was penned by the hand of Dom
>
> --
> Horde developers mailing list - Join the hunt: http://horde.org/bounties/
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: dev-unsubscribe at lists.horde.org
>


----- End message from dom at ijichi.org -----