Re: [VOTE] Move Traffic Control to full GitHub
+1 On Thu, May 18, 2017 at 3:35 PM, Dave Neumanwrote: > +1, thanks for putting the vote up Jan > > On Thu, May 18, 2017 at 4:57 PM, Steve Malenfant > wrote: > > > +1 > > >
Re: [VOTE] Move Traffic Control to full GitHub
+1, thanks for putting the vote up Jan On Thu, May 18, 2017 at 4:57 PM, Steve Malenfantwrote: > +1 >
Re: [VOTE] Move Traffic Control to full GitHub
+1 On Thu, May 18, 2017 at 2:57 PM Steve Malenfantwrote: > +1 >
Re: [VOTE] Move Traffic Control to full GitHub
+1
Re: [VOTE] Move Traffic Control to full GitHub
+1 Ashish and I can help with moving the wiki, issues, and feature requests. Ryan DurfeyM | 303-524-5099 From: "Gelinas, Derek"Reply-To: "dev@trafficcontrol.incubator.apache.org" Date: Thursday, May 18, 2017 at 2:43 PM To: "dev@trafficcontrol.incubator.apache.org" Subject: Re: [VOTE] Move Traffic Control to full GitHub +1 On May 18, 2017, at 4:42 PM, Jeff Elsloo > wrote: +1 on moving. -- Thanks, Jeff On Thu, May 18, 2017 at 2:40 PM, Dan Kirkwood > wrote: +1 On Thu, May 18, 2017 at 2:32 PM, Jan van Doorn > wrote: In https://lists.apache.org/thread.html/5bdb9b073343f49c1d5b85147eb9d260bf7ad15d61384929993c7e1d@%3Cdev.trafficcontrol.apache.org%3E Dave mentioned that we can now move to "full" GitHub. Some more information in that thread if you are not familiar. I would like to call an official vote on that. This vote will be open for at least 72 hours. [ ] +1 Move Traffic Control to use full GitHub [ ] 0 No opinion [ ] -1 Do not Move Traffic Control to use full GitHub because... Rgds, JvD
Re: [VOTE] Move Traffic Control to full GitHub
+1 > On May 18, 2017, at 4:42 PM, Jeff Elsloowrote: > > +1 on moving. > -- > Thanks, > Jeff > > >> On Thu, May 18, 2017 at 2:40 PM, Dan Kirkwood wrote: >> +1 >> >>> On Thu, May 18, 2017 at 2:32 PM, Jan van Doorn wrote: >>> In >>> https://lists.apache.org/thread.html/5bdb9b073343f49c1d5b85147eb9d260bf7ad15d61384929993c7e1d@%3Cdev.trafficcontrol.apache.org%3E >>> Dave >>> mentioned that we can now move to "full" GitHub. Some more information in >>> that thread if you are not familiar. I would like to call an official vote >>> on that. >>> >>> This vote will be open for at least 72 hours. >>> >>> [ ] +1 Move Traffic Control to use full GitHub >>> [ ] 0 No opinion >>> [ ] -1 Do not Move Traffic Control to use full GitHub because... >>> >>> Rgds, >>> JvD >
Re: [VOTE] Move Traffic Control to full GitHub
+1 on moving. -- Thanks, Jeff On Thu, May 18, 2017 at 2:40 PM, Dan Kirkwoodwrote: > +1 > > On Thu, May 18, 2017 at 2:32 PM, Jan van Doorn wrote: >> In >> https://lists.apache.org/thread.html/5bdb9b073343f49c1d5b85147eb9d260bf7ad15d61384929993c7e1d@%3Cdev.trafficcontrol.apache.org%3E >> Dave >> mentioned that we can now move to "full" GitHub. Some more information in >> that thread if you are not familiar. I would like to call an official vote >> on that. >> >> This vote will be open for at least 72 hours. >> >> [ ] +1 Move Traffic Control to use full GitHub >> [ ] 0 No opinion >> [ ] -1 Do not Move Traffic Control to use full GitHub because... >> >> Rgds, >> JvD
Re: [VOTE] Move Traffic Control to full GitHub
+1 On Thu, May 18, 2017 at 2:32 PM, Jan van Doornwrote: > In > https://lists.apache.org/thread.html/5bdb9b073343f49c1d5b85147eb9d260bf7ad15d61384929993c7e1d@%3Cdev.trafficcontrol.apache.org%3E > Dave > mentioned that we can now move to "full" GitHub. Some more information in > that thread if you are not familiar. I would like to call an official vote > on that. > > This vote will be open for at least 72 hours. > > [ ] +1 Move Traffic Control to use full GitHub > [ ] 0 No opinion > [ ] -1 Do not Move Traffic Control to use full GitHub because... > > Rgds, > JvD
[VOTE] Move Traffic Control to full GitHub
In https://lists.apache.org/thread.html/5bdb9b073343f49c1d5b85147eb9d260bf7ad15d61384929993c7e1d@%3Cdev.trafficcontrol.apache.org%3E Dave mentioned that we can now move to "full" GitHub. Some more information in that thread if you are not familiar. I would like to call an official vote on that. This vote will be open for at least 72 hours. [ ] +1 Move Traffic Control to use full GitHub [ ] 0 No opinion [ ] -1 Do not Move Traffic Control to use full GitHub because... Rgds, JvD
Re: Traffic Control SLA
I feel like we aren't mature enough yet to formalize this. We only have 1 official "release" under our belt and we are working towards our second. I think the best solution for now would be to try to define this as we go and handle security, regressions, etc with discussions. Of course, I can be convinced otherwise. On Wed, May 17, 2017 at 3:27 PM, Eric Friedrich (efriedri) < efrie...@cisco.com> wrote: > Hi All- > We had some discussion around what level of support we want to offer to > users of our software. > > > I'd like to suggest a policy that for all releases we will fix all > security issues and we will fix regressions at discretion of the release > manager. > > There was also discussion about how long we should support a release for. > > Options included: > - Doing only 1-2 LTS releases per year > - Having many smaller point releases with 1 or 2 LTS releases per year. > > We should also define the support timeline of an LTS release to say > supporting the two most recent LTS at all times. > > Thoughts? > >