2:36 a.m.
Hi all,
every once in a while, people still report bugs on the old bug tracker
on launchpad.net. Currently, the bug tracker was left open so that we
can still read old bugs and move them over to GitLab. With some help
from Launchpad.net support
<https://answers.launchpad.net/launchpad/+question/695519> I figured out
that we can disable bug submission there without losing access to the
old bugs:
https://launchpad.net/inkscape/+configure-bugtracker
-> Setting: Bugs are tracked: "somewhere else".
I tried that temporarily for a few seconds, and it seems to work:
Then, the main links "Bugs" and "Report a bug" on Launchpad disappear.
However, one can still search for bugs using the direct link to the
"advanced search":
https://bugs.launchpad.net/~inkscape.bugs/+bugs?advanced=1
Links to old bugs still work, e.g.:
https://bugs.launchpad.net/inkscape/+bug/682585
Maybe in the future we could import the old bugs to a separate GitLab
project, so that one can find all bugs (inbox, real bugs, old launchpad
bugs) using the single URL https://gitlab.com/groups/inkscape/-/issues .
And/or mass-close the largest part of the old bugs, at least those that
are not confirmed/triaged and have not been updated for many years.
Looking forward to hear your thoughts.
Best regards and have a nice weekend
Max
5:58 a.m.
Thanks Max,
We coincidentally had an infrastructure meeting today to talk about
this kind of problem. But it looks like you have it solved.
Are there any further actions needed?
Best Regards, Martin Owens
On Sat, 2021-02-20 at 18:36 +0100, Maximilian Gaukler wrote:
Hi all,
every once in a while, people still report bugs on the old bug
tracker
on launchpad.net. Currently, the bug tracker was left open so that
we
can still read old bugs and move them over to GitLab. With some help
from Launchpad.net support
<https://answers.launchpad.net/launchpad/+question/695519> I figured
out
that we can disable bug submission there without losing access to
the
old bugs:
https://launchpad.net/inkscape/+configure-bugtracker
-> Setting: Bugs are tracked: "somewhere else".
I tried that temporarily for a few seconds, and it seems to work:
Then, the main links "Bugs" and "Report a bug" on Launchpad
disappear.
However, one can still search for bugs using the direct link to the
"advanced search":
https://bugs.launchpad.net/~inkscape.bugs/+bugs?advanced=1
Links to old bugs still work, e.g.:
https://bugs.launchpad.net/inkscape/+bug/682585
Maybe in the future we could import the old bugs to a separate
GitLab
project, so that one can find all bugs (inbox, real bugs, old
launchpad
bugs) using the single URL
https://gitlab.com/groups/inkscape/-/issues .
And/or mass-close the largest part of the old bugs, at least those
that
are not confirmed/triaged and have not been updated for many years.
Looking forward to hear your thoughts.
Best regards and have a nice weekend
Max
_______________________________________________
Inkscape Devel mailing list -- inkscape-devel(a)lists.inkscape.org
To unsubscribe send an email to
inkscape-devel-leave(a)lists.inkscape.org
6:53 p.m.
Hi Martin,
Are there any further actions needed?
If nobody disagrees, I will do the following (probably next weekend):
1. set Launchpad to "Bugs are tracked: somewhere else".
2. check for broken Launchpad URLs on
https://inkscape.org/develop/bug-management/
https://gitlab.com/inkscape/inbox/-/blob/master/Guidelines.md
https://alpha.inkscape.org/bug-migration/
and fix where required.
Best Regards,
Max
>
> Best Regards, Martin Owens
>
> On Sat, 2021-02-20 at 18:36 +0100, Maximilian Gaukler wrote:
>> Hi all,
>>
>> every once in a while, people still report bugs on the old bug
>> tracker
>> on launchpad.net. Currently, the bug tracker was left open so that
>> we
>> can still read old bugs and move them over to GitLab. With some help
>> from Launchpad.net support
>> <https://answers.launchpad.net/launchpad/+question/695519> I figured
>> out
>> that we can disable bug submission there without losing access to
>> the
>> old bugs:
>>
>> https://launchpad.net/inkscape/+configure-bugtracker
>> -> Setting: Bugs are tracked: "somewhere else".
>>
>> I tried that temporarily for a few seconds, and it seems to work:
>>
>> Then, the main links "Bugs" and "Report a bug" on Launchpad
>> disappear.
>> However, one can still search for bugs using the direct link to the
>> "advanced search":
>> https://bugs.launchpad.net/~inkscape.bugs/+bugs?advanced=1
>> Links to old bugs still work, e.g.:
>> https://bugs.launchpad.net/inkscape/+bug/682585
>>
11:17 p.m.
Hi Max,
That sounds good to me. I think it's time to flip that switch.
Does anyone else have any urls that should be looked into? Anything on
wiki.inkscape.org?
Best Regards, Martin Owens
On Sun, 2021-02-21 at 10:53 +0100, Maximilian Gaukler wrote:
Hi Martin,
> Are there any further actions needed?
If nobody disagrees, I will do the following (probably next weekend):
1. set Launchpad to "Bugs are tracked: somewhere else".
2. check for broken Launchpad URLs on
https://inkscape.org/develop/bug-management/
https://gitlab.com/inkscape/inbox/-/blob/master/Guidelines.md
https://alpha.inkscape.org/bug-migration/
and fix where required.
Best Regards,
Max
> Best Regards, Martin Owens
>
> On Sat, 2021-02-20 at 18:36 +0100, Maximilian Gaukler wrote:
> > Hi all,
> >
> > every once in a while, people still report bugs on the old bug
> > tracker
> > on launchpad.net. Currently, the bug tracker was left open so
> > that
> > we
> > can still read old bugs and move them over to GitLab. With some
> > help
> > from Launchpad.net support
> > <https://answers.launchpad.net/launchpad/+question/695519> I
> > figured
> > out
> > that we can disable bug submission there without losing access to
> > the
> > old bugs:
> >
> > https://launchpad.net/inkscape/+configure-bugtracker
> > -> Setting: Bugs are tracked: "somewhere else".
> >
> > I tried that temporarily for a few seconds, and it seems to work:
> >
> > Then, the main links "Bugs" and "Report a bug" on
Launchpad
> > disappear.
> > However, one can still search for bugs using the direct link to
> > the
> > "advanced search":
> > https://bugs.launchpad.net/~inkscape.bugs/+bugs?advanced=1
> > Links to old bugs still work, e.g.:
> > https://bugs.launchpad.net/inkscape/+bug/682585
> >
11:20 p.m.
Hi Max,
this is great! The only reason we never considered setting "Bugs are
tracked: somewhere else" was that everybody assumed they would become
inaccessible by that.
Before we go on (it's usually better to wait for people from the actual
bug team to answer, e.g. Nathan or Jonathan; Martin has a tendency of
being overhasty and taking action prematurely 🙄):
* You referenced
https://bugs.launchpad.net/~inkscape.bugs/+bugs?advanced=1
This does not seem to be the proper link however. These are the bugs
(a single bug really) of the bug team are they not?
* The likely proper URL
https://bugs.launchpad.net/inkscape/+bugs?advanced=1 is invalidated
by flipping the preference (just tested)
Am I missing something?
Cheers
Patrick
Am 21.02.2021 um 10:53 schrieb Maximilian Gaukler:
Hi Martin,
> Are there any further actions needed?
If nobody disagrees, I will do the following (probably next weekend):
1. set Launchpad to "Bugs are tracked: somewhere else".
2. check for broken Launchpad URLs on
https://inkscape.org/develop/bug-management/
https://gitlab.com/inkscape/inbox/-/blob/master/Guidelines.md
https://alpha.inkscape.org/bug-migration/
and fix where required.
Best Regards,
Max
>
> Best Regards, Martin Owens
>
> On Sat, 2021-02-20 at 18:36 +0100, Maximilian Gaukler wrote:
>> Hi all,
>>
>> every once in a while, people still report bugs on the old bug
>> tracker
>> on launchpad.net. Currently, the bug tracker was left open so that
>> we
>> can still read old bugs and move them over to GitLab. With some help
>> from Launchpad.net support
>> <https://answers.launchpad.net/launchpad/+question/695519> I figured
>> out
>> that we can disable bug submission there without losing access to
>> the
>> old bugs:
>>
>> https://launchpad.net/inkscape/+configure-bugtracker
>> -> Setting: Bugs are tracked: "somewhere else".
>>
>> I tried that temporarily for a few seconds, and it seems to work:
>>
>> Then, the main links "Bugs" and "Report a bug" on Launchpad
>> disappear.
>> However, one can still search for bugs using the direct link to the
>> "advanced search":
>> https://bugs.launchpad.net/~inkscape.bugs/+bugs?advanced=1
>> Links to old bugs still work, e.g.:
>> https://bugs.launchpad.net/inkscape/+bug/682585
>>
_______________________________________________
Inkscape Devel mailing list -- inkscape-devel(a)lists.inkscape.org
To unsubscribe send an email to inkscape-devel-leave(a)lists.inkscape.org
11:49 p.m.
Hi Patrick,
* The likely proper URL
https://bugs.launchpad.net/inkscape/+bugs?advanced=1 is invalidated
by flipping the preference (just tested)
yes, unfortunately you are right, but at the same time you helped me
find a work-around:
- Create a team "Old inkscape bugs"
- Subscribe that team to all bugs via some script (Note this will
generate one email to the team per bug!)
- Use the "bug team" link like this (example with 5 subscribed bugs)
https://bugs.launchpad.net/~testytesty
I also subscribed my test team to two of your bugs. You should hopefully
*not* have received an email about that.
Best
Max
12:47 a.m.
OK, too bad...
I've not received any mails yet (Launchpad is a bit delayed at times,
though). However I don't think I've ever received any mails for people
subscribing to my bugs.
The idea you have seems sound, if
* we get put together the script to do this and don't run into
Launchpad API issues like rate-limiting and the like (I've heard of
those in the past but have no first-hand knowledge)
* we think the few bugs filed improperly are worth the effort to go
through with this. (For me personally the answer is "no"; I'd just
keep the old tracker as-is until we either complete the migration or
decide to declare it as completed at which point we can flick the
switch without further thought).
Cheers,
Patrick
Am 21.02.2021 um 15:49 schrieb Maximilian Gaukler:
Hi Patrick,
> * The likely proper URL
> https://bugs.launchpad.net/inkscape/+bugs?advanced=1 is invalidated
> by flipping the preference (just tested)
yes, unfortunately you are right, but at the same time you helped me
find a work-around:
- Create a team "Old inkscape bugs"
- Subscribe that team to all bugs via some script (Note this will
generate one email to the team per bug!)
- Use the "bug team" link like this (example with 5 subscribed bugs)
https://bugs.launchpad.net/~testytesty
I also subscribed my test team to two of your bugs. You should
hopefully *not* have received an email about that.
Best
Max
_______________________________________________
Inkscape Devel mailing list -- inkscape-devel(a)lists.inkscape.org
To unsubscribe send an email to inkscape-devel-leave(a)lists.inkscape.org
3:42 a.m.
I don't think the testing team is going to see these emails here.
A notice should be supplied to #team_testing on chat.inkscape.org for a
proper feedback.
Best Regards, Martin Owens
On Sun, 2021-02-21 at 16:47 +0100, Patrick Storz wrote:
OK, too bad...
I've not received any mails yet (Launchpad is a bit delayed at times,
though). However I don't think I've ever received any mails for
people subscribing to my bugs.
The idea you have seems sound, if
we get put together the script to do this and don't run into
Launchpad API issues like rate-limiting and the like (I've heard of
those in the past but have no first-hand knowledge)
we think the few bugs filed improperly are worth the effort to go
through with this. (For me personally the answer is "no"; I'd just
keep the old tracker as-is until we either complete the migration or
decide to declare it as completed at which point we can flick the
switch without further thought).
Cheers,
Patrick
Am 21.02.2021 um 15:49 schrieb Maximilian Gaukler:
> Hi Patrick,
>
> > * The likely proper URL
> > https://bugs.launchpad.net/inkscape/+bugs?advanced=1 is
> invalidated
> > by flipping the preference (just tested)
>
> yes, unfortunately you are right, but at the same time you helped
> me find a work-around:
>
> - Create a team "Old inkscape bugs"
> - Subscribe that team to all bugs via some script (Note this will
> generate one email to the team per bug!)
> - Use the "bug team" link like this (example with 5 subscribed
> bugs) https://bugs.launchpad.net/~testytesty
>
> I also subscribed my test team to two of your bugs. You should
> hopefully *not* have received an email about that.
>
> Best
>
> Max
> _______________________________________________
> Inkscape Devel mailing list -- inkscape-devel(a)lists.inkscape.org
> To unsubscribe send an email to
> inkscape-devel-leave(a)lists.inkscape.org
_______________________________________________
Inkscape Devel mailing list -- inkscape-devel(a)lists.inkscape.org
To unsubscribe send an email to
inkscape-devel-leave(a)lists.inkscape.org
4 a.m.
More likely https://chat.inkscape.org/channel/bug_migration ? I'll drop
a note...
It's a bit representative for the complicated situation we put ourselves in:
* Mailing lists (in theory) still being the official way to announce
important changes across the project but being used less and less
* Rocket chat with more and more teams/channels spawning but no
consistent way to know about all of them (I didn't even know
#team_testing existed).
On the upside I just saw someone finally cleared out the directory
(https://chat.inkscape.org/directory/channels) - seems three times the
charm (that's how often I bugged everybody about this). ;-)
I still wonder whether we should not try to encourage people to continue
using the mailing lists more. Information in chat is volatile. On the
other hand people also don't seem to be interested on reading up past
discussions in many cases, so maybe that's just the doom of "modern"
communication we have to face.
Cheers
Patrick
Am 21.02.2021 um 19:42 schrieb doctormo(a)gmail.com:
I don't think the testing team is going to see these emails
here.
A notice should be supplied to #team_testing on chat.inkscape.org for a
proper feedback.
Best Regards, Martin Owens
On Sun, 2021-02-21 at 16:47 +0100, Patrick Storz wrote:
> OK, too bad...
>
> I've not received any mails yet (Launchpad is a bit delayed at times,
> though). However I don't think I've ever received any mails for
> people subscribing to my bugs.
>
> The idea you have seems sound, if
>
> we get put together the script to do this and don't run into
> Launchpad API issues like rate-limiting and the like (I've heard of
> those in the past but have no first-hand knowledge)
> we think the few bugs filed improperly are worth the effort to go
> through with this. (For me personally the answer is "no"; I'd just
> keep the old tracker as-is until we either complete the migration or
> decide to declare it as completed at which point we can flick the
> switch without further thought).
> Cheers,
> Patrick
>
>
>
> Am 21.02.2021 um 15:49 schrieb Maximilian Gaukler:
>> Hi Patrick,
>>
>>> * The likely proper URL
>>> https://bugs.launchpad.net/inkscape/+bugs?advanced=1 is
>> invalidated
>>> by flipping the preference (just tested)
>> yes, unfortunately you are right, but at the same time you helped
>> me find a work-around:
>>
>> - Create a team "Old inkscape bugs"
>> - Subscribe that team to all bugs via some script (Note this will
>> generate one email to the team per bug!)
>> - Use the "bug team" link like this (example with 5 subscribed
>> bugs) https://bugs.launchpad.net/~testytesty
>>
>> I also subscribed my test team to two of your bugs. You should
>> hopefully *not* have received an email about that.
>>
>> Best
>>
>> Max
>> _______________________________________________
>> Inkscape Devel mailing list -- inkscape-devel(a)lists.inkscape.org
>> To unsubscribe send an email to
>> inkscape-devel-leave(a)lists.inkscape.org
> _______________________________________________
> Inkscape Devel mailing list -- inkscape-devel(a)lists.inkscape.org
> To unsubscribe send an email to
> inkscape-devel-leave(a)lists.inkscape.org
_______________________________________________
Inkscape Devel mailing list -- inkscape-devel(a)lists.inkscape.org
To unsubscribe send an email to inkscape-devel-leave(a)lists.inkscape.org
832
days inactive
833
days old
inkscape-devel@lists.inkscape.org
8 comments
3 participants
participants (3)
-
doctormo＠gmail.com -
Maximilian Gaukler -
Patrick Storz