master revision tracking

["Fieck, Brennan" <Br...@comcast.com>]

So I'm confused. I've heard conflicting answers to this question: If I add something to Master, in what version should the documentation say it was added?


The ones that make sense to me:
* 4.0.0 (someone said this was what master is tracking now)
* 3.1.0 (someone ELSE stated it was this)
* 3.0.1 (current latest revision - though not released yet)
* 3.0.0 (current contents of the VERSION file at the repository's root)

Re: master revision tracking

[Rawlin Peters <ra...@gmail.com>]

I've mostly been operating under the assumption that master is
basically pegged for 4.0 at this point. In 3.0 the old TO UI is
labelled as deprecated for removal in 4.0, and on master we've
completely disabled the old TO UI. I think the disabling of the old TO
UI in favor of using Traffic Portal going forward warrants a major
version bump to 4.0, but I could be possibly swayed into 3.1 (although
it would make the legacy TO UI deprecation banner a lie).

- Rawlin

On Fri, Apr 12, 2019 at 12:37 PM Eric Friedrich -X (efriedri - TRITON
UK BIDCO LIMITED c/o Alter Domus (UK) Limited -OBO at Cisco)
<ef...@cisco.com.invalid> wrote:
>
> 3.0 has already been released and any changes to 3.0 will go into the 3.0.x branch.
> Same for 3.0.1 - that release will come off the 3.0.x branch as well.
>
> The next release off the master branch will be either 3.1 or 4.0 depending on the decision of the community in declaring a new major version.
>
> Unless that decision gets made, I think its reasonable to treat master as 3.1.
>   If we do decide the next release is 4.0, there would be some work to go update version numbers- I’m just assuming minor releases are more common than major releases
>
> —Eric
>
>
> > On Apr 12, 2019, at 2:33 PM, Fieck, Brennan <Br...@comcast.com> wrote:
> >
> > So I'm confused. I've heard conflicting answers to this question: If I add something to Master, in what version should the documentation say it was added?
> >
> >
> > The ones that make sense to me:
> > * 4.0.0 (someone said this was what master is tracking now)
> > * 3.1.0 (someone ELSE stated it was this)
> > * 3.0.1 (current latest revision - though not released yet)
> > * 3.0.0 (current contents of the VERSION file at the repository's root)
> >
>

Re: master revision tracking

["Eric Friedrich -X (efriedri - TRITON UK BIDCO LIMITED c/o Alter Domus (UK) Limited -OBO at Cisco)" <ef...@cisco.com.INVALID>]

3.0 has already been released and any changes to 3.0 will go into the 3.0.x branch.
Same for 3.0.1 - that release will come off the 3.0.x branch as well.

The next release off the master branch will be either 3.1 or 4.0 depending on the decision of the community in declaring a new major version.

Unless that decision gets made, I think its reasonable to treat master as 3.1. 
  If we do decide the next release is 4.0, there would be some work to go update version numbers- I’m just assuming minor releases are more common than major releases

—Eric


> On Apr 12, 2019, at 2:33 PM, Fieck, Brennan <Br...@comcast.com> wrote:
> 
> So I'm confused. I've heard conflicting answers to this question: If I add something to Master, in what version should the documentation say it was added?
> 
> 
> The ones that make sense to me:
> * 4.0.0 (someone said this was what master is tracking now)
> * 3.1.0 (someone ELSE stated it was this)
> * 3.0.1 (current latest revision - though not released yet)
> * 3.0.0 (current contents of the VERSION file at the repository's root)
>