<br><br><div class="gmail_quote">On Wed, Jun 22, 2011 at 7:23 AM, Raphael Kubo da Costa <span dir="ltr"><<a href="mailto:kubito@gmail.com">kubito@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">Dirk Mueller <<a href="mailto:mueller@kde.org">mueller@kde.org</a>> writes:<br>
<br>
> On Friday 17 June 2011, Nicolas Alvarez wrote:<br>
><br>
</div><div class="im">>> kdeutils is supposed to release with split tarballs (of course, the build<br>
>> system in 4.6 has been tweaked to also work as a monolithic tarball for the<br>
>> 4.6.5 release).<br>
><br>
> Lets hope so. Are the branch names in those git modules at least<br>
> consistent?<br>
<br>
</div>Yes. All SVN branches follow the 'x.y' naming scheme (with no KDE/). The<br>
ruleset file for this is in [1]. Future branches should follow the same<br>
convention.<br>
<br>
[1] <a href="https://projects.kde.org/projects/playground/sdk/kde-ruleset/repository/revisions/master/entry/kdeutils/common-branch-rules" target="_blank">https://projects.kde.org/projects/playground/sdk/kde-ruleset/repository/revisions/master/entry/kdeutils/common-branch-rules</a><br>
<div class="im"><br>
>> I'm not sure what's the status of kdeaccessibility, I'll check now.<br>
<br>
> Regarding your main question: we have both KDE 4.7.0 and 4.6.5 imminent.<br>
><br>
> It seems the only sensible solution is to either delay the split until 4.7.0<br>
> is over (which is a pain because it means that I gotta collect the leaves for<br>
> 4.7.1, which is supposed to be a minor release), or we need to do it before<br>
> 4.7.0, essentially before RC1, which is however supposed to be done today.<br>
><br>
> I see no easy solution. what is your timeline for the conversions?<br>
<br>
</div>On the kdeutils side, the migration rules have been ready for a few<br>
months. However, I'll have some time to properly handle this migration<br>
only next month. We are not in a hurry to move, so at least kdeutils can<br>
have its migration delayed until it is OK for you and the rest of the<br>
release team.<br></blockquote><div><br>Same for kde-accessibility. There is general concensus among the active kde-accessibility developers that we want split repos, though Gunnar (the release coordinator) hasn't given any input at all... Anyway, we are ok to move at any convenient time. Though personally I'd prefer a time when I could have some time (maybe a week) to test the resulting repositories and building split/together so as to not recreate the kdeedu issues we had earlier.<br>
<br>thanks,<br>Jeremy <br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><div></div><div class="h5">_______________________________________________<br>
release-team mailing list<br>
<a href="mailto:release-team@kde.org">release-team@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>