Hi, just've pushed some last commits and I'm uploading a snapshot right now. That would be enough for me to go for 2.11.0.M2. Most probably, I'll run the vote next Tuesday, in order to have some space for testing before the release vote and iron out any last minute bug.
cheers, juan pablo On Mon, Feb 18, 2019 at 8:00 PM Dirk Frederickx <dirk.frederi...@gmail.com> wrote: > Agree. I would be sensible to push out a release; to stabilise the template > upgrade. > > dirk > > On Mon, Feb 18, 2019 at 5:53 PM Harry Metske <harry.met...@gmail.com> > wrote: > > > JP, > > > > that would be fine I think. > > > > tx, > > Harry > > > > > > Op zo 17 feb. 2019 om 23:58 schreef Juan Pablo Santos Rodríguez < > > juanpablo.san...@gmail.com> > > > > > Hi, > > > > > > we've been some releases trying to adhere to a release train strategy, > > with > > > stops each quarter. Q4-2018 release had issues, so we > > > ended up releasing it on Jan, 29th, 2019. Given that, I felt that > > probably > > > made sense to skip February stop. > > > > > > However, given that there are a couple of fixes regarding the rename of > > the > > > haddock template to default, a new Dark appereance > > > mode for Haddock, enabled by default, and a few other fixes and > > > improvements, I think releasing 2.11.0.M2 on February would make > > > most sense. I'd only like to extract the util package to its own > > submodule, > > > which should be fairly easy, but other than that, that would > > > be for me if we release on Feb. > > > > > > WDYT? > > > > > > > > > br, > > > juan pablo > > > > > >
