How to promote less mature Frameworks?

[Kevin Ottens]

On Tuesday 19 August 2014 22:39:32 Cornelius Schumacher wrote:
> On Tuesday 19 August 2014 09:33:07 Kevin Ottens wrote:
> > On Tuesday 19 August 2014 08:44:10 David Faure wrote:
> > > 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.
> We already have a list on Inqlude with libraries under development (i.e.
> where there is a release, but which is not considered stable quality yet):
> http://inqlude.org/development.html, and a list with unreleased libraries
> (i.e. where there is no release yet, just a repository to grab the code
> from): http://inqlude.org/unreleased.html.

Ah-ah! Sounds about perfect.
 
> Adding some frameworks there based on information from the yaml file would
> be easy. At the moment all framework in the frameworks project are
> considered stable by Inqlude.

Okidoki, so just need to be adjusted to take the release key into account. If 
that's true it can be considered stable, otherwise it should go in the 
unreleased list.

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/20140820/90723ded/attachment.sig>