> On Apr 4, 2018, at 9:01 AM, Jim Jagielski <j...@jagunet.com> wrote: > > > I will start another thread on the gbuild topic... >
First and foremost, I am incredibly impressed with the work being done on the gbuild migration. I really am. However, and there's always a "however", there must come a time where we "hold the line" on migration in hopes of getting a 4.2.0 out. As such, I think some sort of plan might be due (and apologies if we have such a documented plan already in place)... Does it make sense to spend time to list modules that still need that migration and then prioritize them? As well as create a policy such that all "new and updated" modules must use gbuild but for existing modules, "if it ain't broke, don't fix it"? I'm not trying to stifle the migration, it's just that it appears to me that we need better management about it. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
