I agree with Enrico on dropping contrib and keeping recipes.
My reasons for dropping contrib projects:
- There is not much, if anything, going on around contrib. Even before
maven migration, it was a mess (it was duplicated in the tarball, some were
built, some were not, kind of randomly). Take for
I think that the key question is whether independent releases make sense.
If you have two things that must always be released in synchrony, then
having them in the same repo is a good idea.
If you have two things that are released completely independently, then
separate repos make sense.
On Wed
Il mer 22 mag 2019, 09:59 Tamas Penzes ha
scritto:
> Hi All,
>
> There is trend among Apache projects to minimise the content of the main
> project and move not crucial parts into separate repos. I mostly prefer the
> mono-repo style development, but in some cases where the connection between
> t
The downside is that you need to separately maintain, support, build infra
round, ... and release those repos. They get out of sync with the main
repo/releases, etc...
Another option is to move them to github or retire them entirely.
Patrick
On Wed, May 22, 2019 at 12:59 AM Tamas Penzes
wrote:
Hi All,
There is trend among Apache projects to minimise the content of the main
project and move not crucial parts into separate repos. I mostly prefer the
mono-repo style development, but in some cases where the connection between
the main project and a subproject is weak I find this idea suppor
