What Andy's outlined below are pretty much the process and steps we have
been following for all the Mahout releases and for the first Pirk release
recently.
Again both Mahout and Pirk are all Maven and the relevant plugins and
profiles have been setup and configured to build, package, sign, push
a
Kam is checking in release candidate artifacts to dev staging SVN by hand
and then promoting them by hand, I believe.
Apache projects cannot "release on GitHub". Please review the release
policy documents we've provided links to in the past.
FWIW, here is the shorthand version of what I do to rel
On Tue, Sep 6, 2016 at 1:17 PM, Pat Ferrel wrote:
> Ok, if no other objections then we have no blockers for source release.
>
> There is a process to get the tar into Apache mirrors but to release on
> Github all we need to do it merge develop, wait for travis tests and tag
> the master. Github c
Ok, if no other objections then we have no blockers for source release.
There is a process to get the tar into Apache mirrors but to release on Github
all we need to do it merge develop, wait for travis tests and tag the master.
Github can be told to produce a source release tar and host it and
Agree we should go source only for this release.
On Sep 5, 2016 1:10 PM, "Suneel Marthi" wrote:
> On Mon, Sep 5, 2016 at 2:55 PM, Andrew Purtell
> wrote:
>
> > I also don't have experience with SBT, apologies. I did do some poking
> > around on Google and it looks like SBT is well behind Maven
On Mon, Sep 5, 2016 at 2:55 PM, Andrew Purtell
wrote:
> I also don't have experience with SBT, apologies. I did do some poking
> around on Google and it looks like SBT is well behind Maven in providing
> this type of functionality out of the box or by third party plugin
> (sbt-assembly does some
I also don't have experience with SBT, apologies. I did do some poking around
on Google and it looks like SBT is well behind Maven in providing this type of
functionality out of the box or by third party plugin (sbt-assembly does some
useful and interesting things but is focused exclusively on p
I agree with doing a source release now while gradually fixing a binary
release.
On Monday, September 5, 2016, Suneel Marthi wrote:
> Its easy to do what Andy is describing using maven's assembly plugin in the
> maven world. I have no experience with sbt so can't speak to how it can be
> done wi
Its easy to do what Andy is describing using maven's assembly plugin in the
maven world. I have no experience with sbt so can't speak to how it can be
done with Sbt and would defer that to the experts.
We hit a similar issue with licenses in source and binary on the first Pirk
release last week. W
It covers LICENSE and NOTICE file generation for both source and binary
releases, and inclusion of the resulting files in source archives, binary jars,
and binary archives through integration with the maven build and assembly
targets.
Including the complete text of any given license in LICENSE
In case we can automate LICENSE.txt creation I’d still rather not have it as a
blocker since the file is easy to update to reflect source releases and for
other reasons I listed I’m not sure if its value.
Removing binary-ready release as a blocker will give us time to automate
without the press
Thanks Andy.
RE “Only need to include one entry with the complete text of a license,
everything else can just name the license.” So the copyright notice in the
license is not important, only the license type? This is often the only
important difference in the license from one dep to another.
I won't weigh in on the question at hand but I'd like to make a couple of
clarifications for what it is worth:
> This yielded 166 deps, so this implies we need to include 166 licenses and
> copyright notices in LICENSE.txt.
There are some available simplifications:
- Only need to include one e
This weekend I tracked down all out deps, which required a few scripts to
process sbt output. This yielded 166 deps, so this implies we need to include
166 licenses and copyright notices in LICENSE.txt. As I read the Apache
guidelines this should be the license that goes with the version we incl
14 matches
Mail list logo
