Re: [VOTE] Release Apache Maven Dependency Analyzer version 1.11.2
By my count we need one more PMC member to approve this to get to
three. This is an important upgrade that enables lots of new work in
the dependency plugin. Can anyone else give us a +1? Thanks.
On Fri, Jul 24, 2020 at 2:43 PM Benson Margulies <[hidden email]> wrote:
> +1 binding.
> On Thu, Jul 23, 2020 at 5:39 PM Eric Lilja <[hidden email]> wrote:
> > On Fri, Jul 24, 2020 at 12:06 AM Sylwester Lachiewicz <
> > [hidden email]>
> > wrote:
> > > +1
> > >
> > > in fact, in this release, based on commits, we have also fixed:
> > > MSHARED-879 Reproducible builds
> > > MSHARED-810 Support for Java 12
> > > MSHARED-792 Maven Dependency Analyzer ignores Java 8 type annotations on
> > > local variables
> > >
> > > All the above tasks was assigned to the next planned version 3.0, now all
> > > fix tags where corrected.
> > Vote: +1 non-binding
> > Thanks for highlighting this, Sylwester. I think we have the same situation
> > in maven-site-plugin (and maybe elsewhere). Issues fixed without a fix
> > version. I usually look at the next version in Jira to see what issues are
> > already completed to make it into the next release and what other,
> > non-completed issues, also share the same fix version (I know some
> > components have several future versions, which may have their own
> > issues, like Maven itself, or surefire, but most do not is my experience).
> > I would like to track all changes in Jira, including dependency upgrades
> > and would like all pull requests to have corresponding jira issue with a
> > fix version so it's easy to track progress and see as complete as possible
> > release notes. Maybe the WoW around this needs to be aligned a bit more
> > among the developers in the Maven dev community.
> > - Eric L