I don't think that tagging on the source code/repo level is a problem as long as it is not announced as an Apache release or distributed under that name
But they can merely be used as a tagged version of source code which developers can use on their own responsibility Also I believe it is better to mention somewhere, maybe as a disclaimer file at the root of the tagged version [1], that this code does not represent an Apache release and it is only can be used on users/developers own responsibility [1] other mentors would you please correct in that matter if I am mistaken ? Sent from my Samdung Galaxy S3 Apologies for any typos On Jul 4, 2012 7:50 PM, "John Kinsella" <j...@stratosec.co> wrote: > Can we add git tags for the 3.0.0, 3.0.1, and 3.0.2 releases? I realize > they're not ASF-blessed releases, but would be very handy for when folks > want to grab a particular release from the repo. > > I think 3.0.0 is cf0a4e02743abb87b665ea585cb3cf1786c4d966? The zip file on > sf.net mentions bcc4833 but I don't see that as a rev. I haven't tracked > down the other two, yet. > > John >
