Packaging scripts for frameworks

[Kevin Ottens]

Hello,

On Saturday 21 December 2013 12:38:17 Albert Astals Cid wrote:
> > How should we proceed about this?
> 
> Easy pasrt: tarball + repo tag.
> 
> Then you need to find a place to set it up in the download server.
> I think we should put the stable ones in
> http://download.kde.org/stable/ and the others in
> http://download.kde.org/unstable/.
> 
> But which kind of subpaths do you want?
> frameworks/$frameworkName/allReleasesInHere?
> $frameworkName/allReleasesInHere?
> 
> I'd go for the first, otherwise the number of folders in the "root" is going
> to explode.

Agreed... or...
frameworks/$version/tarballsOfEachFrameworksForGivenVersion
(frameworks/5.0 would contain karchive-5.0.tar.bz2 and friends)
Or is it too foreign to what we currently do?

I don't mind either way, just seemed like another natural option to me.

> Also you could do against the unstable/stable thing and just use stable for
> everything like akonadi does[1] but honestly I do think that it's not a good
> idea.

Agreed.

> Now, the hard part, how's versioning going to go now and in the future?
> I see you want to do a 5.0 of two frameworks and unstable of the others, so
> let's say 5.0.0 for karchive/threadweaver and 4.9.50 for the others.

Let's keep it simple and make it 4.9.50 for all of them. We can't exclude that 
karchive or threadweaver won't see some changes between now and the 5.0.

> But what about the future? Will there be a 5.0 of the others or will skip to
> 5.1? If there will be a 5.0 of the others will it be 5.0.0 or 5.0.1 and
> then release also the karchive/threadweaver 5.0.1?
> 
> I'm asking when you decide to release non beta versions of
> karchive/threadweaver/kconfig are they version numbers going to be in sync?
> Because our scripts work with the assumption that all you release has the
> same version number.

I think we should keep it that way for the frameworks. They will all have the 
same version number always.

Let's not make it too complicated. The promise was that we would make a tech 
release which would contain at least karchive and threadweaver in a usable 
state, at least I don't remember saying those two would be final and not the 
rest.

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/release-team/attachments/20131221/8658407a/attachment.sig>