[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-promo
Subject:    Re: [kde-promo] Learning lessons from release problems
From:       Anne Wilson <annew () kde ! org>
Date:       2010-02-19 11:05:23
Message-ID: 201002191105.30022.annew () kde ! org
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Thursday 18 February 2010 21:36:18 Ingo Klöcker wrote:
> On Friday 12 February 2010, Anne Wilson wrote:
> > RC3 was, for me, so smooth that I didn't really expect to see any
> > major problems with 4.4.  However, the forum and lists are full of
> > people that are having problems.  Mostly they are caused by what I
> > understand to be a change in the Nepomuk database structure.
> > Apparently some people picked up from somewhere the hint that any
> > existing nepomuk database should be deleted, prior to updating, but
> > despite the amount of reading I do, I didn't see that.
> > 
> > I'm sure we'll gradually get people sorted and up and running again,
> > but I'd like to try to avoid such a problem in the future.  The
> > question is, how can we ensure that such important crumbs of
> > information are spread around, preferably a few days before release?
> 
> The problem here really was the timing. The new version of Virtuoso was
> released just a few days before KDE SC 4.4.0 (and after the last RC).
> This didn't leave enough time for the packagers or us to ease the
> upgrade path. There is no way to avoid such a problem from happening
> again in the future except for forbidding dependencies on external stuff
> that is ready "just in time for the release" (but not a second earlier).
> 
Yes, that seems to have been the problem.  Is there no way that, in these 
circumstances, we can spread a strong warning on the lines of 'WARNING - due 
to a change in the way the database is structured, any user who had the old 
virtuoso will need to delete his database and rebuild'?  Clearly something was 
said, somewhere, as I've seen mention of people knowing and deleting the 
database before starting the update, but it doesn't seem to have spread too 
well.

I can see that not including the new virtuoso would have been a serious 
setback, and, as you say, we are bound to meet a similar situation again, so 
it's really a matter of thinking now, before it does happen again, of such an 
emergency strategy.

Anne
-- 
KDE Community Working Group
New to KDE Software? - get help from http://userbase.kde.org

["signature.asc" (application/pgp-signature)]

_______________________________________________
This message is from the kde-promo mailing list.

Visit https://mail.kde.org/mailman/listinfo/kde-promo to unsubscribe, set digest on \
or temporarily stop your subscription.



[prev in list] [next in list] [prev in thread] [next in thread]