Lucene seems to use SHA1 to create a binary format of junit which is OK to
include in source releases. Not exactly sure how they encrypt/decrypt it
yet but i'm still poking around...
Thanks
Angus Turner
angusisf...@gmail.com
On Sat, Sep 15, 2012 at 1:50 AM, Upayavira wrote:
> Look at a few othe
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/7077/
---
(Updated Sept. 14, 2012, 9:45 p.m.)
Review request for wave.
Changes
---
Hi,
On Fri, Sep 14, 2012 at 8:25 PM, Upayavira wrote:
> I have been pointing out that the ability to release correctly is what
> the incubator PMC wants to see, rather than a technically valid or
> useful release. That said, a release that is full of holes might
> actually have the counter-intuit
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/7077/#review11560
---
Ship it!
Thanks.
There are still a few spaces left floating, but we
This is precisely what is currently being discussed. In fact, we have a
new volunteer (Angus Turner) who is helping get things in order, with
large header correcting patches.
I have been pointing out that the ability to release correctly is what
the incubator PMC wants to see, rather than a techni
Look at a few other projects, e.g. Lucene, and see what they do
regarding tests.
Upayavira
On Fri, Sep 14, 2012, at 09:13 AM, Ali Lown wrote:
> Angus,
>
> In a source release where the receiver is expected to build the code
> themselves, the tests would be expected to ensure that their build
>
Is there anything that could be released, even in alpha/beta form? Code
completeness or maturity is not a barrier to graduation so long as the
community can demonstrate an understanding of the Apache release process. IMO,
it is best to get early, alpha releases out on a regular basis. You don
On Fri, Sep 14, 2012 at 11:04 AM, Angus Turner wrote:
> So I guess the easiest solution would be to move junit, emma and libidn out
> of our source, and instead set up ant to download them at build time?
> That's reaching the limits of my java-fu so if there's anyone that can
> spare what i assume
So I guess the easiest solution would be to move junit, emma and libidn out
of our source, and instead set up ant to download them at build time?
That's reaching the limits of my java-fu so if there's anyone that can
spare what i assume is only a quick job that'd be excellent.
I guess the question
On 13 September 2012 07:23, Angus Turner wrote:
> We have some licensing issues that are preventing us from going ahead
> with the release:
> -junit and emma both use the common public license, which isn't
> compatible with the apache one
The Apache Foundation's list of resolved legal questions s
Angus,
In a source release where the receiver is expected to build the code
themselves, the tests would be expected to ensure that their build
works correctly.
In a binary release, we wouldn't need to ship the tests.
Ali
On 14 September 2012 09:03, Angus Turner wrote:
> Hey all,
> I was thinkin
Sounds good - in regards to the two points you mention:
1) XML/DOM model is found in model/document; see e.g.
https://svn.apache.org/repos/asf/incubator/wave/trunk/src/org/waveprotocol/wave/model/document/MutableDocument.java
or model/document/raw/RawDocument for examples of what you can access.
(p
12 matches
Mail list logo
