I think that our first release should be a 'complete' one, including the
binary artifacts, but I don't think that it has to be the most pristine on
the L&N front as long as we meet the ASF L&N requirements (which, as far as
I can tell, is far more than most Apache projects ;)). We can make the
'cleanup L&N placement' a task for release #(1 + n) where n is small. This
seems to go hand-in-hand with a submodule refactor which won't happen for
this release... (please correct me if you think that we can clean the L&N
situation without the submodule refactor)

Please see the specific comment that I sent a few minutes ago.

Thanks!


On Fri, Aug 19, 2016 at 11:16 AM, Suneel Marthi <[email protected]>
wrote:

> On Fri, Aug 19, 2016 at 11:13 AM, Tim Ellison <[email protected]>
> wrote:
>
> > On 19/08/16 15:53, Suneel Marthi wrote:
> > > On Fri, Aug 19, 2016 at 10:13 AM, Tim Ellison <[email protected]>
> > wrote:
> > <snip>
> > >> I'd appreciate other mentors' close review of these built artefacts
> too.
> > >>
> > >> Seems that the main project source release looks good, but the
> > >> convenience JARs still needs some filtering/moving work.
> > >
> > > Anything else you can think of. Not sure how much of this can be
> > addressed
> > > in this release. Its best to acknowledge the remaining license issues
> > that
> > > need to be addressed and move forward with cutting a release.
> > >
> > > There just doesn't seem a clean way to get all of this straightened out
> > for
> > > the very first release, its possible that the way we are packaging the
> > > artifacts now may not be the right way and we need to do it
> differently,
> > > something that we had not considered or talked about so far.
> >
> > The main release artefact (apache-pirk-0.0.2-source-release.zip) is
> > looking good.  I think there is a good argument to publish this as the
> > first project release, and work on the convenience binaries to be
> > included with the next release.
> >
>
> I can confirm that the logs/ are being packaged into the sources.zip and
> need to be excluded when building that artifact. I'll take a stab at this.
>
>
> >
> > It may be that the content of the next release is primarily the
> > inclusion of the convenience binaries, and it happens within a few
> > weeks.  I don't see a problem with that.
> >
> > However, Ellison Anne was up for tackling the L&N's this time around, so
> > I'm not going to stand in the way of that.  There's no rush.
> >
> > Regards,
> > Tim
> >
> >
>

Reply via email to