[
https://issues.apache.org/jira/browse/SOLR-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13565949#comment-13565949
]
Steve Rowe commented on SOLR-4377:
----------------------------------
@Mark:
bq. I saw that right after the 4.1 tag, a couple quick commits went in - one
for a spell fix in CHANGES and one a build issue - it made me unsure about
whether we had released the tag, or a rev with the two fixes that happened
right after. Of course I suspect we released the tag, but an automated smoke
test would make me feel better about trusting that.
After I created the RC, I made those commits to the branch anticipating another
RC, but I tagged the revision the RC was built from, so those commits aren't
included there.
The {{dev-tools/scripts/buildAndPushRelease.py}} script creates the trailing
dir name in the release staging RC URL (e.g.
http://people.apache.org/~sarowe/staging_area/lucene-solr-4.1.0-RC1-rev1434440/),
including the SVN revision, supplied by the {{svnversion}} program. You can
manually verify that the tag revision and the RC revision match once the tag
has been created.
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
