Re: [trinity-devel] Plan B

Tim is a great team leader and incredibly skilled with programming and seeing both the trees and forest. But Tim is only one person. There are many patches that have been submitted to the bugzilla. Those patches have yet to be merged. Many of those patches directly affect building packages. Perhaps I'm out in left field, but seems to me that all build related bug reports should be resolved as fast as possible. Any such report with a patch should be merged within a day or two. Granted, often we bypass the bugzilla and resolve build related bugs directly in this list, but I'm addressing those that do get filed in the bugzilla. Is Tim the only person qualified or allowed to merge patches? He has to sleep too and should not be the only person merging patches. Many of the patches are nominal or trivial. Others should be able merge those types of patches. If Tim is not the only person, is anybody who has GIT access interested in merging those patches? If Tim is the only person then why don't we have alternates to share the load for when Tim is busy with other life requirements? All of this leads into an important topic. Where do we stand when Tim has to devote time and energy to other life requirements? Do we have a Plan B to keep the project moving forward? Seems to me that whenever Tim is not merging patches the project grinds to a halt. That's a high compliment to Tim, but an uncomfortable reflection on the project. :(

Darrell --------------------------------------------------------------------- To unsubscribe, e-mail: trinity-devel-unsubscribe(a)lists.pearsoncomputing.net For additional commands, e-mail: trinity-devel-help(a)lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting