[
https://issues.apache.org/jira/browse/SOLR-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13565719#comment-13565719
]
Roman Shaposhnik commented on SOLR-4377:
----------------------------------------
bq. I'm not sure that is the case. I think it comes down to the PMC for a
particular project and what they decide to release.
Well, as an IPMC member I can tell you that this is something we strongly
required from the poddling release. Perhaps you're right and somehow the TLPs
are exempt from this requirement. I'd be happy to solicit the advice of ASF
long timers if for nothing else but to make sure we treat poddling the same way
we are going to treat them when they graduate.
> 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
> 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]
