Re: bic and sic change in soprano
On 2012-05-29, Aaron J. Seigo ase...@kde.org wrote: as Trueg is perhaps MIA for a few more days and i'd like to see this move forward sooner rather than later, has anyone figured out what commits removed this class(es?) ... mainly 3d66d429cb48781881af3e735f2a80af2114ab25, but 5dde64227186d405f86bf66256705fbceabcf1e2 also has some related bits. /Sune ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: nepomuk-core needs unreleased Soprano
The new beta1 release is uploaded to SF now. I will add announcements tonight. Sorry for the delay. I was moving house and had no internet connection. On 05/26/2012 04:57 PM, Albert Astals Cid wrote: Hi, I've just learnt that nepomuk-core needs an unreleased Soprano, so until Sebastian does a new release you'll have to use the git version of soprano. Sorry for just learning this. Albert ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: nepomuk-core needs unreleased Soprano
On Wednesday, May 30, 2012 09:15:03 Sebastian Trüg wrote: The new beta1 release is uploaded to SF now. I will add announcements tonight. i assume these will be source and binary incompatible with previous releases due to the removal of tcpclient.h from the build. i have put in a stub version of tcpclient.cpp that does nothing other than tell the developer not to use it ;) it now builds and should be SC and BC. i pushed this to both master and the 2.8 branch. this means we'll need a re-do of the tarballs .. but that's not a big deal. so current status is: * SC/BC should be restored (though not tested with an automated checker; just took care of the tcpclient issue) * we have a branch (2.8) which releases can be pulled from ... we should be good to go? Sorry for the delay. I was moving house and had no internet connection. yes, this sucks .. what makes me nervous, and should make us all nervous, is this implies that soprano has a bus number of 1. that is not tolerable for a component that so many things in our code relies on. may i suggest that Vishesh be promoted to co-maintainer so that he may also take on tasks such as these if you become unavailable? it's still a relatively low bus number of 2, but that's a lot better than 1. -- Aaron J. Seigo signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
[HEADS-UP] libkgoogle renaming to libKGAPI
Howdy, Just read on kde-core-devel that Dan will be renaming his libkgoogle library to libKGAPI The code for this library will be available in KDE's Git repo. The repo is already there as libkgoogle but I don't know if Dan will also change the name of the repo. The rename will affect kdepim-runtime 4.9 so I assume you'll need to package a libKGAPI if you want your users to have access to Google resources from kdepim applications. More details as they become available. -Allen ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: nepomuk-core needs unreleased Soprano
On Wednesday 30 May 2012, Sebastian Trüg wrote: what is a bus number? The number of developers who need to be hit by a bus for the project to be destroyed. 1 means there's a single point of failure (you), i.e., whenever you aren't available for whatever reason (such as the past few days), everything grinds to a halt. Kevin Kofler ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Calling off Beta1
Hello all, On Tue, May 29, 2012 at 1:35 PM, Scott Kitterman k...@kitterman.com wrote: Why cancel instead of just telling people the need to update to soprano from git? Scott K I think that most of the discussion here is based off of a miscommunication caused by the title of this thread. The original post by Albert does state that the current *tarballs* for beta1 have been cancelled, while the title suggests that the whole of beta1 has been called off. This uncertainty, I think, has lead to confusion as to whether any tarballs at all will be made for beta1, and I think most of the posts (as well as the resulting tensions) have been based off the premise that beta1 isn't happening at all. If I am understanding the original post correctly, the release is still planned. (But perhaps delayed?) On the other hand, I could be totally wrong, and the cancelled tarballs could mean a cancelled beta1 release entirely.Some things could have perhaps been communicated better, and things were definitely exacerbated by Trueg's MIA-ness over the weekend. I think that there are still some pieces of information that still need to be known before the situation can be considered cleared up: - Given that only the tarballs for beta1 have been cancelled, will the release proceed with new tarballs now that we have a soprano release, or will beta1 not have a release in tarball form? - If so, when is the new release timeframe for beta1? (I'm assuming that if new tarballs are spun, the timeframe has changed, since the tarballs are not currently available via ftpmaster) I also have a few remarks as to how the situation with soprano was handled in general. There were bound to be bumps along the way with this transition, so please don't take these as accusations of blame against any person or group of people, but more as things to take in to consideration for the future. (Remember, hindsight vision is always 20/20, etc, and there were external events complicating things...) Given the nature of the reason for cancelling the tarballs, I don't think a complete removal from ftpmaster/respin is quite the proper response for a missing dependency. I can definitely see the rationale for a delay of the release, but once the issue is resolved, the KDE tarballs will only be respun from the same tag and will be effectively identical. Technically, the tarballs are embargoed until release already, or at least embargoed until a day or so before release to give distros a chance to have binaries more or less built at the official release time. I seem to remember Kubuntu catching some flak for this early on in the KDE4 days for publishing tarballs before they were ready, so I have a bit of personal experience to this bit. ;-) The tarballs are still useful to packagers in a practical sense even in the case of a release delay, especially since any respins will be based off the same tag. Packaging work is cumulative, so work could still be done with the old tarballs. I think that in the future instead of the release team removing the tarballs from ftpmaster, a note send out to the various m-l's saying the release has been delayed, so please remember to respect the existing embargo on the tarballs would be a bit more appropriate than the outright removal of the tarballs from ftpmaster. Regards, Jonathan ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Beta 1: New Plans
Ok, so these are the new plans a) reupload old tarballs ASAP (working on that, expect them on the usual location by the end of the day) b) repackage all the tarballs with contents from master (KDE/4.8 for kdelibs) tomorrow afternoon. This will include patches the patches you had to apply manually before so that there were no duplicate installed files, etc c) upload these new tarballs tomorrow d) Make the release on Monday This plan has been agreed with Sebas and Allen. If you have serious objections please make them ASAP. Albert P.S: Please note I probably will be disconnected from the interwebs from Thursday night to Sunday evening ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: Beta 1: New Plans
On 05/30/2012 06:28 PM, Albert Astals Cid wrote: Ok, so these are the new plans a) reupload old tarballs ASAP (working on that, expect them on the usual location by the end of the day) b) repackage all the tarballs with contents from master (KDE/4.8 for kdelibs) tomorrow afternoon. This will include patches the patches you had to apply manually before so that there were no duplicate installed files, etc c) upload these new tarballs tomorrow d) Make the release on Monday This plan has been agreed with Sebas and Allen. If you have serious objections please make them ASAP. Albert P.S: Please note I probably will be disconnected from the interwebs from Thursday night to Sunday evening OK with me, thanks for all this Albert. Anne-Marie ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Soprano tarball
BTW you guys can find the soprano tarball at http://sourceforge.net/projects/soprano/files/Soprano/2.7.56/ Albert ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
