How to promote less mature Frameworks?

[Kevin Ottens]

On Tuesday 19 August 2014 08:44:10 David Faure wrote:
> On Friday 15 August 2014 12:51:58 Kevin Ottens wrote:
> > And that's the problem if we release them. If it's released "with the
> > rest" expect people to have wrong expectations about them.
> > 
> > A possibility would be perhaps to produce nightly tarballs for those
> > frameworks which don't have the "release: true" flag. This way they keep
> > not being part of a release, and early adopters have something easy to
> > grab.
>
> Wouldn't early adopters just checkout and build from git ?

Well, I guess some of them might just want to grab something and run with it. 
Maybe not the majority indeed...

> I don't know about you, but I almost never download a source tarball,
> because a git checkout is just so much easier to update later.
> We mostly make tarballs for packagers, and the non-mature frameworks we're
> talking about should definitely NOT be packaged.

Agreed.

> IMHO the solution is just to publicize the upcoming frameworks somewhere.

Which shouldn't be that hard, it's "only" about processing the yaml file and 
creating a page listing them. I think that's what makes most sense indeed.

Regards.
-- 
Kévin Ottens, http://ervin.ipsquad.net

KDAB - proud supporter of KDE, http://www.kdab.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20140819/17e22424/attachment.sig>