Hi Guillaume, Do you know why maven-shared-utils has not been released yet? It sounds like a good idea to include this at least in the official 4.0.0 release, so I think it makes sense to include it in either this alpha release or perhaps a next one. I'm not familiar with the jansi changes or the status of maven-shared-utils though, maybe others who are can chime in.
Martin Op ma 12 apr. 2021 om 11:13 schreef Guillaume Nodet <gno...@apache.org>: > Would it be possible to include all the jansi related issues ? That > requires a release of maven-shared-utils > MNG-7080, MNG-7079, MNG-6719, MNG-6239, MNG-6755, MNG-6380, MNG-6915 > I'm willing to help, but all the PRs are kinda blocked because of the need > for a maven-shared-utils release, so they include a snapshot dependency and > obviously fail the tests... > > Guillaume > > > Le lun. 12 avr. 2021 à 09:06, Martin Kanters <martinkant...@apache.org> a > écrit : > >> Great to see the enthusiasm. I also expected more work to be done for this >> release, but apparently that's not the case (if we aren't missing >> something >> else). >> >> As Romain is saying, I think we should put some work into documenting. At >> least some of the new changes. Maarten Mulders and I are working on >> documenting all reactor changes, listed under MNGSITE-444 [1]. Have we >> documented other big features, like the Maven Wrapper and Build/Consumer >> POM already? If not, should we make tickets for it? Also, not sure whether >> this is required for alpha-1. >> >> Regarding MNG-6772 / MNG-6397 / MRESOLVER-168, I think we can either try >> to >> include all in this release, or make that part of alpha-2. I'm unfamiliar >> with the consequences, so I'll let you decide that ;) Let me know if I can >> help. >> >> Regards, >> Martin >> >> [1] https://issues.apache.org/jira/browse/MNGSITE-444 >> >> Op zo 11 apr. 2021 om 20:07 schreef Romain Manni-Bucau < >> rmannibu...@gmail.com>: >> >> > +1, I just suspect we should be clear on the status of this alpha >> (unstable >> > and unexpected to hit CI for ex) and breaking changes which can break >> again >> > in final potentially (this is what generally upset people with >> alpha/beta >> > and prevent their usage in later versions). In any case having some >> preview >> > is generally always worth it before ;). >> > >> > 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 dim. 11 avr. 2021 à 17:59, Michael Osipov <micha...@apache.org> a >> > écrit : >> > >> > > Attention: MNG-6772 is already on master and Robert and me have >> decided >> > > to reopen it to give it more thought. It must be reverted from master >> > > first before you cut a release until we have decided how to procede >> with >> > > this as well as related MNG-6397. >> > > >> > > Except that I see no reason not to continue with alpha-1. I am certain >> > > that this is a good release, but we will require more rounds of it. >> > > >> > > Michael >> > > >> > > Am 2021-04-11 um 17:32 schrieb Hervé BOUTEMY: >> > > > cutting 4.0.0-alpha release: very good idea!!! >> > > > >> > > > on the 3 issues, I can tell that MNG-6397 is a long standing issue >> that >> > > looks >> > > > relevant (caused by MNG-6772 [1] that better describes it) >> > > > >> > > > But I don't see why this particular issue is an absolute must for >> > > 4.0.0-alpha: >> > > > I would propose to mark it for 4.0.x-candidate >> > > > >> > > > >> > > > And I'm interested in people wanting to help on it (in a separate >> > > thread). >> > > > >> > > > >> > > > on the question of cutting the first alpha release, shouldn't we >> > include >> > > Maven >> > > > Resolver 1.7.0? It would help to have MRESOLVER-168 to work on >> > > MNG-6772... >> > > > >> > > > Regards, >> > > > >> > > > Hervé >> > > > >> > > > >> > > > [1] https://issues.apache.org/jira/browse/MNG-6772 >> > > > >> > > > Le dimanche 11 avril 2021, 16:19:49 CEST Martin Kanters a écrit : >> > > >> Hi all, >> > > >> >> > > >> I am wondering if we have a good idea of what we want to have >> finished >> > > >> before cutting the first 4.0.0-alpha release. >> > > >> I would love to work towards the actual release, and thus am >> wondering >> > > >> whether there's a list of issues we can finish. >> > > >> When selecting all unresolved issues targeted for 4.0.0-alpha-1, >> JIRA >> > > comes >> > > >> up with just 3 issues, which I'm not sure if they are still >> relevant. >> > > [1] >> > > >> I guess there might be more we need to include in the version, but >> > > that's >> > > >> unknown to me. >> > > >> >> > > >> Thanks, >> > > >> Martin >> > > >> >> > > >> [1] >> > > >> >> > > >> > >> https://issues.apache.org/jira/issues/?filter=-5&jql=project%20%3D%20MNG%20A >> > > >> >> > > >> > >> ND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%204.0.0-alpha-1% >> > > >> 20order%20by%20priority%20DESC%2Cupdated%20DESC >> > > > >> > > > >> > > > >> > > > >> > > > >> > > > >> --------------------------------------------------------------------- >> > > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> > > > For additional commands, e-mail: dev-h...@maven.apache.org >> > > > >> > > >> > > >> > > >> > > --------------------------------------------------------------------- >> > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org >> > > For additional commands, e-mail: dev-h...@maven.apache.org >> > > >> > > >> > >> > > > -- > ------------------------ > Guillaume Nodet > >
