[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Don't put new packages through updates-testing

Rahul Sundaram wrote:
Hans de Goede wrote:

Which sure does NOT cover basic functionality. First please get a clue about what we are talking about (by say packaging 30 packages?) and then return to this discussion.

Thank you for first getting a clue,

No thanks to you or Ralf for insulting your fellow contributors and showing the your "joke" claim wasn't really a joke after all. If you want to prevent me or anyone from suggesting anything at all before we start packaging a arbitrary number of 30 packages that isn't going to happen.

The 30 packages part was not serious, it was an example. The getting a clue part is not a joke, if you do not understand what Ralf means with a simple program start (without any cmdline arguments) for many programs will only result in a usage message, and then claim that getting the usage message covers testing basic functionality, then you do not know what you're talking about. Ever heard of coverage percentages for software tests? Only getting the usage() message scores you about 1 to 0.1 % of coverage for a small program (and then I'm being very optimistic), even less for a larger one.

Distribution building is more than packaging. It involves everything from documentation, translation to infrastructure work and lots more. We are all contributors in different areas. Keep that mind.

I know that and I very much value and appreciate all the work done by documenters, tranlaters, the infra structure team and all I forget. However I'm not participating in discussions about translations as I know very little about translations. Learn to know you're own weakness-es, and if you have little knowledge of something, then don't mingle yourself in discussions about it.

Atleast so far you've shown little knowledge of testing.



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]