Re: [Tiki-devel] Wishlist/bug/issue tracker on dev.tiki.org: please no one change anything without my approval until futher notice

[Bernard S. <bs...@sh...>]

On 31 May 2013, at 05:53 , Marc Laporte <ma...@ma...> wrote:

> I merged the column "revision" into the description field and then
> deleted it. (There were just a few tickets with some data)
> 
> a) 95%+ of bug reports won't have a revision, but just a version number
> b) I see no use case for sorting or filtering
> 
> 
> 

Marc,

It seams you missed some discussions here…
The pretty tracker i set official goal is to give a solution to the"pro or techi" members of the community.
Those having access to the regression page editing.

Those reports included the revision number all the way and it is one critical when doing triage or debugging (i doubt they could be a question about it).

I think you are looking on the bug tracker the "old way", for a unique use with a unique display type.
Trackers (with the addition of template and plugins) are flexible enough to be part of different process with the same (or partial) data and Tiki permission are flexible enough to create different tracker tools for different type of users.
That's how trackers and trackers tools are evolving in Tiki.


Marc, on one hand i perfectly understand your concern about old data, on the otheri think there is room for a discussion with all the actor that are involved in report/triage/bug tracking/release before hard work being done during a month (and discussed openly) is undone overnight. Nothing was deleted or made irreversible - creating tracker Id14 outside tracker Id5 to have flexibility was part of the plan. :)


Bernard


PS : Dear Marc, since the 15/04 this bug trackers things is underwork, everyone reading the list knows that.
Each time things where changed or we go in a direction or another people discuss it openly.

The event things (Olaf's email you mention) was checked and implemented in coordination with several key players (Xavi that is the father of the event feature in trackers and Changi that manage the cron and server logs, sorry for the others :)).
I missed a permission on a template and it was corrected a few hours after being reported. This is quit short to says that "obviously was put in production without any testing"… :( Half a dozen of people sweat and gave their time to get it to work.


> 
> On Thu, May 30, 2013 at 7:02 PM, Marc Laporte <ma...@ma...> wrote:
>> Hi!
>> 
>> To avoid data desync, I deleted the new categorization project until their is a
>> 1- data migration plan
>> 2- the 100+ reports are updated
>> 
>> But here is a copy of the tracker field definitions and
>> https://dev.tiki.org/tiki-view_tracker.php?trackerId=14 remains
>> 
>> 
>> 
>> 
>> 
>> On Thu, May 30, 2013 at 6:20 PM, Marc Laporte <ma...@ma...> wrote:
>>> As a follow-up:
>>> 
>>> A data transition plan is necessary when working with live data.
>>> 
>>> Some new categories were created for wishes, which is sensible.
>>> However, the old category system is still there. Thus, we have data in
>>> both the new and the old.
>>> 
>>> This makes reports very difficult. The new system also has a flaw that
>>> you can only pick one category (I understand that the goal is to have
>>> a cleaner UI). So when there is a bug with WYSIWYG in Trackers, do you
>>> put this in WYSIWYG or in Trackers?  The new system can't deal with
>>> this with this is very important reality.
>>> 
>>> I will revert to previous categories before the data diverges too much
>>> because 100+ reports at https://dev.tiki.org/Keywords have not been
>>> adapted to a new system.
>>> 
>>> M
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> On Thu, May 30, 2013 at 4:52 PM, Marc Laporte <ma...@ma...> wrote:
>>>> And beside not being applicable to feature requests, it just flat
>>>> didn't work, and obviously was put in production without any testing,
>>>> as the blank email received by Olaf:
>>>> http://tiki.org/tiki-view_forum_thread.php?comments_parentId=47242
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> On Thu, May 30, 2013 at 4:48 PM, Marc Laporte <ma...@ma...> wrote:
>>>>> For the record, I am deleting the events that were created. This was
>>>>> not well thought out.
>>>>> 
>>>>> Below is a copy for the record.
>>>>> 
>>>>> 
>>>>> o       c       4 weeks creation
>>>>> mail: creator
>>>>> before: 5 days
>>>>> subject: Your bug report will be closed in 5 days
>>>>> body: wiki:closingbugreport_notification
>>>>> 
>>>>> p       c       4 weeks modification
>>>>> mail: creator
>>>>> before: 5 days
>>>>> subject: Your bug report will be closed in 5 days
>>>>> body: wiki:closingbugreportnotmodified_notification
>>>>> 
>>>>> 
>>>>> On Thu, May 30, 2013 at 4:46 PM, Marc Laporte <ma...@ma...> wrote:
>>>>>> Hi!
>>>>>> 
>>>>>> We have a huge problem of data corruption on dev.tiki.org
>>>>>> 
>>>>>> Please no one change anything until further notice until we sort this out.
>>>>>> 
>>>>>> Thanks
>>>>>> 
>>>>>> 
>>>>>> --
>>>>>> Marc Laporte
>>>>>> 
>>>>>> http://MarcLaporte.com
>>>>>> http://Tiki.org/MarcLaporte
>>>>>> http://AvanTech.net
>>>>> 
>>>>> 
>>>>> 
>>>>> --
>>>>> Marc Laporte
>>>>> 
>>>>> http://MarcLaporte.com
>>>>> http://Tiki.org/MarcLaporte
>>>>> http://AvanTech.net
>>>> 
>>>> 
>>>> 
>>>> --
>>>> Marc Laporte
>>>> 
>>>> http://MarcLaporte.com
>>>> http://Tiki.org/MarcLaporte
>>>> http://AvanTech.net
>>> 
>>> 
>>> 
>>> --
>>> Marc Laporte
>>> 
>>> http://MarcLaporte.com
>>> http://Tiki.org/MarcLaporte
>>> http://AvanTech.net
>> 
>> 
>> 
>> --
>> Marc Laporte
>> 
>> http://MarcLaporte.com
>> http://Tiki.org/MarcLaporte
>> http://AvanTech.net
> 
> 
> 
> -- 
> Marc Laporte
> 
> http://MarcLaporte.com
> http://Tiki.org/MarcLaporte
> http://AvanTech.net
> 
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite
> It's a free troubleshooting tool designed for production
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://p.sf.net/sfu/appdyn_d2d_ap2
> _______________________________________________
> TikiWiki-devel mailing list
> Tik...@li...
> https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel