[Kde-pim] What's up with kdepim*?

Jeremy Whiting jpwhiting at kde.org
Mon Jul 20 13:26:23 UTC 2015


The problem isn't that pim wants to be released again, the problem is
pim people (maybe you, I can't recall) asked for it to not get
released from master until further notice. Then no notice was given.
Notice 3 days after dependency freeze isn't a good idea, causes more
rush and stress on our release team. At any rate if pim depends on
parts of akonadi which are in frameworks that haven't been released,
then we can't release pim until after the first frameworks release
that has what's depended on (or we could put the missing dependency in
the applications release, but that's a bad idea as when would it then
get moved to frameworks release cyle?)


On Mon, Jul 20, 2015 at 7:21 AM, Aleix Pol <aleixpol at kde.org> wrote:
> On Mon, Jul 20, 2015 at 3:19 PM, laurent Montel <montel at kde.org> wrote:
>> Le Monday 20 July 2015, 06:45:31 Jeremy Whiting a écrit :
>>> TLDR we can't release applications that depend on an unreleased framework...
>> ?
>> So we can release an application which depends on lib which is not released ?
> Framework is a synonym for library. It doesn't make a difference, I'd
> say. Releasing with unreleased dependencies means that distributors
> can't ship what we release, therefore it's a bogus release.
> Aleix

More information about the release-team mailing list