Re: Are tests part of the release?

2015-08-11 Thread Hendrik Dev
thanks for your feedback, i canceled the vote, we fixed the deps and startet a new vote. On Mon, Aug 10, 2015 at 3:45 PM, Bertrand Delacretaz bdelacre...@apache.org wrote: On Mon, Aug 10, 2015 at 11:11 AM, jan i j...@apache.org wrote: ...we do not have a demand that a release must contain a

Re: Are tests part of the release?

2015-08-10 Thread jan i
On 10 August 2015 at 10:33, Bertrand Delacretaz bdelacre...@apache.org wrote: On Sun, Aug 9, 2015 at 10:43 AM, Hendrik Dev hendrikde...@gmail.com wrote: ...We have (accidentally) a dependency to a snapshot version for a library but only in maven test scope... To me this means that release

Re: Are tests part of the release?

2015-08-10 Thread Bertrand Delacretaz
On Sun, Aug 9, 2015 at 10:43 AM, Hendrik Dev hendrikde...@gmail.com wrote: ...We have (accidentally) a dependency to a snapshot version for a library but only in maven test scope... To me this means that release is broken, if I cannot test it I cannot trust it. Not like Fully Absolutely

Re: Are tests part of the release?

2015-08-10 Thread Bertrand Delacretaz
On Mon, Aug 10, 2015 at 11:11 AM, jan i j...@apache.org wrote: ...we do not have a demand that a release must contain a test set, so if the release does not contain the test we cannot see it as broken, or ?... From the ASF's point of view you are correct, having tests in a release is not

Re: Are tests part of the release?

2015-08-09 Thread Romain Manni-Bucau
A tag should be buildable anytime. Snapshots can be dropped from repos so from my understanding it is an issue even if less impacting than direct binaries dependencies. Le 9 août 2015 02:05, Justin Mclean jus...@classsoftware.com a écrit : Hi, Are tests are part of the release

Re: Are tests part of the release?

2015-08-09 Thread Romain Manni-Bucau
, Are tests are part of the release? If they are included as source code in the released artefact yes :-) Background: We have (accidentally) a dependency to a snapshot version for a library but only in maven test scope. Up to the project I’d say, but I’d just raise a JIRA

Re: Are tests part of the release?

2015-08-09 Thread John D. Ament
direct binaries dependencies. Le 9 août 2015 02:05, Justin Mclean jus...@classsoftware.com a écrit : Hi, Are tests are part of the release? If they are included as source code in the released artefact yes :-) Background: We have (accidentally) a dependency to a snapshot version

Re: Are tests part of the release?

2015-08-09 Thread William A Rowe Jr
On Aug 9, 2015 4:05 AM, Justin Mclean jus...@classsoftware.com wrote: Hi, Are tests are part of the release? If they are included as source code in the released artefact yes :-) Well put. The Apache HTTP Server has several 'test' modules which are embedded in release tarballs. The 'test

Re: Are tests part of the release?

2015-08-09 Thread Roman Shaposhnik
On Sun, Aug 9, 2015 at 5:29 AM, Romain Manni-Bucau rmannibu...@gmail.com wrote: A tag should be buildable anytime. Snapshots can be dropped from repos so from my understanding it is an issue even if less impacting than direct binaries dependencies. To me the above is exactly the way to think

Are tests part of the release?

2015-08-09 Thread Hendrik Dev
Are tests are part of the release? Background: We have (accidentally) a dependency to a snapshot version for a library but only in maven test scope. Thanks Hendrik -- Hendrik Saly (salyh, hendrikdev22) @hendrikdev22 PGP: 0x22D7F6EC

Re: Are tests part of the release?

2015-08-09 Thread jan i
On 9 August 2015 at 10:43, Hendrik Dev hendrikde...@gmail.com wrote: Are tests are part of the release? It is not a mandatory part, the project defines the content of the release. I work with a.o. Corinthia, there we have some test cases that will not be released, but most will, for dependency

Re: Are tests part of the release?

2015-08-09 Thread Justin Mclean
Hi, Are tests are part of the release? If they are included as source code in the released artefact yes :-) Background: We have (accidentally) a dependency to a snapshot version for a library but only in maven test scope. Up to the project I’d say, but I’d just raise a JIRA and fix it next