johnzon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Romain Manni-Bucau <rmannibu...@gmail.com>
Subject Re: [VOTE] Release Apache Johnzon 1.2.1
Date Thu, 03 Oct 2019 06:39:38 GMT
my own +1

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 lun. 30 sept. 2019 à 15:36, Justin Mclean <justin@classsoftware.com> a
écrit :

> Hi,
>
> > We tend to bypass dev dist area for nexus based releases since we grab
> the
> > artifact from nexus so it is as error prone to set up the dev dist area
>
> I guess it OK as long at it ends up on
> https://dist.apache.org/repos/dist/release/johnzon/
>
> > than not doing it for such releases and at the end the important part is
> to
> > synchronize the prod area and not the dev one
>
> You can publish via a svn mv so syncing is easy.
>
> > Fiexd the header and NOTICE year for next release - header was just my
> > default template in my IDE but was not intended to be pushed like that,
> not
> > a big deal for the release. Thanks a lot to have caught it!
>
> Yes a trivial issue, thanks for fixing.
>
> > About Joni, you are right, it is a dependency and we don't bundle it in
> > sources but some usage requires end user to import it, thought it was
> saner
> > to keep it mentionned here but happy to drop it for next release too if
> > everybody agrees.
>
> Having extra stuff in LICENSE is just a documentation issue not a
> licensing issue so it’s not a big deal.
>
> Thanks,
> Justin
>
>
> 1. https://www.apache.org/dev/release-distribution#public-distribution

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message