community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Luciano Resende <>
Subject Re: Issues with hosting unpublished SNAPSHOT then using it in a release candidate
Date Thu, 08 Feb 2018 20:04:34 GMT
SNAPSHOTS can be modified (overridden by a new version of the snapshot or
deleted) and will break the following release policy rule:

'Every ASF release MUST contain one or more source packages, which MUST be
sufficient for a user to build and test the release provided they have
access to the appropriate platform and tools.'

If you are maintaining your own SNAPSHOT of a given project (e.g.
commons-csv) and assuming they are not going to perform a release, you
might be better performing a release yourself (Any23) which is not perfect
but I have seen other projects doing it (e.g.

Having said that, I would really try to discuss with commons-csv if they
could help and accept your changes and perform a release.


On Thu, Feb 8, 2018 at 10:26 AM, lewis john mcgibbney <>

> Hi Folks,
> Over at Any23 [0], we have, for some time, been depending upon an old
> SNAPSHOT of commons-csv which we host in SVN [1] and utilize in our POM
> [2].
> During a recent review process for our 2.2 release candidate, it was
> pointed out that there may be an issue with this practice.
> Can someone please point me towards documentation on this practice such
> that we can determine if we need to fix the issue or if we can release the
> candidate then fix for the next release?
> Thank you kindly,
> Lewis
> [0]
> [1]
> [2]
> --

Luciano Resende

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message