David Faure | 1 Feb 13:03 2011
Picon

Re: MALLOC_CHECK_=3 in 4.6.0

On Wednesday 26 January 2011, Will Stephenson wrote:
> We forgot to disable this when branching 4.6, which kills Eclipse:
> https://bugs.kde.org/show_bug.cgi?id=247398

Someone forgot to follow the steps listed in kde-common/release/RELEASE-
CHECKLIST ;)

--

-- 
David Faure, faure@..., http://www.davidfaure.fr
Sponsored by Nokia to work on KDE, incl. Konqueror (http://www.konqueror.org).
Jonathan Riddell | 1 Feb 19:40 2011

Re: Minor Point Relase Policy Draft

On Mon, Jan 24, 2011 at 06:45:49PM +0000, Albert Astals Cid wrote:
> > > > > > > http://techbase.kde.org/Policies/Minor_Point_Release_Policy/Draft

> So did anyone have a look at my edits to that page? Do they make sense for 
> you? It's something we could agree on?

Yes that looks good, thanks Albert.

Jonathan
Tom Albers | 5 Feb 22:13 2011
Picon

Minor releases KDE 4.6

Hi,

I've adapted the app to include a schedule for minors as well. Release on 1st tuesday of the month + tagging on
the thursday before. This results in:

=== Thursday, February 24, 2011: KDE 4.6.1 tagging ===
=== Tuesday, March 1, 2011: KDE 4.6.1 release ===
=== Thursday, March 31, 2011: KDE 4.6.2 tagging ===
=== Tuesday, April 5, 2011: KDE 4.6.2 release ===
=== Thursday, April 28, 2011: KDE 4.6.3 tagging ===
=== Tuesday, May 3, 2011: KDE 4.6.3 release ===
=== Thursday, June 2, 2011: KDE 4.6.4 tagging ===
=== Tuesday, June 7, 2011: KDE 4.6.4 release ===
=== Thursday, June 30, 2011: KDE 4.6.5 tagging ===
=== Tuesday, July 5, 2011: KDE 4.6.5 release ===

I think the amount of backporting decreases a bit at the end, so an alternative would be to delay the .4
tagging/release 1 month and not do a .5. I'ld vote for this alternative personally.

If ok, I'll add it to techbase and the ical, together with the KDE 4.7 schedule Albert suggested. 

Best,

--

-- 
Tom Albers
KDE Sysadmin
Albert Astals Cid | 6 Feb 13:33 2011
Picon

Re: Minor releases KDE 4.6

A Dissabte, 5 de febrer de 2011, Tom Albers va escriure:
> Hi,
> 
> I've adapted the app to include a schedule for minors as well. Release on
> 1st tuesday of the month + tagging on the thursday before. This results
> in:
> 
> === Thursday, February 24, 2011: KDE 4.6.1 tagging ===
> === Tuesday, March 1, 2011: KDE 4.6.1 release ===
> === Thursday, March 31, 2011: KDE 4.6.2 tagging ===
> === Tuesday, April 5, 2011: KDE 4.6.2 release ===
> === Thursday, April 28, 2011: KDE 4.6.3 tagging ===
> === Tuesday, May 3, 2011: KDE 4.6.3 release ===
> === Thursday, June 2, 2011: KDE 4.6.4 tagging ===
> === Tuesday, June 7, 2011: KDE 4.6.4 release ===
> === Thursday, June 30, 2011: KDE 4.6.5 tagging ===
> === Tuesday, July 5, 2011: KDE 4.6.5 release ===
> 
> I think the amount of backporting decreases a bit at the end, so an
> alternative would be to delay the .4 tagging/release 1 month and not do a
> .5. I'ld vote for this alternative personally.
> 
> If ok, I'll add it to techbase and the ical, together with the KDE 4.7
> schedule Albert suggested.

+1

Albert

> 
(Continue reading)

Anne-Marie Mahfouf | 8 Feb 17:36 2011
Picon

KDE-Edu 4.6 branch: svn or git?

Hi all,

We're planning to move the kdeedu module to git soon and we will split it so 
that each application will be built on its own.

Should we keep kdeedu 4.6 branch in svn in order to allow the same packaging 
than for the 4.6.0 release?

Thanks in advance for your reply, best regards,

Anne-Marie
Tom Albers | 8 Feb 21:31 2011
Picon

Re: Minor releases KDE 4.6

4.6 minors and 4.7 Pushed to techbase and ics.

Toma
Frederik Schwarzer | 8 Feb 23:12 2011
Picon

Re: KDE-Edu 4.6 branch: svn or git?

On 08/02/2011, Anne-Marie Mahfouf <annemarie.mahfouf@...> wrote:

Hi,

> We're planning to move the kdeedu module to git soon and we will split it so
> that each application will be built on its own.
>
> Should we keep kdeedu 4.6 branch in svn in order to allow the same packaging
> than for the 4.6.0 release?

While kdelibs and kdebase are still there in SVN, they do not get any
updates anymore. So it seems 4.6 development for these modules happens
in Git now.

If it remains that way, packging will not be the same as for 4.6.0
anyway. Can we do that or is it not a good idea to switch package
layouts (as for kdebase) within one major version?

Regards
Ian Monroe | 8 Feb 23:17 2011
Picon

Re: KDE-Edu 4.6 branch: svn or git?

On Tue, Feb 8, 2011 at 16:12, Frederik Schwarzer
<schwarzerf@...> wrote:
> On 08/02/2011, Anne-Marie Mahfouf <annemarie.mahfouf@...> wrote:
>
> Hi,
>
>> We're planning to move the kdeedu module to git soon and we will split it so
>> that each application will be built on its own.
>>
>> Should we keep kdeedu 4.6 branch in svn in order to allow the same packaging
>> than for the 4.6.0 release?
>
> While kdelibs and kdebase are still there in SVN, they do not get any
> updates anymore. So it seems 4.6 development for these modules happens
> in Git now.
>
> If it remains that way, packging will not be the same as for 4.6.0
> anyway. Can we do that or is it not a good idea to switch package
> layouts (as for kdebase) within one major version?

Well this was discussed with Dirk beforehand, so we're just doing the
same thing for kdeedu. Kdeedu is 21 repos so its a different magnitude
of a change.

Ian
David Faure | 12 Feb 11:21 2011
Picon

Re: who should I list as kde project manager

On Monday 17 January 2011, Ian Monroe wrote:
> So as we agreed last month, we are moving kdelibs and kdebase to git
> after 4.6.0 tagging. Is that still happening this week?
> 
> Anyways, when that happens we'll need to have a "KDE Project Manager"
> (or better: multiple) for projects.kde.org. This person has the power
> to delete branches, but probably more relevant then that, can set
> which branches should be actively translated.
> 
> The repos I'm creating are: kdebase-apps, kdebase-runtime,
> kdebase-workspace, and konsole.
> 
> Logically I think a combination of the (entire?) release team and i18n
> admins should have this position, and then also Knight for Konsole.
> Currently the function performed by the KDE Project Manager is done by
> the i18n people, but Redmine could give us more flexibility I guess.

You could add me as project manager for kdelibs and kde-baseapps, I guess.

--

-- 
David Faure, faure@..., http://www.davidfaure.fr
Sponsored by Nokia to work on KDE, incl. Konqueror (http://www.konqueror.org).
Ian Monroe | 12 Feb 15:20 2011
Picon

Re: who should I list as kde project manager

On Sat, Feb 12, 2011 at 04:21, David Faure <faure@...> wrote:
> On Monday 17 January 2011, Ian Monroe wrote:
>> So as we agreed last month, we are moving kdelibs and kdebase to git
>> after 4.6.0 tagging. Is that still happening this week?
>>
>> Anyways, when that happens we'll need to have a "KDE Project Manager"
>> (or better: multiple) for projects.kde.org. This person has the power
>> to delete branches, but probably more relevant then that, can set
>> which branches should be actively translated.
>>
>> The repos I'm creating are: kdebase-apps, kdebase-runtime,
>> kdebase-workspace, and konsole.
>>
>> Logically I think a combination of the (entire?) release team and i18n
>> admins should have this position, and then also Knight for Konsole.
>> Currently the function performed by the KDE Project Manager is done by
>> the i18n people, but Redmine could give us more flexibility I guess.
>
> You could add me as project manager for kdelibs and kde-baseapps, I guess.

Done. Feel free to add more.

Ian

Gmane