We have different types of bugs, where users produce compilable code: A) Incorrect GObject mechanisms applications, in any area related to construct, signals, properties an so or programming errors (including Cush code assumptions not directly supported in Vala yet). They can fixable by the user using code practices, like code conventions and tips. This kind of things can be documented, as a limitation, in order to help users to avoid this kind of errors. This bugs can be targeted to 1.2, I think, because Vala can help users by emitting warnings or errors, when possible, but are not a barrier to use Vala in a safe way. B) Valid Vala code and valid GObject features application, fixable only in Vala. These should be fixed before 1.0. These stuff is important, in order to advance and focus resources in critical issues. Vala 1.0 is not around the corner, then there is no hurry. Just is important to clarify users how to use Vala with its limitations. ---------- Forwarded message ---------- From: Rico Tzschichholz <ricotz t-online de> Date: 2017-02-23 9:37 GMT-06:00 Subject: Fwd: Re: Vala bug management To: Al Thomas <astavale yahoo co uk>, "Dr. Michael Lauer" <mickey vanille de
Cc: Daniel Espinosa <esodan gmail com> Just forwarding this to Al and Michael. -------- Weitergeleitete Nachricht -------- Betreff: Re: Vala bug management Datum: Thu, 23 Feb 2017 06:52:59 -0600 Von: Daniel Espinosa <esodan gmail com> An: Rico Tzschichholz <ricotz t-online de> I really appreciate your time to discuss bug management in private before to continue. If you agree, we can stablish following policy: 1) If a bug produce invalid C code should be keep open until it is fixed 2) If bug produce valac segfault then it should be marked as important-blocker. 3) If bug produce a segfault at runtime but it has a workaround it should be marked as low-enhancement 4) If bug produce invalid C code but is a programming error derived from miss understanding on how GObject works, this is, programmer should take care to avoid, bug should be marked as low-enhancement Bug reporter should know agreed politics in order to help in marking their bugs, to reduce load and focus on important bugs. I'm trying to explain workarounds in bug reports and reporter should do the same if knowns, this will help others to find help to fix their code. There are two issues: A) People have miss understanding about Vala design and may forget to study GObject before use it B) Bugzilla have >600 bugs most of them have workarounds, keep noise on Vala code generation quality C) There are bugs on bindings but not in valac, they different beast. May is time to create a repository for bindings and one for Vala El 23 feb. 2017 12:24 a. m., "Rico Tzschichholz" <ricotz t-online de <mailto:ricotz t-online de>> escribió: Hello Daniel, it is great to see your enthusiasm for cleaning up bugzilla! Unfortunately closing valid bugs as resolved-notabug is not wanted. Please add comments or request for more feedback or reproducers from the reporter to fully understand the scope of a bug. Therefore if a provided test-cases still causes faulty c-code or lets valac throwing errors then please leave the bug open. For example https://bugzilla.gnome.org/show_bug.cgi?id=604973 <https://bugzilla.gnome.org/show_bug.cgi?id=604973> -- if some vala snippet causes the generation of invalid c-code then valac should detect this and there is a chance to have it fixed. Best regards, Rico -- This electronic message may contain privileged and confidential information intended only for the use of the addressees named above. If you are not the intended recipient of this email, we kindly ask you to delete this message and any attachment. You are hereby notified that any use, dissemination, distribution, reproduction of this email is prohibited. If you have received this email in error, please notify sender immediately. Any document, image or any other form of electronic representation of any work attached to this email, is suitable to be protected by copyright enforcement by applicable law in your or sender's Country's and International Legislation Trabajar, la mejor arma para tu superación "de grano en grano, se hace la arena" (R) (en trámite, pero para los cuates: LIBRE)
Attachment:
signature.asc
Description: PGP signature