Release Schedule

[George Goldberg]

Sorry for the top post - just need to put this out there:

We *must* promote this as an *alpha* or *tech preview* or something
release. This is simply because we have completely bypassed the
correct procedures used by KDE for releasing software. Before we can
make any kind of final release, we need to go through the KDE Review
process and into extragear or somewhere. This is something we should
look at doing once we have made a couple more preview releases and the
basic feature set has settled down. For a technical preview release it
seems reasonable to release it as a git snapshot straight from
playground (where we currently reside), but for a proper release, this
is *not* OK.

2011/7/23 Martin Klapetek <martin.klapetek at gmail.com>:
> On Sat, Jul 23, 2011 at 11:16, George Kiagiadakis
> <kiagiadakis.george at gmail.com> wrote:
>>
>> 2011/7/23 Martin Klapetek <martin.klapetek at gmail.com>:
>> > On Sat, Jul 23, 2011 at 00:52, David Edmundson
>> > <david at davidedmundson.co.uk>
>> > wrote:
>> >>
>> >> On Fri, Jul 22, 2011 at 6:04 PM, Daniele E. Domenichelli
>> >> <daniele.domenichelli at gmail.com> wrote:
>> >> > On 21/07/11 00:40, David Edmundson wrote:
>> >> >> Ok, with the release happening, here is the plan:
>> >> >>   - Feature freeze as of tomorrow night. Any features after 10pm
>> >> >> tomorrow won't be in the first release
>> >> >>   - Fixes can go on till Friday night, keep fixing trunk
>> >> >>   - At this point, we make 0.1 branches in every component
>> >> >>   - These get packaged and shipped on Thursday
>> >> >
>> >> >
>> >> > Some questions:
>> >> >
>> >> > - Do we have scripts to create the tarballs?
>> >> No. Do we need them?
>>
>> git archive --format=tar --prefix=telepathy-kde-$COMPONENT-$VERSION/
>> HEAD | bzip2 -9 > telepathy-kde-$COMPONENT-$VERSION.tar.bz2
>>
>> ;)
>>
>> > Probably not.
>> >>
>> >> > - Where do we upload the tarballs?
>> >> Don't know - any ideas?
>> >
>> > Does KDE provide any kind of "release space"? Otherwise I think it's ok
>> > to
>> > put the tarballs to whatever place, important is to get links among
>> > people
>> > (we need to decide this ASAP so we can put those link in promo notes).
>>
>> The KDE ftp server. Someone needs to ask the sysadmins...
>
> <bcooksley> mck182: upload your files to upload.kde.org
> <bcooksley> there is a file there "README" which lays out the steps you need
> to take to get it uploaded
> <bcooksley> to the main ftp.kde.org + mirror network
>
>>
>> >>
>> >> > - Who will create the tarballs?
>> >> Don't know - volunteers?
>> >
>> > I know virtually nothing about packaging, so probably not me. But it
>> > should
>> > be just making a snapshot of the git repos, right?
>>
>> I can do that...
>> Snapshots of the git repos it is, unless we want to do something more
>> monolithic...
>>
>> PS: What should be the names of the tarballs? For some of the
>> comonents (for instance, the text-ui), the repo name is not the best
>> to use in the tarball. I would suggest to use the names that I used in
>> the debian packages (see [1]), but I'm open to other ideas...
>
> I agree. Let's go with these names. It will be less confusing for everyone.
>
>>
>> [1]. http://cgit.collabora.com/git/user/gkiagia (telepathy-kde-* repos)
>> _______________________________________________
>> KDE-Telepathy mailing list
>> KDE-Telepathy at kde.org
>> https://mail.kde.org/mailman/listinfo/kde-telepathy
>
>
> _______________________________________________
> KDE-Telepathy mailing list
> KDE-Telepathy at kde.org
> https://mail.kde.org/mailman/listinfo/kde-telepathy
>
>