The original intention of this thread was cache-side config generation, we
should take other conversations to other threads if we think now is the
time to have them.
First of all, thanks for putting the thought and time into this. I do
think large changes like this might be better first discussed
I'm fine with that as well
On Fri, Aug 2, 2019, 15:55 Rawlin Peters wrote:
> +1
>
> At our current release cadence, that sounds good to me.
>
> - Rawlin
>
> On Fri, Aug 2, 2019 at 10:46 AM Dave Neuman wrote:
> >
> > I think we want to support the latest two Minor or Major versions, not
> just
>
+1
At our current release cadence, that sounds good to me.
- Rawlin
On Fri, Aug 2, 2019 at 10:46 AM Dave Neuman wrote:
>
> I think we want to support the latest two Minor or Major versions, not just
> the latest two Major versions. When 3.1 is released we support 3.0.1 and
> 3.1 and no longer s
I think we want to support the latest two Minor or Major versions, not just
the latest two Major versions. When 3.1 is released we support 3.0.1 and
3.1 and no longer support 2.2. The reason is that our releases (especially
Major ones) are very infrequent and it’s not practical to support a release
+1
On Fri, Aug 2, 2019 at 10:01 AM Robert Butts wrote:
> +1
>
> I'm in favor of being liberal with experimental things. Just name it
> something someone won't mistake for anything stable or release-ish,
> "dev-githubactions" or whatever. And delete it if/when you're no longer
> using it.
>
>
> O
+1
I'm in favor of being liberal with experimental things. Just name it
something someone won't mistake for anything stable or release-ish,
"dev-githubactions" or whatever. And delete it if/when you're no longer
using it.
On Fri, Aug 2, 2019 at 9:22 AM Gray, Jonathan
wrote:
> Nope, I've done s
Nope, I've done similar things in the past for Jenkins (and it's on my todo
list again, so I'm curious what you find out).
Jonathan G
On 8/2/19, 8:54 AM, "ocket " wrote:
I wanted to mess around with GitHub actions for Traffic Control - but
they're in beta and I haven't been grant
I wanted to mess around with GitHub actions for Traffic Control - but
they're in beta and I haven't been granted access to them as a GitHub user.
But Apache as an organization has. So basically, I can mess with them on
the ATC repo, but not on my personal fork.
For that purpose, I was wondering if
I agree, when the latest release is version X.Y.Z and Y=0 then version
X-1.a.b should receive both bug and security fixes (where a is the latest
minor version of release X-1 and b is the latest patch of that version).
But when Y>0, X-1.a.b receives only security updates and X.Y-1.b gets both
bugfix
