Am 04.04.2018 um 15:06 schrieb Jim Jagielski:
>> On Apr 4, 2018, at 9:01 AM, Jim Jagielski <> 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)...

I don't know if there is already a plan, but what about voting for a
release manager and get the thing going?

Regards, Matthias

> 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:
> For additional commands, e-mail:

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to