[
https://issues.apache.org/jira/browse/LUCENE-4134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13550406#comment-13550406
]
Robert Muir commented on LUCENE-4134:
-------------------------------------
personally i would prefer if we don't have a separate script for changing the
maven files.
I'm not really sure what this tester is currently doing: but in my opinion if
someone gets
"Lucene 4.1" i should know WTF they got, regardless of whether its from an FTP
site or maven.
So if it doesnt exist now, at least in the future I'd like more logic
cross-checking between
the two things to ensure they are consistent with each other.
Its scary to me that different build systems are producing different artifacts
and we don't
have this today.
And i know the checking isn't good enough when i see basic shit like things not
even named
the same way: SOLR-4287
> modify release process/scripts to use svn for rc/release publishing
> (svnpubsub)
> -------------------------------------------------------------------------------
>
> Key: LUCENE-4134
> URL: https://issues.apache.org/jira/browse/LUCENE-4134
> Project: Lucene - Core
> Issue Type: Task
> Reporter: Hoss Man
> Priority: Blocker
> Fix For: 4.1
>
>
> By the end of 2012, all of www.apache.org *INCLUDING THE DIST DIR* must be
> entirely managed using "svnpubsub" ... our use of the Apache CMS for
> lucene.apache.org puts us in compliance for our main website, but the dist
> dir use for publishing release artifacts also needs to be manaved via svn.
--
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]
