Hi Mike,

I'd like to see us increment the version on master ASAP. Once 0.3.0 is
released, master is no longer the 0.3.0 branch.

I recommend that we run 0.3.x patches off the 0.3.0 release branch and
rename master to 0.4.0.

Thanks,

-D...


On Mon, Nov 14, 2016 at 4:40 PM, Michael Miklavcic <
[email protected]> wrote:

> 1 - What the next version should be.
> 2 - When we should increment the version
>
> On Mon, Nov 14, 2016 at 2:35 PM, [email protected] <[email protected]>
> wrote:
>
> > Sorry, but I don't exactly follow.  Are you looking to discuss what the
> > version number should be next time around (1.0 vs 0.4 vs 0.3.1?) or what
> > tasks need to be accomplished before the next version of metron is
> > considered ready?  Thanks,
> >
> > Jon
> >
> > On Mon, Nov 14, 2016, 16:29 Michael Miklavcic <
> [email protected]
> > >
> > wrote:
> >
> > > This is a thread to discuss what the next version of Metron should be
> > > after Apache
> > > Metron 0.3.0-RC1 incubating is released, e.g. 0.3.1?
> > >
> > > I'd like to up the rev asap, however one thing to consider is that we
> > might
> > > change the version again at a later point in time prior to the next
> > > release. This current release candidate being a case in point. On the
> > other
> > > hand, I am also currently working on simplifying the version change
> > process
> > > so it might not be a big deal either way.
> > >
> > > Thanks,
> > > Mike Miklavcic
> > >
> > --
> >
> > Jon
> >
> > Sent from my mobile device
> >
>

Reply via email to