FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Ubuntu > Kubuntu Development

 
 
LinkBack Thread Tools
 
Old 01-13-2008, 05:15 PM
"Yuriy Kozlov"
 
Default kde3 to 4 bugs transition policy?

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.sourcepacka gename=kdebase&field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=NEW&f ield.status%3Alist=INCOMPLETE_WITH_RESPONSE&field. status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.st atus%3Alist=CONFIRMED&field.status%3Alist=TRIAGED& field.status%3Alist=INPROGRESS&field.importance%3A list=LOW&field.importance%3Alist=WISHLIST&assignee _option=any&field.assignee=&field.bug_reporter=&fi eld.bug_contact=&field.bug_commenter=&field.subscr iber=&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=o n&field.has_patch.used=&field.tag=&field.has_cve.u sed=

--
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
 
Old 01-13-2008, 06:25 PM
Stephan Hermann
 
Default kde3 to 4 bugs transition policy?

Hi Yuriy,

On So, 2008-01-13 at 13:15 -0500, 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.

Who should not focus on KDE 3? We still have dapper with kde3 and this
is still supported until 10.2009, feisty, gutsy and hardy will have
support for 18 months, and kde3 is still in hardy. so there is no need
to migrate bugs or whatever. All KDE3 bugs are still valid and can be
resolved by a patch, a workaround or whatever.

So from a developers PoV there is a nogo for that...
kde4 packages are completly new and should be handled as different
packages. Bugs in kde4 packages are not likely in kde3 packages and vice
versa...

Regards,

sh
--
´╗┐SysAdmin, OSS Developer
GPG-Key ID: 0xC098EFA8
Fingerprint: 3D8B 5138 0852 DA7A B83F DCCB C189 E733 C098 EFA8
http://www.sourcecode.de/


--
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
 
Old 01-13-2008, 06:42 PM
Scott Kitterman
 
Default kde3 to 4 bugs transition policy?

On Sunday 13 January 2008 14:25, Stephan Hermann wrote:
> Hi Yuriy,
>
> On So, 2008-01-13 at 13:15 -0500, 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.
>
> Who should not focus on KDE 3? We still have dapper with kde3 and this
> is still supported until 10.2009, feisty, gutsy and hardy will have
> support for 18 months, and kde3 is still in hardy. so there is no need
> to migrate bugs or whatever. All KDE3 bugs are still valid and can be
> resolved by a patch, a workaround or whatever.
>
> So from a developers PoV there is a nogo for that...
> kde4 packages are completly new and should be handled as different
> packages. Bugs in kde4 packages are not likely in kde3 packages and vice
> versa...
>
Agreed.

I would suggest that marking KDE3 bugs "Fix Released" against KDE4 packages is
appropriate once KDE4 is complete and mature enough that it's the default KDE
for Kubuntu.

Scott K

--
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
 
Old 01-13-2008, 08:46 PM
Stephan Hermann
 
Default kde3 to 4 bugs transition policy?

Hi,

On So, 2008-01-13 at 14:42 -0500, Scott Kitterman wrote:
> On Sunday 13 January 2008 14:25, Stephan Hermann wrote:
> > Hi Yuriy,
> >
> > On So, 2008-01-13 at 13:15 -0500, 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.
> >
> > Who should not focus on KDE 3? We still have dapper with kde3 and this
> > is still supported until 10.2009, feisty, gutsy and hardy will have
> > support for 18 months, and kde3 is still in hardy. so there is no need
> > to migrate bugs or whatever. All KDE3 bugs are still valid and can be
> > resolved by a patch, a workaround or whatever.
> >
> > So from a developers PoV there is a nogo for that...
> > kde4 packages are completly new and should be handled as different
> > packages. Bugs in kde4 packages are not likely in kde3 packages and vice
> > versa...
> >
> Agreed.
>
> I would suggest that marking KDE3 bugs "Fix Released" against KDE4 packages is
> appropriate once KDE4 is complete and mature enough that it's the default KDE
> for Kubuntu.

