[
https://issues.apache.org/jira/browse/SOLR-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13565897#comment-13565897
]
Steve Rowe commented on SOLR-4377:
----------------------------------
I'm not sure why .gitignore and .hgignore aren't present, but I'd argue that
they have no point in a source tarball outside of a VC system.
All of the other difference (except for svn $URL$ keyword expansion differences
as a result of branch vs. tag location) appear to be intentional - see [the
package-src-tgz target in
{{solr/build.xml}}|http://svn.apache.org/viewvc/lucene/dev/trunk/solr/build.xml?view=markup#l382].
> making release tarballs identical to the release tags
> -----------------------------------------------------
>
> Key: SOLR-4377
> URL: https://issues.apache.org/jira/browse/SOLR-4377
> Project: Solr
> Issue Type: Improvement
> Components: scripts and tools
> Affects Versions: 4.0, 4.1
> Reporter: Roman Shaposhnik
> Fix For: 4.2, 5.0
>
> Attachments: diff.txt
>
>
> Now that we're integrating Solr with Hadoop via the Apache Bigtop project it
> is a bit of a nuisance to our build system that the release tarballs don't
> quite match the SVN tags. This is also something that is not quite ASF kosher
> strictly speaking.
> Would it be ok with a Solr community to add a comparison check between
> release tarballs and SVN tags as part of the release process checklist?
> If you guys have a Wiki outlining how-to-release perhaps it needs to be
> captured over there or just added to the process. Either way would be fine.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
