kde3 to 4 bugs transition policy?

[Sarah Hobbs]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'd suggest that kde 3.5 bugs stay open.  No one seems to look much at
them anyway, or if they do, don't do much about them.  They can all be
closed when we don't support kde 3.5 anymore (in one go, by the
launchpad guys).

I'd also suggest re-reporting all kde 3 bugs that still apply to kde 4 -
a lot of them will have been solved in other ways, and launchpad is
really not a good place for feature requests anyway - they should be on
bugs.kde.org.  With the wishlists, it would be a good idea to file them
in b.k.o, and mark them as "Won't fix" (ie, won't fix here) and link the
upstream bugs.

I'd like to remind people to actively send bugs upstream, particularly
while we have a fairly new starting point, and rapid upstream
development.  If we get all the kde4 bugs that should be forwarded done,
then we will find it harder to fall behind on our bug tracking.

Yuriy Kozlov wrote:
> Hello, happy 4.0!
> 
> With KDE 4.0 out and many people's focus for hardy, I was wondering
> what the plan was for all the KDE 3.5 bugs in launchpad.  There are
> about 1900 of them open[1], and it's now increasingly likely that many
> will never get fixed in 3.5 or even looked at.  Many bugs are likely
> already fixed in KDE 4.0, and others will be fixed there and not in
> 3.5.
> 
> Maybe it's time to start transitioning the bugs over to the KDE 4
> packages?  Meaning close bugs if they are fixed in 4.0, and change the
> source package to the kde4 one if it's not essential and reasonable to
> fix the bug in 3.5 for hardy.
> 
> I propose to start by doing this for the wishlist and low importance
> bugs.  This is currently about 100 bugs for e.g. kdebase[2].
> Thoughts?
> 
> 
> [1] https://launchpad.net/~kubuntu-team/+packagebugs
> [2] https://launchpad.net/~kubuntu-team/+packagebugs-search?field.distribution=ubuntu&field.sourcepackagename=kdebase&field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.importance%3Alist=LOW&field.importance%3Alist=WISHLIST&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_contact=&field.bug_commenter=&field.subscriber=&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.tag=&field.has_cve.used=
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHjFvF7/o1b30rzoURAobmAJ9uStbLkW/7YgTbtjOTL4gqsOXCXgCgmbfu
nPvTe6eJ4s2fLdZTyLwNfbk=
=P6hS
-----END PGP SIGNATURE-----