Well, I would say, that regarding the state of kde 4.0.0 this will be a
long way...and we need to support kde 3 from dapper at least until
2009...so we have time to fix all bugs ,-)

Regards and have a good night,

sh
--
´╗┐SysAdmin, OSS Developer
GPG-Key ID: 0xC098EFA8
Fingerprint: 3D8B 5138 0852 DA7A B83F DCCB C189 E733 C098 EFA8
http://www.sourcecode.de/


--
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
 
Old 01-15-2008, 06:07 AM
Sarah Hobbs
 
Default kde3 to 4 bugs transition policy?

-----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.sourcepacka gename=kdebase&field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=NEW&f ield.status%3Alist=INCOMPLETE_WITH_RESPONSE&field. status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.st atus%3Alist=CONFIRMED&field.status%3Alist=TRIAGED& field.status%3Alist=INPROGRESS&field.importance%3A list=LOW&field.importance%3Alist=WISHLIST&assignee _option=any&field.assignee=&field.bug_reporter=&fi eld.bug_contact=&field.bug_commenter=&field.subscr iber=&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=o n&field.has_patch.used=&field.tag=&field.has_cve.u sed=
>

-----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-----

--
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
 
Old 01-15-2008, 03:19 PM
"Yuriy Kozlov"
 
Default kde3 to 4 bugs transition policy?

On Jan 15, 2008 2:07 AM, Sarah Hobbs <hobbsee@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&f ield.status%3Alist=INCOMPLETE_WITH_RESPONSE&field. status%3Alist=CONFIRMED&field.status%3Alist=TRIAGE D&field.status%3Alist=INPROGRESS&field.status%3Ali st=FIXCOMMITTED&field.assignee=&field.bug_reporter =&field.omit_dupes=on&field.has_patch=&field.has_n o_package=

--
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
 
Old 01-15-2008, 03:24 PM
"Yuriy Kozlov"
 
Default kde3 to 4 bugs transition policy?

On Jan 13, 2008 2:25 PM, Stephan Hermann <sh@sourcecode.de> wrote:
> Hi Yuriy,

> Who should not focus on KDE 3? We still have dapper with kde3 and this
> is still supported until 10.2009, feisty, gutsy and hardy will have
> support for 18 months, and kde3 is still in hardy. so there is no need
> to migrate bugs or whatever. All KDE3 bugs are still valid and can be
> resolved by a patch, a workaround or whatever.

Not shouldn't, but I was just observing that people aren't (which may
not be an accurate observation).
"Support" for dapper, feisty, and gutsy is for security updates and
"high impact" bugs. So low importance and wishlist bugs by policy
cannot be fixed in those releases. That leaves hardy.
~ Yuriy

--
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
 
Old 01-15-2008, 03:57 PM
Scott Kitterman
 
Default kde3 to 4 bugs transition policy?

On Tuesday 15 January 2008 11:24, Yuriy Kozlov wrote:
> On Jan 13, 2008 2:25 PM, Stephan Hermann <sh@sourcecode.de> wrote:
> > Hi Yuriy,
> >
> > Who should not focus on KDE 3? We still have dapper with kde3 and this
> > is still supported until 10.2009, feisty, gutsy and hardy will have
> > support for 18 months, and kde3 is still in hardy. so there is no need
> > to migrate bugs or whatever. All KDE3 bugs are still valid and can be
> > resolved by a patch, a workaround or whatever.
>
> Not shouldn't, but I was just observing that people aren't (which may
> not be an accurate observation).
> "Support" for dapper, feisty, and gutsy is for security updates and
> "high impact" bugs. So low importance and wishlist bugs by policy
> cannot be fixed in those releases. That leaves hardy.
> ~ Yuriy

For which KDE3 will still be the default and the version that people who use
Kubuntu for actual work will mostly use.

Scott K

--
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
 
