+1 First step is to walk through our jira issues for the release. Check if some are implemented but not yet set to fixed in Jira. Then move the rest to the next release version. Go to release notes and copy those to our readme.txt
Sent with autocorrect... > On 17.10.2018, at 16:24, Romain Manni-Bucau <rmannibu...@gmail.com> wrote: > > Sounds like it can be the moment to pass another step? ;) > > Romain Manni-Bucau > @rmannibucau <https://twitter.com/rmannibucau> | Blog > <https://rmannibucau.metawerx.net/> | Old Blog > <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book > <https://www.packtpub.com/application-development/java-ee-8-high-performance> > > > Le mer. 17 oct. 2018 à 15:45, Thomas Andraschko <andraschko.tho...@gmail.com> > a écrit : > >> Weekend is of course ok :) >> Would be really great if you could trigger it, still didn't had the change >> to do a apache release :D >> >> Am Mi., 17. Okt. 2018 um 15:40 Uhr schrieb Mark Struberg >> <strub...@yahoo.de.invalid>: >> >>> sure we can. Just slightly offline due to travelling to GeeCon in Prague >>> right now. >>> Probably do a release on the weekend? >>> >>> LieGrue, >>> strub >>> >>>> Am 17.10.2018 um 15:21 schrieb Thomas Andraschko < >>> andraschko.tho...@gmail.com>: >>>> >>>> Hi Mark, >>>> >>>> WDYT about releasing 2.0.8? >>>> We have 2 good performance improvements, ASM7 update and some bug >> fixes. >>>> I think it's not a bad time for a release + we can push the new release >>> to >>>> TomEE? >>>> >>>> TomEE-M1 + 2.0.8 improves the startup of TomEE, compared to the TomEE >>>> SNAPSHOT last week, up to ~2,5 seconds. >>>> >>>> Best regards, >>>> Thomas >>> >>> >>
