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
Sorry I don't think I'll be able to help on this after all, I'm getting
overburdened with my still recovering health.
Jonathan
___
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team
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
On 05/01/2012 07:02 PM, Torgny Nyblom wrote:
On Tuesday 01 May 2012 08.59.41 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
On Tuesday 01 May 2012 20.02.55 Anne-Marie Mahfouf wrote:
On 05/01/2012 07:02 PM, Torgny Nyblom wrote:
On Tuesday 01 May 2012 08.59.41 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
On Friday 27 April 2012 18.18.06 Allen Winter wrote:
Howdy,
I started jotting down some thoughts about a brand new KDE SC Release
Process at
http://techbase.kde.org/User:Winterz. For your convenience, a copy of that
wiki
page is enclosed below.
Let's discuss what I wrote there.
[...]
will eventually
make the final decisions on things.
= start wiki =
KDE SC Release Packaging Thoughts
1. the Continuous Integration (CI) System
- all the KDE SC modules are built continuously
- no packaging unless all modules build ok
(even better would be to force all make tests too
