Hi Folks,
Thank you to everyone that replied here. Some excellent guidance which I
appreciate.
In resolution, we made the upgrade in Any23
https://issues.apache.org/jira/browse/ANY23-264
I think we will most likely drop the release candidate, spin a new one and get
back to VOTE'ing.
Thank you
Le
+1 to what Luciano says below.
-Bertrand
On Thu, Feb 8, 2018 at 9:04 PM, Luciano Resende wrote:
> ...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...
> ..
Hi Lewis,
Did you build the snapshot jar yourself? If not, where did you get
it? Are you bundling the compiled jar with your distribution?
It would be much better to either upgrade to a released version (the
best alternative) or if that is too painful, grab the sources,
repackage them and incor
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 appro
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 pl