Old 01-15-2008, 04:53 PM
"Richard A. Johnson"
 
Default kde3 to 4 bugs transition policy?

We should tag the current KDE 3.5 bugset accordingly as to show a little
separation. As for wishlist bugs, I would have to consider those are probably
invalid if it is a "new feature."

As they said on one of the KDE mailing lists, KDE 3.5 isn't going anywhere soon.

--
Richard A. Johnson
nixternal@kubuntu.org
GPG Key: 0x2E2C0124
--
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
 
Old 06-19-2008, 02:00 AM
"Yuriy Kozlov"
 
Default kde3 to 4 bugs transition policy?

On Sun, Jan 13, 2008 at 2:15 PM, Yuriy Kozlov <yuriy-kozlov@kubuntu.org> 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.sourcepacka gename=kdebase&field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=NEW&f ield.status%3Alist=INCOMPLETE_WITH_RESPONSE&field. status%3Alist=INCOMPLETE_WITHOUT_RESPONSE&field.st atus%3Alist=CONFIRMED&field.status%3Alist=TRIAGED& field.status%3Alist=INPROGRESS&field.importance%3A list=LOW&field.importance%3Alist=WISHLIST&assignee _option=any&field.assignee=&field.bug_reporter=&fi eld.bug_contact=&field.bug_commenter=&field.subscr iber=&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=o n&field.has_patch.used=&field.tag=&field.has_cve.u sed=
>

Now that we have specs for Intrepid, namely replacing KDE 3 packages
with KDE 4 versions, I'd like to revisit this. Basically, I think,
the normal policy should be followed: Either the bug qualifies for
SRU[1], or if it's fixed in the development version, that means it's
fixed since the fix is never going to get to the stable version. In
this case, if a bug is fixed in KDE 4.1, and does not qualify for a
SRU to Hardy/KDE 3.5, then it's considered fixed.

So, the triage procedure for open (including Confirmed!) bugs in KDE
(not *-kde4) packages would be the following:
1. Test on Hardy/KDE3. If it's not present, then mark it fixed or
invalid, as appropriate.
If you can confirm it on Hardy/KDE3:
a. If it qualifies for SRU according to [1], mark it Confirmed and
tag it as kubuntu-needs-sru (?). If all other needed information is
there, mark it Triaged. In most cases, the importance should be set
to High, since if it wasn't important it probably doesn't qualify for
SRU either.
b. If it doesn't, go on to step 2.
2 (optional). Test on Hardy/KDE4 with backports. If it's not present,
then mark it fixed. If not, go on to step 3.
3. Test on Hardy with KDE 4.1 daily build OR (preferably) on Intrepid.
If it's not present mark it fixed. If it's still there, and all
needed information is there, mark it Triaged. As usual, for
application feature requests, and most non-packaging bugs, look for
and/or file the bug upstream at bugs.kde.org and add a bug watch.

For *-kde4 packages in Hardy:
1. Test on Hardy/KDE4. If it's not present, then mark it fixed or
invalid, as appropriate.
If you can confirm it on Hardy/KDE4:
a. If it qualifies for SRU according to [1], mark it Confirmed and
tag it as kubuntu-needs-sru (?). If all other needed information is
there, mark it Triaged. In most cases, the importance should be set
to High, since if it wasn't important it probably doesn't qualify for
SRU either.
b. If it doesn't, go on to step 2.
2. Test on Hardy with KDE 4.1 daily build OR (preferably) on Intrepid.
If it's not present mark it fixed. If it's still there, and all
needed information is there, mark it Triaged and change the package to
the one without the -kde4 suffix. As usual, for application feature
requests, and most non-packaging bugs, look for and/or file the bug
upstream at bugs.kde.org and add a bug watch.

[1] https://wiki.kubuntu.org/StableReleaseUpdates

Thoughts?
~ Yuriy

--
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel
 

Thread Tools




All times are GMT. The time now is 01:38 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ę2007 - 2008, www.linux-archive.org