1.0 release

[Jack Bearden <ja...@altiscale.com>]

Hi all,

What kind of things are preventing Yetus from a 1.0 release? What does
everyone expect before 1.0?

- Jack

Re: 1.0 release

[Sean Busbey <bu...@apache.org>]

You must have hit send early there Allen...

;)

On Wed, Sep 12, 2018, 10:11 Allen Wittenauer
<aw...@effectivemachines.com.invalid> wrote:

>
> > On Sep 4, 2018, at 12:38 PM, Jack Bearden <ja...@altiscale.com> wrote:
> > What kind of things are preventing Yetus from a 1.0 release? What does
> > everyone expect before 1.0?
>
>
>         I’m more than a little disappointed that no one has responded to
> this question.. but I can’t say I’m exactly surprised. :(
>
>

Re: 1.0 release

[Allen Wittenauer <aw...@effectivemachines.com.INVALID>]

> On Sep 4, 2018, at 12:38 PM, Jack Bearden <ja...@altiscale.com> wrote:
> What kind of things are preventing Yetus from a 1.0 release? What does
> everyone expect before 1.0?


	I’m more than a little disappointed that no one has responded to this question.. but I can’t say I’m exactly surprised. :(

	

Re: 1.0 release

[Sean Busbey <bu...@apache.org>]

Before we hit 1.0 I'd want a formalization of what we're saying the
compatibility expectations are for everything we publish.

For example, we've changed the output of release doc maker a couple times.
Would we need to stop doing that?

I've seen Allen mention a Jenkins plugin a couple of times with an
implication of rewriting large parts of test-patch. Could that happen post
1.0 without a major version change?

Prior to 1.0 I should probably do a check to see if anything HBase does
with test-patch could be made less hacky.

When we started I remember saying that I wanted to see a non-asf project
use yetus before declaring 1.0. I feel less strongly about that now because
I'm using it on a few different itches already.


On Tue, Sep 4, 2018, 14:39 Jack Bearden <ja...@altiscale.com> wrote:

> Hi all,
>
> What kind of things are preventing Yetus from a 1.0 release? What does
> everyone expect before 1.0?
>
> - Jack
>