Regarding Winterfell - Was: Re: PHP Fatal error: Class 'Sabre\VObject\Property\Text' not found (partially solved)

[Timotheus Pokorra]

Hello Aaron or Jeroen,

can you please comment on the issues of stability in Winterfell? See
conversation below.
What can the community do to help with this?

Thank you,
  Timotheus

On 28 June 2016 at 13:48, hede <kolab983 at der-he.de> wrote:
> Am Mon, 27 Jun 2016 07:41:34 +0200 schrieb Timotheus Pokorra <timotheus at kolab.org>:
>
>> I have another Winterfell problem with Guam, already broken for two
>> weeks: https://git.kolab.org/T1305, on CentOS7. It seems I did not yet
>> get the attention of Aaron, the author of guam. On the other hand
>> nobody else confirmed the issue either, although it is totally
>> reproducible for me. I cannot access IMAP folders at all.
>
> The developers do not test their changes. If Winterfell breaks, it breaks and it stays in this state. Maybe it's even intended to break...
>
> guam is one good example. Jeroen yesterday did some changes to guam. It compiled before he'd begun, he committed some changes, since then it doesn't even compile... it's left in that state.
>
> Second example: Since its first commit, the debian.rules file for guam has a nonfunctional line. It simply doesn't work this way and was committed without testing any functionality - there is none.
>
> Winterfells seems not to be as stable as other development platforms. Elsewhere its common to demand authors to check their commits. Like with Debian unstable or even experimental for example - unusable builds are quite uncommon, even with frequent changes. Developers are encouraged to commit only coherent changes into the non-private development repositories. Kolab:Winterfell is quite different here, leaving packages in a broken state seems quite common.
>
> regards
> hede