[ 
https://issues.apache.org/jira/browse/LUCENE-3964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248434#comment-13248434
 ] 

Steven Rowe commented on LUCENE-3964:
-------------------------------------

bq. Confused about the component: build.

Feel free to change it to a more appropriate component (not sure what that 
would be).

bq. I certainily hope the build need not be changed to do this (certainly not 
for 3.6)

No, it does not.  As I mentioned in my previous post on this issue, the patch 
is against trunk, and it works against your 3.6.0 RC0 (Lucene only at this 
point; Solr still needs to be tested.)

bq. I think we should generate an RC like we do now, putting it on p.a.o, vote 
on it, and this is merely a deployment issue.

+1

bq. If there are any scripts involved in this, i think they should go in 
dev-tools instead, (like other release deployment scripts)?

Yup, that's what I've done.

This is a work in progress - please review if you're interested!
                
> Stage Maven release artifacts
> -----------------------------
>
>                 Key: LUCENE-3964
>                 URL: https://issues.apache.org/jira/browse/LUCENE-3964
>             Project: Lucene - Java
>          Issue Type: New Feature
>          Components: general/build
>    Affects Versions: 3.6, 4.0
>            Reporter: Steven Rowe
>            Assignee: Steven Rowe
>            Priority: Critical
>             Fix For: 3.6, 4.0
>
>         Attachments: LUCENE-3964.patch
>
>
> We need a way to stage Maven artifacts to the Apache release repository.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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]

Reply via email to