Hello, I'd like to propose that we publish a minor release of parquet, eg version 1.8.0
I think this also points out that we could use some policy / guiding principles around when and how to do minor releases (ideally we can do them fairly often). I think a good policy would be to choose a point in time to "begin" a release, at which point the only pending PRs that block the release are bug fixes for issues known to be in master already. Once those blockers are merged, the release goes out, and we can start merging new features again. The motivation for this is to prevent long releases blocked on many pending features. If we can release early and often, we won't feel a need to get a PR into any one particular release. We can either do this by being careful about what goes into master (aim for master always being releasable), or we can make release branches and only merge bug fixes into release branches. I think maintaining release branches w/ backports can get fairly difficult so I'd probably lean towards not going that direction. So that said, what do you all think? Also, does anyone have any bug fixes that needs to go into master before a 1.8.0 release? If so please add it to: https://issues.apache.org/jira/browse/PARQUET-292 Thanks! Alex -- Alex Levenson @THISWILLWORK
