Sebastian Kügler | 16 Aug 12:13 2011
Picon

release team BoF writeup

Hey all,

I'm a bit behind on my backlog from the desktop summit. On the train though, I 
wrote down the results of the release team BoF, you can find them here.

It still needs wikifying, which is on my plate and I hope to get it pushed on 
top of my stack later this week.

Because you're curious (we all are), please already head over to 
http://vizzzion.org/blog/2011/08/release-team-changes/

Cheers,
--

-- 
sebas

http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9
Torgny Nyblom | 16 Aug 12:33 2011
Picon

Re: release team BoF writeup

On Tue, 16 Aug 2011 12:13:13 +0200, Sebastian Kügler wrote:
[...]
> Because you're curious (we all are), please already head over to
> http://vizzzion.org/blog/2011/08/release-team-changes/

If you don't get any suitable responses to your inquiries about backup 
people,
I would be interested in helping out with that or in general.

/Regards
Torgny
_______________________________________________
release-team mailing list
release-team <at> kde.org
https://mail.kde.org/mailman/listinfo/release-team
Raphael Kubo da Costa | 18 Aug 00:30 2011
Picon

Heads-up: kdeutils is moving to git

Hello there,

kdeutils is currently in the last stages of its migration to git: the
repositories have been created and I will do the initial pushes soon
(but probably not tomorrow, as I'll spend most of the day flying back to
Brazil).

The applications are all going to have separate repositories, but there
are no dependencies between the applications (ie. there is no
libkdeutils).

