kde3 to 4 bugs transition policy?
Yuriy Kozlov
yuriy.kozlov at gmail.com
Tue Jan 15 16:19:36 GMT 2008
On Jan 15, 2008 2:07 AM, Sarah Hobbs <hobbsee at ubuntu.com> wrote:
> -----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.
>
My concern is that upstream will consider the wishlist bugs fixed if
they are fixed in KDE4, so rejecting them in lp and refiling on b.k.o
is effectively the same thing I was suggesting, but creates more work
for both us and upstream compared to us seeing that they are fixed in
KDE4 and just closing them.
Bugs that are not fixed in KDE 4.0 of course should be filed upstream
where applicable.
> 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.
>
Already 100 bugs searching for kde4 [1]
Sounds good for a hug day.
~ Yuriy
[1] https://bugs.launchpad.net/ubuntu/+bugs?field.searchtext=kde4&orderby=-importance&search=Search&field.status%3Alist=NEW&field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.status%3Alist=FIXCOMMITTED&field.assignee=&field.bug_reporter=&field.omit_dupes=on&field.has_patch=&field.has_no_package=
More information about the kubuntu-devel
mailing list