I like the idea of having a road map, but I think that's a separate discussion. I'd be happy to chime in a separate discuss thread if you want to drive this Fabian/Robert. Now that I'm re-reading my initial email, I actually think it sounded a lot like a proposal to add more information to the website. Sorry about that. My main question was actually the following:
- What is the planned feature freeze date (and planned release date) for the 1.8 release? Best, Ufuk On Fri, Feb 8, 2019 at 2:38 PM Fabian Hueske <fhue...@gmail.com> wrote: > > I like the idea of a roadmap that is kept up-to-date. > We've tried that in the past a couple of times but they became outdated > rather quickly. > We've also had a some threads on the dev mailing list to discuss the scope & > features of next releases. > > We could discuss and update the roadmap after every release (or even feature > freeze). > IMO, it would be good to have two things on in the document. > > * a long-term vision (~1 year) where the project is heading to > * a roadmap for the next release (~3 months) > > Cheers, Fabian > > Am Di., 5. Feb. 2019 um 16:55 Uhr schrieb Robert Metzger > <rmetz...@apache.org>: >> >> Hey Ufuk, >> >> I agree! We should have regular discussions here on the list for scoping >> releases, and then put this to the website. >> The Beam project has a pretty nice roadmap [1] available on their site. >> I actually don't really know if there's an agreed upon release schedule in >> the Flink community (I've not been following the dev@ list closely >> recently). >> I'll try to find somebody who knows a bit more about the recent Flink >> community developments to put together a first draft for such a roadmap. >> >> [1] https://beam.apache.org/roadmap/ >> >> On Mon, Feb 4, 2019 at 9:29 AM Ufuk Celebi <u...@apache.org> wrote: >> >> > Hey devs, >> > >> > I've been only following Flink dev loosely in the last couple of >> > months and could not find the following information: >> > >> > What's the schedule for the next release? In particular, when is the >> > planned feature freeze and when is the planned release date? >> > >> > I think this can be valuable information for both devs and users. What >> > do you think about adding this information to the Flink website? It >> > does not have to be exact dates, but general information such as "we >> > do time based releases every X months", "we support the last two minor >> > releases with patches", etc. I think this page [1] would be a good >> > target for this information. >> > >> > Best, >> > >> > Ufuk >> > >> > >> > [1] https://flink.apache.org/community.html >> >
