[kde-release-team] Re: New module: KPkPass

Albert Astals Cid aacid at kde.org
Tue Mar 20 21:07:02 GMT 2018


El dimarts, 20 de març de 2018, a les 7:20:21 CET, Ben Cooksley va escriure:
> On Tue, Mar 20, 2018 at 10:36 AM, Sandro Knauß <sknauss at kde.org> wrote:
> > Hey,
> > 
> > On Montag, 19. März 2018 20:26:36 CET Volker Krause wrote:
> >> On Monday, 19 March 2018 18:15:49 CET Jonathan Riddell wrote:
> >> > On Mon, Mar 19, 2018 at 06:04:51PM +0100, Volker Krause wrote:
> >> > 
> >> > https://community.kde.org/Policies/Application_Lifecycle
> >> > 
> >> > > (1) We do not do "direct-to-frameworks" releases, ie. new modules
> >> > > should
> >> > > be battle-tested elsewhere before moving to KF5.
> >> > 
> >> > I don't know of that but once in frameworks there's strict ABI
> >> > requirements
> >> > 
> >> > so it's usually best to test elsewhere.  Self released extragear is
> >> > easy
> >> > enough.
> >> 
> >> Can Application modules depend on libraries from Extragear releases
> >> though?
> > 
> > Why not? Applications can depend on everything external and internal KDE
> > including Extragear.
> 
> The only restriction here is that the Extragear component is released
> prior to Applications making it's release.
> (ie. you shouldn't be dependent on the latest git version)
> 
> Otherwise there is no limitation on Applications -> Extragear (or
> Plasma as the case may be)
> 
> Playground on the other hand is quite different - nothing outside
> Playground may depend on something in Playground.

I don't agree there, if we can make unstable releases from playground, then we 
can make things depend on them. Ideally optionally, but I don't see the 
problem in depending on something that has had a tarball released.

Cheers,
  Albert



More information about the kde-pim mailing list