Re: Missing tag for 1.9.0 release

I wouldn’t be surprised if the ‘real’ thing came about after the last Flume release. I know we went back and tagged all the old Log4j releases after that came out. I will see if I can’t get a tag applied to the correct place. Ralph > On Mar 8, 2022, at 2:37 PM, Sean Busbey wrote: > > > Hi!

Re: [DISCUSS] consolidating and documenting contributor guidelinees

> On Mar 8, 2022, at 12:39 PM, Sean Busbey wrote: > > >> On Mar 8, 2022, at 11:44 AM, Ralph Goers wrote: >> >> >> >>> On Mar 8, 2022, at 8:55 AM, Sean Busbey wrote: >>> >>> - suggest all changes as PRs >> >> Generally, I am OK with that. As there have been no commits and no other >> p

Missing tag for 1.9.0 release

Hi! We’re missing a git tag for the 1.9.0 release. Could someone push one? From looking at the VOTE threads, I believe this git commit is what was voted on: > d4fcab4f501d41597bc616921329a4339f73585e That’s the current head of branch-1.9. I see that prior releases were named like “release-

Re: [DISCUSS] consolidating and documenting contributor guidelinees

> On Mar 8, 2022, at 11:44 AM, Ralph Goers wrote: > > > >> On Mar 8, 2022, at 8:55 AM, Sean Busbey wrote: >> >> - suggest all changes as PRs > > Generally, I am OK with that. As there have been no commits and no other > participants I didn’t see the point of doing PRs for all the work I ha

Re: [DISCUSS] release planning

> On Mar 8, 2022, at 11:25 AM, Ralph Goers wrote: > > Answers inline below. FWIW, these are my opinions. I don’t know that the PMC > has ever made declarations to these. I would like this thread to be the start of us as a project documenting what expectations we want folks to have. Does that

Re: [DISCUSS] consolidating and documenting contributor guidelinees

> On Mar 8, 2022, at 8:55 AM, Sean Busbey wrote: > > > Hi folks! > > Right now we have contributor guidelines in a couple of places: > > * source tree as CONTRIBUTING.md and DEVNOTES, visible on GitHub > * confluence on a HOW TO CONTRIBUTE and Developer Section pages, linked from > the web

Re: [DISCUSS] release planning

Answers inline below. FWIW, these are my opinions. I don’t know that the PMC has ever made declarations to these. > On Mar 8, 2022, at 8:34 AM, Sean Busbey wrote: > > > Hi folks! > > Apologies if I missed this discussion; I’ve read back through the dev list > through 2021. I wanted to make s

[GitHub] [flume] tmgstevens commented on a change in pull request #351: Docker

tmgstevens commented on a change in pull request #351: URL: https://github.com/apache/flume/pull/351#discussion_r821824821 ## File path: flume-ng-dist/Dockerfile ## @@ -0,0 +1,39 @@ +# Licensed to the Apache Software Foundation (ASF) under one +# or more contributor license agr

[DISCUSS] consolidating and documenting contributor guidelinees

Hi folks! Right now we have contributor guidelines in a couple of places: * source tree as CONTRIBUTING.md and DEVNOTES, visible on GitHub * confluence on a HOW TO CONTRIBUTE and Developer Section pages, linked from the website We also have a few different ways of accepting contributions * J

[DISCUSS] release planning

Hi folks! Apologies if I missed this discussion; I’ve read back through the dev list through 2021. I wanted to make sure I have the correct expectations before I start stomping around in Jira. I haven’t found a write up anywhere on what promises we make for major/minor/patch versions. What i