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

List:       kde-pim
Subject:    [Kde-pim] Re: Data driven mail migration
From:       Ingo =?iso-8859-15?q?Kl=F6cker?= <kloecker () kde ! org>
Date:       2011-03-02 21:00:57
Message-ID: 201103022200.58121 () thufir ! ingo-kloecker ! de
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Wednesday 02 March 2011, Anne Wilson wrote:
> On Wednesday 02 March 2011 16:45:00 Guy Maurel wrote:
> > Hello!
> > 
> > On Wednesday, March 02, 2011 09:14:55 AM Till Adam wrote:
> > > I'd be interested in the top 5 bugs that keep you from doing
> > > work. I'm sure those are addressable.
> > 
> > Could it be possible to make a definition list of
> > - what ...
> > - where ...
> > - which
> > files and directories are necessary and only those
> > to make such a migration test.
> > What is usefull to write down at migration time/after migration?
> > - number of (which) processes
> > - which new files and directories
> > 
> > With such a set of rules, some/many helpers could point to problems
> > and / or show the problems are solved, in a common way.
> > 
> > have a nice day
> 
> I was thinking exactly the same today.  Ideally I'd like to see it on
> UserBase so that the forums can easily point people to it.  If it
> helps, I could take a text document, or other format, and do the
> wiki markup.

I don't think it makes much sense to document a migration test (!) on 
UserBase. If we want to document it then, IMO, Community Wiki is more 
appropriate. Or a blog entry. In fact, many moons ago, Kevin did exactly 
this:
  http://www.kdedevelopers.org/node/4242


Regards,
Ingo

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

_______________________________________________
KDE PIM mailing list kde-pim@kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/

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