Release Schedule

David Edmundson david at davidedmundson.co.uk
Sat Jul 23 00:59:45 CEST 2011


2011/7/22 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?
>
>
> 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).
>
>>
>> > - 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 had planned to make a branch of every repository we're shipping
>> called telepathy-kde-0.1.
>> It's how telepathy-qt4 do it, and they're generally good at everything.
>>
>> From here anyone can generate a tarball.
>>
>> Dear packagers,
>> What stuff do you need?
>> If you run a repo, could you let me know with the address, and update
>> this wiki page
>> http://community.kde.org/Real-Time_Communication_and_Collaboration/Packaging_Guide
>>
>> >
>> > About the blog post(s) announcing the release, we have a lot of things
>> > to say, but not many people will read a long article, so we were
>> > thinking about having several posts, one per component. What do you
>> > think about writing blog posts following the same schema? For example:
>> >
>> > [Announcement] Telepathy-KDE 0.1 released! part X of Y - component name
>> >   [...]
>> >   description of the component
>> >   [...]
>> >   Links to the other parts of the announcement
>> >
>> Fine by me, I volunteer to do one post, any others? Decide who does what.
>
> I'm taking contact list.
ok, I think of the Accounts KCM as my baby (even though it's more like
I adopted it) so I'll have that.
> --
> Marty K.
>
>>
>> >
>> > Cheers,
>> >  Daniele
>> > _______________________________________________
>> > 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
>
>
> _______________________________________________
> KDE-Telepathy mailing list
> KDE-Telepathy at kde.org
> https://mail.kde.org/mailman/listinfo/kde-telepathy
>
>


More information about the KDE-Telepathy mailing list