Re: Guideline for contributing new extensions

[Marcelo Vanzin <va...@apache.org>]

The document seems to imply that all source will live in the same
repository. Is that the goal?

My preference would be to have separate extensions live in separate
repos; that way, they can have their different release cycles that
might align better with the systems they're actually dependent on
(e.g. a Kafka extension releasing right after a new major Kafka
version). And one extension being unstable doesn't affect development
for other extensions.


On Tue, May 31, 2016 at 4:40 PM, Luciano Resende <lu...@gmail.com> wrote:
> I have drafted a very basic guideline for contributing new extensions for
> Apache Bahir. My main goal is to use that as the start point to a community
> discussion that can flush out some details and make the process for
> proposing, accepting and retiring a extension very transparent.
>
> Please review the initial draft at :
> http://bahir.apache.org/contributing-extensions/
>
> And let's use this thread for any question, comments, feedback, etc.
>
> --
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/

Re: Guideline for contributing new extensions

[Marcelo Vanzin <va...@apache.org>]

On Wed, Jun 1, 2016 at 10:34 AM, Luciano Resende <lu...@gmail.com> wrote:
> This brings a good point, but still, i think for management purposes, one
> repo might make things easier, and we could easily enable this by providing
> minor releases between runtime releases (e.g. bahir 2.0.0.1 when kafka 0.11
> comes up but spark hasn't released 2.0.1 yet)

I was envisioning something closer to Apache Commons (with a
commons-parent and each component with its own repo), but I'm fine
with starting up with your suggestion and adapting as needed.

Re: Guideline for contributing new extensions

[Luciano Resende <lu...@gmail.com>]

On Tue, May 31, 2016 at 6:51 PM, Marcelo Vanzin <va...@apache.org> wrote:

> The document seems to imply that all source will live in the same
> repository. Is that the goal?
>
>
Because the main goal is to make these extensions to follow their "runtime"
release and because we might end up having several extensions for a given
"runtime", I was thinking on having one repository per "runtime" (e.g.
Spark) which would make it easier to manage and release at the same time
Spark releases for example.


> My preference would be to have separate extensions live in separate
> repos; that way, they can have their different release cycles that
> might align better with the systems they're actually dependent on
> (e.g. a Kafka extension releasing right after a new major Kafka
> version). And one extension being unstable doesn't affect development
> for other extensions.
>
>
This brings a good point, but still, i think for management purposes, one
repo might make things easier, and we could easily enable this by providing
minor releases between runtime releases (e.g. bahir 2.0.0.1 when kafka 0.11
comes up but spark hasn't released 2.0.1 yet)

Would that be ok for starting ? And I am sure we can re-evaluate moving to
a repo per extension in the future.

Thoughts ?

-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/