On 23 December 2013 05:50, David Crossley wrote:
> Marvin Humphrey wrote:
>> Greg Trasuk wrote:
>> >
>> > Thanks everyone for the input. To summarize, it appears that the consensus
>> > argument is:
>> >
>> > - Jar files are not prohibited by policy in project repositories (svn),
>> > although
Marvin Humphrey wrote:
> Greg Trasuk wrote:
> >
> > Thanks everyone for the input. To summarize, it appears that the consensus
> > argument is:
> >
> > - Jar files are not prohibited by policy in project repositories (svn),
> > although they may not make a lot of sense.
> > - Source distribution
On Fri, Dec 20, 2013 at 8:49 AM, Greg Trasuk wrote:
> Thanks everyone for the input. To summarize, it appears that the consensus
> argument is:
>
> - Jar files are not prohibited by policy in project repositories (svn),
> although they may not make a lot of sense.
> - Source distributions must
I am not an expert, we only graduated a year ago. But I think there are
two rules in here:
1) Source archive must not contain compiled source code that is part of
the product's functionality. There is leeway on compiled source code
processed during testing. I think the board may pull your relea
Thanks everyone for the input. To summarize, it appears that the consensus
argument is:
- Jar files are not prohibited by policy in project repositories (svn),
although they may not make a lot of sense.
- Source distributions must not distribute executable code in binary form.
i.e. Don’t shi
On Thu, Dec 19, 2013 at 10:40 AM, Henry Saputra wrote:
> So the point of concern is the "external" jars, but jars that are
> generated by the project itself (for example for tests) should be
> fine?
One main concern is oversight for what goes into an an Apache release.
It's not realistic to perf
On 19 December 2013 18:57, Alex Harui wrote:
> My understanding of the link I posted way back is that the source package
> cannot contain compiled output that will be executed by the customer.
> IMO, whether it is "external" or not doesn't matter. The JAR used by the
> Compress tests is hopefully
My understanding of the link I posted way back is that the source package
cannot contain compiled output that will be executed by the customer.
IMO, whether it is "external" or not doesn't matter. The JAR used by the
Compress tests is hopefully just data, not some part of its functionality.
On 12
Ah I see.
So the point of concern is the "external" jars, but jars that are
generated by the project itself (for example for tests) should be
fine?
- Henry
On Thu, Dec 19, 2013 at 10:34 AM, sebb wrote:
> On 19 December 2013 18:26, Henry Saputra wrote:
>> But at the end, when a podling prepare
On 19 December 2013 18:26, Henry Saputra wrote:
> But at the end, when a podling prepare a release there should not
> include jar files as part of the source release artifacts to be VOTED
> on, is this correct?
I think that depends on what the jar files are.
For example. Apache Commons Compress i
But at the end, when a podling prepare a release there should not
include jar files as part of the source release artifacts to be VOTED
on, is this correct?
- Henry
On Thu, Dec 19, 2013 at 9:21 AM, Marvin Humphrey wrote:
> On Wed, Dec 18, 2013 at 7:45 PM, Greg Trasuk wrote:
>> We’re having a di
On Wed, Dec 18, 2013 at 7:45 PM, Greg Trasuk wrote:
> We’re having a discussion over in d...@river.apache.org that was triggered by
> the recent discussion here about the Spark podling release.
The River discussions seem to be playing out productively. Here are links for
other people who may be
Some example of projects that have them in both the repo and source dist is
Apache Cassandra or Apache OpenOffice
-Jake
On Wed, Dec 18, 2013 at 11:01 PM, Joseph Schaefer wrote:
> No policy says anything about binaries in svn, but if you can't have them
> in your source package it probably doesn
No policy says anything about binaries in svn, but if you can't have them in
your source package it probably doesn't make much sense to keep them in svn.
But really that part is up to the project not the IPMC.
Sent from my iPhone
> On Dec 18, 2013, at 10:45 PM, Greg Trasuk wrote:
>
>
> Hi a
Hi all:
We’re having a discussion over in d...@river.apache.org that was triggered by
the recent discussion here about the Spark podling release. In particular,
http://mail-archives.apache.org/mod_mbox/incubator-general/201312.mbox/%3CCAAS6%3D7iQSKTgNdO-0Qyd3T9--%2B%2BHQFEmhJi7CHoByqvQvp9_bg%40
15 matches
Mail list logo