[PySide] Bugzilla closed for new entries
Matti Airas
As discussed before, Qt Project's JIRA Bug Tracker should now be used
for reporting new bugs against PySide.
https://bugreports.qt-project.org/
I have now disabled opening new bugs in the old Bugzilla instance and
requested all open bugs to be re-submitted in JIRA.
Sorry for all inconvenience caused. :-)
Cheers,
ma.
_______________________________________________
PySide mailing list
PyS...@qt-project.org
http://lists.qt-project.org/mailman/listinfo/pyside
anatoly techtonik
> Hi,
>
> As discussed before, Qt Project's JIRA Bug Tracker should now be used
> for reporting new bugs against PySide.
>
> https://bugreports.qt-project.org/
>
>
> I have now disabled opening new bugs in the old Bugzilla instance and
> requested all open bugs to be re-submitted in JIRA.
>
> Sorry for all inconvenience caused. :-)
There should be a possibility to provide a link to a newly recreated issue.
I also afraid that most people will lack the incentive to recreate bugs anew.
--
anatoly t.
Hugo Parente Lima
> On Thu, Mar 8, 2012 at 6:15 PM, Matti Airas <matti....@nokia.com> wrote:
> > Hi,
> >
> > As discussed before, Qt Project's JIRA Bug Tracker should now be used
> > for reporting new bugs against PySide.
> >
> > https://bugreports.qt-project.org/
> >
> >
> > I have now disabled opening new bugs in the old Bugzilla instance and
> > requested all open bugs to be re-submitted in JIRA.
> >
> > Sorry for all inconvenience caused. :-)
>
> There should be a possibility to provide a link to a newly recreated issue.
> I also afraid that most people will lack the incentive to recreate bugs
> anew. --
+1
> anatoly t.
> _______________________________________________
> PySide mailing list
> PyS...@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
--
Hugo Parente Lima
INdT - Instituto Nokia de Tecnologia
matti....@nokia.com
> On Thu, Mar 8, 2012 at 6:15 PM, Matti Airas <matti....@nokia.com> wrote:
>> Hi,
>>
>> As discussed before, Qt Project's JIRA Bug Tracker should now be used
>> for reporting new bugs against PySide.
>>
>> https://bugreports.qt-project.org/
>>
>>
>> I have now disabled opening new bugs in the old Bugzilla instance and
>> requested all open bugs to be re-submitted in JIRA.
>>
>> Sorry for all inconvenience caused. :-)
>
> There should be a possibility to provide a link to a newly recreated issue.
Just comment on the bug in either bug tracker - it's not that hard!
> I also afraid that most people will lack the incentive to recreate bugs anew.
Thank you for volunteering to replicate all open bugs from Bugzilla to Jira! Please report back to the mailing list once you've done it!
Cheers,
ma.
anatoly techtonik
> On Mar 8, 2012, at 18:04, ext anatoly techtonik wrote:
>
>> On Thu, Mar 8, 2012 at 6:15 PM, Matti Airas <matti....@nokia.com> wrote:
>>> Hi,
>>>
>>> As discussed before, Qt Project's JIRA Bug Tracker should now be used
>>> for reporting new bugs against PySide.
>>>
>>> https://bugreports.qt-project.org/
>>>
>>>
>>> I have now disabled opening new bugs in the old Bugzilla instance and
>>> requested all open bugs to be re-submitted in JIRA.
>>>
>>> Sorry for all inconvenience caused. :-)
>>
>> There should be a possibility to provide a link to a newly recreated issue.
>
> Just comment on the bug in either bug tracker - it's not that hard!
>
>> I also afraid that most people will lack the incentive to recreate bugs anew.
>
> Thank you for volunteering to replicate all open bugs from Bugzilla to Jira! Please report back to the mailing list once you've done it!
Well, somebody needs to execute this stuff -
http://confluence.atlassian.com/display/JIRA/Importing+Data+from+Bugzilla
I'll try to contact tracker list about this.
--
anatoly t.
Matti Airas
> Well, somebody needs to execute this stuff -
> http://confluence.atlassian.com/display/JIRA/Importing+Data+from+Bugzilla
>
> I'll try to contact tracker list about this.
Neat! Thanks.
ma.
anatoly techtonik
> On 08.03.2012 19:28, ext anatoly techtonik wrote:
>>
>> Well, somebody needs to execute this stuff -
>> http://confluence.atlassian.com/display/JIRA/Importing+Data+from+Bugzilla
>>
>> I'll try to contact tracker list about this.
>
>
> Neat! Thanks.
Done. The letter should appear at
http://lists.qt-project.org/pipermail/jeg/ in the March section.
--
anatoly t.
anatoly techtonik
> On Fri, Mar 9, 2012 at 11:56 AM, Matti Airas <matti....@nokia.com> wrote:
>> On 08.03.2012 19:28, ext anatoly techtonik wrote:
>>>
>>> Well, somebody needs to execute this stuff -
>>> http://confluence.atlassian.com/display/JIRA/Importing+Data+from+Bugzilla
>>>
>>> I'll try to contact tracker list about this.
>>
>>
>> Neat! Thanks.
>
> Done. The letter should appear at
> http://lists.qt-project.org/pipermail/jeg/ in the March section.
Good news. JIRA team received the letter and opened an issue (see below).
There are still some questions:
1. Should we import all tickets or those that are open right now?
2. If we import all tickets, should we preserve numbering?
Please add your concerns to the JIRA ticket.
---------- Forwarded message ----------
Date: Wed, Mar 21, 2012 at 10:53 AM
Subject: RE: [JEG] Import PySide bugs
To: tech...@gmail.com, j...@qt-project.org
A JIRA issue has been started to track this request.
https://bugreports.qt-project.org/browse/QTJIRA-164
Please raise requests to that JIRA project.
Hugo Parente Lima
> On Sat, Mar 10, 2012 at 10:19 AM, anatoly techtonik <tech...@gmail.com>
wrote:
> > On Fri, Mar 9, 2012 at 11:56 AM, Matti Airas <matti....@nokia.com>
wrote:
> >> On 08.03.2012 19:28, ext anatoly techtonik wrote:
> >>> Well, somebody needs to execute this stuff -
> >>> http://confluence.atlassian.com/display/JIRA/Importing+Data+from+Bugzil
> >>> la
> >>>
> >>> I'll try to contact tracker list about this.
> >>
> >> Neat! Thanks.
> >
> > Done. The letter should appear at
> > http://lists.qt-project.org/pipermail/jeg/ in the March section.
>
> Good news. JIRA team received the letter and opened an issue (see below).
> There are still some questions:
>
> 1. Should we import all tickets or those that are open right now?
> 2. If we import all tickets, should we preserve numbering?
Better to import all tickets preserving the numbering, because many of our
unit test are named like test_bugXXX.py, then when we face a regression and
need to do some archaeology it's a just a matter of going to bugzilla and see
the bug comments.
They could ignore bugs with numbers already present on jira, they are really
too old anyway, probably from boost::python time.
> Please add your concerns to the JIRA ticket.
>
> ---------- Forwarded message ----------
> Date: Wed, Mar 21, 2012 at 10:53 AM
> Subject: RE: [JEG] Import PySide bugs
> To: tech...@gmail.com, j...@qt-project.org
>
>
> A JIRA issue has been started to track this request.
> https://bugreports.qt-project.org/browse/QTJIRA-164
>
> Please raise requests to that JIRA project.
> --
> anatoly t.
> _______________________________________________
> PySide mailing list
> PyS...@qt-project.org
> http://lists.qt-project.org/mailman/listinfo/pyside
--