KDE SC Release Packaging Thoughts

Anne-Marie Mahfouf annemarie.mahfouf at free.fr
Tue May 1 18:00:53 UTC 2012


On 05/01/2012 02:59 PM, Allen Winter wrote:
> Seems we have general agreement on this outline then.
> Now let's review where we stand.
>
> On Friday 27 April 2012 6:18:06 PM Allen Winter wrote:
>
>> 1. the Continuous Integration (CI) System
>>
>>   - all the KDE SC modules are built continuously
> So we have build.kde.org and a lot of modules are already being built continuously.
> Partial Done
>
>>   - no packaging unless all modules build ok
> Will be done as part of the packaging tools
>
>>     (even better would be to force all make tests too)
> a dream..  a goal to work towards
>
>>   - the packaging tools run on the CI system generating "test" tarballs.
> Todo
>
>>   - the "test" tarballs could be downloaded from the CI system
> Todo
>
>
>> 2. the KDE Sysadmin Team
>>
>>   - provides and manages the CI system
> Done
>
>>   - will transfer "test" tarballs to the public ftp site
> Todo
>
>>   - prepares the public ftp site for bandwidth requirements at release announce time
> Todo
>
>
>> 3. the KDE Promo Team
>>
>>   - writes and distributes release announcements through normal channels
> Done
>
>>   - deals with the media
> Done
>
>>   - manages public expectations
> Done
>
>> 4. the KDE i18n Team
>>
>>   - maintains the languages list
> Done,  see kde-common/release/language_list
>
>> 5. the KDE Release Team
>>
>>   - coordinates the entire release effort
> We can do better
>
>>   - sets release milestones and dates
> Done
>
>>   - communicates important dates to the community and to distros
> We can do better
>
>>   - communicates important news to the community and to distros
> We can do better
>
>>   - creates "test" tarballs using the CI system and handles distro feedback
> Todo
>
>>   - adds hot and security patches to the tarballs before the final release
> Todo
>
>>   - creates "final" tarballs using the CI system
> Todo
>
>>   - pushes tags to the module repositories in a timely manner
> Todo
>
>>   - writes and maintains the necessary tools
> Todo
>
>>   - writes and maintains the release process documentation
> Todo
>
>
> So need people to start helping out .
> I see 2 big categories of need: 1) the CI work  2) the release team work
>
> Gotta run now.
> But feel free to chime-in with ideas on any of the above items.
>
> -Allen
> _______________________________________________
Thanks for setting this up, I am not much of an admin guru or a script 
wizard so I don't know what I can do but feel free to assign me any 
tasks within my range of action!

Best regards,

Anne-Marie


More information about the release-team mailing list