Nicolás Alvarez and I have recently done some changes to the buildsystem
so that it is possible to build kdeutils both as a whole module or each
application individually, so the 4.7 branch workflow does not need to be
changed (I don't know how Dirk is going to create the tarballs, though).

If there are objections or blocking questions, please post them here
asap, otherwise I think the migration should be finished during the
weekend.
_______________________________________________
release-team mailing list
release-team <at> kde.org
https://mail.kde.org/mailman/listinfo/release-team
Aaron J. Seigo | 18 Aug 07:47 2011
Picon

Re: Heads-up: kdeutils is moving to git

On Wednesday, August 17, 2011 19:30:59 Raphael Kubo da Costa wrote:
> The applications are all going to have separate repositories, but there are
> no dependencies between the applications (ie. there is nolibkdeutils).

please document clearly and publicly how to fetch and build the new set of 
repositories as one module.

in the past modules that have split up like this have done so with no 
documentation as to how to recreate the "whole module" build easily which has 
resulted in the loss of people who previously were regularly buliding the 
software. 

"use kdesrcbuild" and similar answers are not good enough, either: we need 
simple, straight-forward, copy-and-paste recipes to pass on to those who 
follow KDE from sources.

if there is no such documentation then i'll have to object to the splitting of 
this module. we've done enough damage to ourselves with the "split and worry 
about it later" approach.

thanks for your understanding ...

--

-- 
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Qt Development Frameworks
(Continue reading)

Sebastian Kügler | 18 Aug 10:53 2011
Picon

Re: Heads-up: kdeutils is moving to git

On Thursday, August 18, 2011 07:47:56 Aaron J. Seigo wrote:
> On Wednesday, August 17, 2011 19:30:59 Raphael Kubo da Costa wrote:
> > The applications are all going to have separate repositories, but there
> > are no dependencies between the applications (ie. there is
> > nolibkdeutils).
> 
> please document clearly and publicly how to fetch and build the new set of 
> repositories as one module.
> 
> in the past modules that have split up like this have done so with no 
> documentation as to how to recreate the "whole module" build easily which
> has  resulted in the loss of people who previously were regularly buliding
> the software.
> 
> "use kdesrcbuild" and similar answers are not good enough, either: we need 
> simple, straight-forward, copy-and-paste recipes to pass on to those who 
> follow KDE from sources.
> 
> if there is no such documentation then i'll have to object to the splitting
> of  this module. we've done enough damage to ourselves with the "split and
> worry about it later" approach.
> 
> thanks for your understanding ...

We also need this from the release team POV. So if you move, please

- don't do it too shortly before tagging a patchlevel release

- let us know how we can reassemble the tarball for our release

(Continue reading)

Raphael Kubo da Costa | 19 Aug 03:21 2011
Picon

Re: Heads-up: kdeutils is moving to git

On Thu, Aug 18, 2011 at 5:53 AM, Sebastian Kügler <sebas <at> kde.org> wrote:
> We also need this from the release team POV. So if you move, please
>
> - don't do it too shortly before tagging a patchlevel release

I'm planning on doing it this weekend, which is a bit less than 2
weeks than the tagging of 4.7.1. Would that be enough?

> - let us know how we can reassemble the tarball for our release
>
> Please check with Dirk wether it works or not, as to cause as little
> disruption to our release process as possible. But you know all that, since
> you've taken part in all those discussions =)

Basically, the current CMakeLists.txt in svn can still be used, but an
even smaller version which just does a series of
macro_optional_add_subdirectory() calls. Going back to Aaron's
message, where should I put these instructions?

Dirk, do you need me to do anything specific for your tarballing needs?
_______________________________________________
release-team mailing list
release-team <at> kde.org
https://mail.kde.org/mailman/listinfo/release-team
Thomas Zander | 19 Aug 13:31 2011
Picon

Re: Heads-up: kdeutils is moving to git

On Thursday 18 August 2011 22.21.46 Raphael Kubo da Costa wrote:
> Basically, the current CMakeLists.txt in svn can still be used, but aneven 
smaller version which just does a series ofmacro_optional_add_subdirectory() 
calls. Going back to Aaron'smessage, where should I put these instructions?

Is there a kdeutils.git repo where this can be put?

I fully agree with Aarons message; the amount of time spent tracking down sub-
projects and their git checkout line is a big cause of worry for me too.

I had had the wish in the past to have a simple repo for a (former) module 
like kdeutils, and kdegraphics etc and that that module would have at minimum 
a script to do the checkout of the other repositories.

What do others think about a solution of that kind?
And is it applicable to our other (former) modules too?

Yury G. Kudryashov | 19 Aug 13:37 2011
Picon

Re: Heads-up: kdeutils is moving to git

Thomas Zander wrote:

> What do others think about a solution of that kind?
> And is it applicable to our other (former) modules too?
There is a "superbuild" script; you can find details in kde-buildsystem ML.
--

-- 
Yury G. Kudryashov,
mailto: urkud <at> mccme.ru

Jeremy Whiting | 19 Aug 14:25 2011
Picon

Re: Heads-up: kdeutils is moving to git

I'm looking to migrate kdeaccessibility this weekend also.  It's mostly ready, just polishing it a bit in svn first (making each application build on its own or part of kdeaccessibility).  I'll backport these changes to the 4.7 branch when it's in git.

I'm wondering the same thing, kdeaccessibility has a Mainpage.dox (as did kdeedu before it split) that we are wondering where to keep also, besides the top CMakeLists.txt for the released tarball.  I agree a git repo for each module makes sense rather than putting this stuff into superbuild (which I discussed with Allen the other night). So it would be something like this:

kdeaccessibility.git (holds CMakeLists.txt, and Mainpage.dox)
-- jovie.git
--kaccessible.git
--kmag.git
--kmousetool.git
--kmouth.git

with similar setups for kdeedu, kdegraphics, etc.

On the other hand if Dirk is going to use superbuild to do the release tarballs we could just "dump" this non-superbuild stuff into there Mainpage.dox, any top level README, etc. since we need to have module specific CMakeLists.txt in there anyway for superbuild to work.

thoughts?
Jeremy

On Fri, Aug 19, 2011 at 5:37 AM, Yury G. Kudryashov <urkud.urkud <at> gmail.com> wrote:
Thomas Zander wrote:

> What do others think about a solution of that kind?
> And is it applicable to our other (former) modules too?
There is a "superbuild" script; you can find details in kde-buildsystem ML.
--
Yury G. Kudryashov,
mailto: urkud <at> mccme.ru

_______________________________________________
release-team mailing list
release-team <at> kde.org
https://mail.kde.org/mailman/listinfo/release-team

<div>
<p>I'm looking to migrate kdeaccessibility this weekend also.&nbsp; It's mostly ready, just polishing it a bit in svn first (making each application build on its own or part of kdeaccessibility).&nbsp; I'll backport these changes to the 4.7 branch when it's in git.<br><br>I'm wondering the same thing, kdeaccessibility has a Mainpage.dox (as did kdeedu before it split) that we are wondering where to keep also, besides the top CMakeLists.txt for the released tarball.&nbsp; I agree a git repo for each module makes sense rather than putting this stuff into superbuild (which I discussed with Allen the other night). So it would be something like this:<br><br>kdeaccessibility.git (holds CMakeLists.txt, and Mainpage.dox)<br>-- jovie.git<br>--kaccessible.git<br>--kmag.git<br>--kmousetool.git<br>--kmouth.git<br><br>with similar setups for kdeedu, kdegraphics, etc.<br><br>On the other hand if Dirk is going to use superbuild to do the release tarballs we could just "dump" this non-superbuild stuff into there Mainpage.dox, any top level README, etc. since we need to have module specific CMakeLists.txt in there anyway for superbuild to work.<br><br>thoughts?<br>Jeremy<br><br></p>
<div class="gmail_quote">On Fri, Aug 19, 2011 at 5:37 AM, Yury G.  Kudryashov <span dir="ltr">&lt;<a href="mailto:urkud.urkud <at> gmail.com">urkud.urkud <at> gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote">
<div class="im">Thomas Zander wrote:<br><br>
&gt; What do others think about a solution of that kind?<br>
&gt; And is it applicable to our other (former) modules too?<br>
</div>There is a "superbuild" script; you can find details in kde-buildsystem ML.<br>--<br>
Yury G. Kudryashov,<br>
mailto: <a href="mailto:urkud <at> mccme.ru">urkud <at> mccme.ru</a><br><div>
<div></div>
<div class="h5">
<br>
_______________________________________________<br>
release-team mailing list<br><a href="mailto:release-team <at> kde.org">release-team <at> kde.org</a><br><a href="https://mail.kde.org/mailman/listinfo/release-team" target="_blank">https://mail.kde.org/mailman/listinfo/release-team</a><br>
</div>
</div>
</blockquote>
</div>
<br>
</div>
Raphael Kubo da Costa | 20 Aug 21:34 2011
Picon

Re: Heads-up: kdeutils is moving to git

Raphael Kubo da Costa <kubito <at> gmail.com> writes:

> Hello there,
>
> kdeutils is currently in the last stages of its migration to git: the
> repositories have been created and I will do the initial pushes soon
> (but probably not tomorrow, as I'll spend most of the day flying back to
> Brazil).
>
> The applications are all going to have separate repositories, but there
> are no dependencies between the applications (ie. there is no
> libkdeutils).
>
> Nicolás Alvarez and I have recently done some changes to the buildsystem
> so that it is possible to build kdeutils both as a whole module or each
> application individually, so the 4.7 branch workflow does not need to be
> changed (I don't know how Dirk is going to create the tarballs, though).
>
> If there are objections or blocking questions, please post them here
> asap, otherwise I think the migration should be finished during the
> weekend.

kdeutils has finished moving to git; I have done the initial pushes to
all repositories and svn only has a MOVED_TO_GIT file.

As for the concerns about being able to build everything as a single
module, I've created a scratch git repository [1] containing the files that
used to be in the top-level kdeutils directory in SVN, including
CMakeLists.txt. I am open to where to put these instructions in TechBase
or anywhere else you think they are needed.

[1] $ git clone kde:scratch/rkcosta/kdeutils-toplevel
_______________________________________________
release-team mailing list
release-team <at> kde.org
https://mail.kde.org/mailman/listinfo/release-team

Gmane