You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Michael McCandless (JIRA)" <ji...@apache.org> on 2016/02/11 17:41:18 UTC
[jira] [Created] (LUCENE-7022) smokeTestRelease.py should confirm
the git revision is "recognized"
Michael McCandless created LUCENE-7022:
------------------------------------------
Summary: smokeTestRelease.py should confirm the git revision is "recognized"
Key: LUCENE-7022
URL: https://issues.apache.org/jira/browse/LUCENE-7022
Project: Lucene - Core
Issue Type: Bug
Reporter: Michael McCandless
Spinoff from LUCENE-7021, but this issue aims to catch release bits built on unpushed changes in the smoke tester, by having it verify that the revision the bits were built from (stored in the JAR's META-INF) is in fact pushed to the public Apache git repository (git-wip-us.apache.org/repos/asf/lucene-solr.git).
This seems very important, since a git newbie like myself could easily mess something up and somehow push a release containing local (not pushed) commits that I then lose when deleting my local clone.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org