Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Re: [dev] [announce] IMP H5 (6.1.0beta1)

4 views
Skip to first unread message

Michael M Slusarz

unread,
May 7, 2013, 12:47:44 PM5/7/13
to
Quoting Jan Schneider <j...@horde.org>:

> The Horde Team is pleased to announce the first beta release of the Internet
> Mail Program (IMP) version H5 (6.1.0).

[snip]

> * Allow uploading, drag & drop, and pasting of images into the
> HTML editor.

I guess we (I) should make this more clear. This is correct. But I
have also added support to drag/drop ANY attachment from the local
desktop as an attachment in dynamic view. That's a pretty nifty
feature IMHO.

[snip]

> The full list of changes can be viewed here:
>
> https://github.com/horde/horde/blob/768c3924e38f0155632c7adebffd57a975498aed/imp/docs/CHANGES

Given the recent "I upgraded minor versions/used git master and now
all my configuration options don't work!" we've seen on the mailing
lists, we really should put an extra blurb in the release announcement
demanding that docs/UPGRADING be read. PEAR has made it much easier
to upgrade; but it also gives the false (and incorrect) sense of
security that documentation no longer needs to be examined.

It would be even better if we could somehow cause a dialog/message to
be thrown when upgrading an application via package.xml. But don't
think there's a mechanism to do that.

michael

___________________________________
Michael Slusarz [slu...@horde.org]

--
dev mailing list
Frequently Asked Questions: http://wiki.horde.org/FAQ
To unsubscribe, mail: dev-uns...@lists.horde.org

Michael M Slusarz

unread,
May 7, 2013, 12:54:04 PM5/7/13
to
Quoting Michael M Slusarz <slu...@horde.org>:

> Quoting Jan Schneider <j...@horde.org>:
>
>> The Horde Team is pleased to announce the first beta release of the Internet
>> Mail Program (IMP) version H5 (6.1.0).

Also... you're going to release Horde_Core 2.5.0 today, correct? Or
else none of these packages is going to work as Horde and IMP (at a
minimum) require it.

Jan Schneider

unread,
May 7, 2013, 12:59:32 PM5/7/13
to

Zitat von Michael M Slusarz <slu...@horde.org>:

> Quoting Michael M Slusarz <slu...@horde.org>:
>
>> Quoting Jan Schneider <j...@horde.org>:
>>
>>> The Horde Team is pleased to announce the first beta release of
>>> the Internet
>>> Mail Program (IMP) version H5 (6.1.0).
>
> Also... you're going to release Horde_Core 2.5.0 today, correct? Or
> else none of these packages is going to work as Horde and IMP (at a
> minimum) require it.

It has been released today.
--
Jan Schneider
The Horde Project
http://www.horde.org/

Jan Schneider

unread,
May 7, 2013, 1:04:19 PM5/7/13
to

Zitat von Michael M Slusarz <slu...@horde.org>:

> Quoting Jan Schneider <j...@horde.org>:
>
>> The Horde Team is pleased to announce the first beta release of the Internet
>> Mail Program (IMP) version H5 (6.1.0).
>
> [snip]
>
>> * Allow uploading, drag & drop, and pasting of images into the
>> HTML editor.
>
> I guess we (I) should make this more clear. This is correct. But I
> have also added support to drag/drop ANY attachment from the local
> desktop as an attachment in dynamic view. That's a pretty nifty
> feature IMHO.
>
> [snip]

I think this was clear, I just incorrectly merged those two separate
items into one.

>> The full list of changes can be viewed here:
>>
>> https://github.com/horde/horde/blob/768c3924e38f0155632c7adebffd57a975498aed/imp/docs/CHANGES
>
> Given the recent "I upgraded minor versions/used git master and now
> all my configuration options don't work!" we've seen on the mailing
> lists, we really should put an extra blurb in the release
> announcement demanding that docs/UPGRADING be read. PEAR has made
> it much easier to upgrade; but it also gives the false (and
> incorrect) sense of security that documentation no longer needs to
> be examined.

We have this in Horde's release notes already. But it might make sense
to add them to all applications that have UPGRADING docs.

> It would be even better if we could somehow cause a dialog/message
> to be thrown when upgrading an application via package.xml. But
> don't think there's a mechanism to do that.

Unfortunately not.
0 new messages