Skip to main content
Mohammad A
Mohammad A
Senior
April 1, 2017
Question

Request for a bug tracking system

  • April 1, 2017
  • 10 replies
  • 1695 views
Posted on April 02, 2017 at 00:18

It happens many times that I find a bug inside the Cube/HAL driver or even inside the comments and documents and I really want to report it, so they can FIX it, thus making a bug free environment to develop my/our applications, BUT the lack of a bug tracking system prevents me to report it.

Even though I see some users report bugs in the forum, but it feels like useless as nobody replys to them or they can't find out if their contribution into fixing bugs has been observed by ST employees.

So, my request is starting a bug reporting/tracking system. I think it's a win-win suggestion.

#bug #request
This topic has been closed for replies.

10 replies

AvaTar
AvaTar
Senior III
April 2, 2017
Posted on April 02, 2017 at 11:04

I bet they have a bugtracking software in place internally, without access from 'outsiders' like here on this forum.

But let's see what the ST staff tells us ...

S.Ma
S.Ma
Principal
April 2, 2017
Posted on April 02, 2017 at 13:10

Maybe a git of the source files would make the loop back more reactive?

Mohammad A
Mohammad AAuthor
Senior
April 2, 2017
Posted on April 02, 2017 at 21:52

nice, so we can commit changes and request for a pull

Mohammad A
Mohammad AAuthor
Senior
April 2, 2017
Posted on April 02, 2017 at 23:07

I would like to ask some of moderators forward this request to staffs if possible.

valentin
valentin
Associate III
April 3, 2017
Posted on April 03, 2017 at 02:18

+1 would be really nice and would probably save some time on ST's side, too

Imen.D
ST Technical Moderator
April 3, 2017
Posted on April 03, 2017 at 11:30

Hello,

I will raise your request internally.

All your comments and suggestions are welcome in order to improve our solutions.

Imen

In order to give better visibility on the answered topics, please click on 'Best answer' on the reply which solved your issue or answered your question. Thanks
Mohammad A
Mohammad AAuthor
Senior
April 6, 2017
Posted on April 06, 2017 at 15:58

Please let us know about the conclusion of your internal

discussions

Tesla DeLorean
Tesla DeLorean
Guru
April 4, 2017
Posted on April 04, 2017 at 17:02

There definitely needs to be change in release and test strategy, where bug tracking goes along with Regression Testing and Dog Fooding of the released code.

The embedded ecosystem needs solid, tested code, you need to apply the TEN YEAR commitment to the expectation for your code. Many applications aren't going to have easy opportunities to field upgrade and may be deployed for decades. It is incumbent on ST to do a better job with the code quality.

The bug tracking has been requested repeatedly, posting unformated/unfocused bug reports to the forum is not sufficient. There needs to be ownership. You have thousands of eyes on the code, you need to use them effectively.

Tips, Buy me a coffee, or three.. PayPal Venmo (See Profile) Up vote any posts that you find helpful, it shows what's working..
AvaTar
AvaTar
Senior III
April 4, 2017
Posted on April 04, 2017 at 19:32

The bug tracking has been requested repeatedly, posting unformated/unfocused bug reports to the forum is not sufficient. There needs to be ownership. You have thousands of eyes on the code, you need to use them effectively.

Linux, especially the kernel, are examples that this might work - on professional level, with professional results.

Terms & ConditionsAccessibility statement