Any ideas if/when we might begin bug bankruptcy model? For those unfamiliar with the process, Bugs can become stale, abandoned, obsolete, or no longer applicable. This usually comes with age of the bug. I suggest any bugs over 2yrs old be subject to bug bankruptcy if it has not been updated within a specific amount of time. Basically we cannot test, maintain, etc EVERY bug in the queue. We could send out an email (automated) once a bug becomes of age that if the bug is not updated within the next few days, it will be deleted or marked obsolete/abandoned. This could help heavily clean up our bug queue to a more manageable sum, only keeping open bugs that are not abandoned.
On Fri, Jun 23, 2017 at 12:05 PM Sławomir Nizio <[email protected]> wrote: > Hello, > > > If Bugzilla is too complicated, maybe it's time for another tool? > > The point was how Bugzilla is configured, not the tool itself. > > > > Where do you get topics for blogging? Our forums? What about other > blogs? Facebook? Google+? > > > > As far as I understood, there are some changes needed regarding ARM on > the homepage. Do we have a ticket for that? > > > > From what I've seen, Gentoo users reemerge everything because of the new > GCC with incompatible ABI. Sabayon offers binaries, so it would cause one > big update. Does that cause too much stress on the build servers? I don't > understand the issues here... > > Point is that everything has to be rebuilt which will take quite some > time. Especially, no updates to part of packages could be provided > within that time. As I understand it, there are two ideas to tackle this > (see also the GCC-5.x Migration thread): branched repository into which > users would need to switch when all's done (using the equo hop command > [1]), or just an update freeze until all is done. Or perhaps a server > side clone being done in parallel to allow partial updates from the > old/current one, with a switch (say, rsync -av --delete from the old > one) that would be transparent to users? > > Anyway, there is a plan to update some core packages first. > > If there are further comments to this topic, I suggest making them to > the mentioned dedicated thread. > > > [1] The last time Sabayon required users to execute equo hop was several > years ago, since when Sabayon got fully rolling release. > >
