BTW on our github readme, the latest version in Maven is displayed as 2.5.0, while 2.7.0 was published. This could be an image caching issue. But instead of showing something incorrect, maybe rather remove, unless it can be fixed?
On Tue, Oct 9, 2018 at 9:13 AM Thomas Weise <t...@apache.org> wrote: > Announcement was sent: > https://lists.apache.org/thread.html/b970a49a59fe97754eb6483823cca78e7208f17ae486bc959ee28e25@%3Cdev.beam.apache.org%3E > > I did not check other release finalization steps, is the tag not automated? > > > On Tue, Oct 9, 2018 at 9:06 AM Jean-Baptiste Onofré <j...@nanthrax.net> > wrote: > >> Hi guys, >> >> it seems the latest steps to finalize the 2.7.0 release have to be >> performed. >> >> Can I create the 2.7.0 git tag based on the RC3 one ? >> >> About the announcement, is someone planning to tackle that ? >> >> Thanks ! >> Regards >> JB >> -- >> Jean-Baptiste Onofré >> jbono...@apache.org >> http://blog.nanthrax.net >> Talend - http://www.talend.com >> >
