Hi Paolo, may you explain exactly what you mean with "builds are often broken" ? May you give an example of such and, in the example, what should the "sheriff" do to manage it ? (Sorry, I just need to understand what you are referring to)
Thanks! Il giorno gio 1 ago 2024 alle ore 15:09 Paolo Bizzarri <[email protected]> ha scritto: > Hello kie mates, > > please find my proposal in the following. > > PROBLEM > - builds are often broken and they stay broken for a long time. There seem > to be not a clear definition of who should take care of this > > CONTEXT > - fixing builds is slow, annoying and tipically is more a job of chasing > someone else than fixing it yourself. So it becomes quickly wearing. > > PROPOSED SOLUTION > - identify a number of build sheriffs that look at the various builds, open > the relevant issues for tracking and chase other devs and contributors to > fix the issues themselves. The sheriffs are not supposed to fix everything > by themselves, but instead to keep the attention of other developers on the > status of the builds. > I suggest we have three sheriffs, that stay around for one month and then > pass the token to someone else: one for drools and optaplanner, one for > kogito, one for kie-tools. > > Let me know your ideas and feedback. > > Regards > > Paolo >
