openoffice-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jim Jagielski <...@jaguNET.com>
Subject gbuild migration (Was: Re: Building module store error on macOS)
Date Wed, 04 Apr 2018 13:06:01 GMT


> On Apr 4, 2018, at 9:01 AM, Jim Jagielski <jim@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-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org


Mime
View raw message