jackrabbit-oak-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jukka Zitting (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Edited] (OAK-44) Release managements tweaks
Date Mon, 30 Apr 2012 11:02:48 GMT

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

Jukka Zitting edited comment on OAK-44 at 4/30/12 11:01 AM:
------------------------------------------------------------

bq. can we also tweak the release tag settings?

I'd actually rather stick with the default settings as much as possible (convention over configuration,
etc.).

The reason why Jackrabbit 2.x uses different tag names is that we came up with that convention
way before the Maven release plugin existed. But for any new codebases like Oak I think it's
better to stick with the new standard conventions as codified in the release plugin.

PS. I adjusted the vote email template to use the correct tag URL in revision 1332152.
                
      was (Author: jukkaz):
    bg. can we also tweak the release tag settings?

I'd actually rather stick with the default settings as much as possible (convention over configuration,
etc.).

The reason why Jackrabbit 2.x uses different tag names is that we came up with that convention
way before the Maven release plugin existed. But for any new codebases like Oak I think it's
better to stick with the new standard conventions as codified in the release plugin.
                  
> Release managements tweaks
> --------------------------
>
>                 Key: OAK-44
>                 URL: https://issues.apache.org/jira/browse/OAK-44
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>            Reporter: Alex Parvulescu
>            Assignee: Alex Parvulescu
>            Priority: Minor
>             Fix For: 0.2
>
>
> There are still some minor things to be tweaked for the next release:
>  - change the TO field in the email template to point to oak-dev@jackrabbit.apache.org
>  - change scp -r ${basedir}/target/${project.version} people.apache.org:public_html/oak/
to scp -r ${basedir}/target/${project.version} ${username}@people.apache.org:public_html/oak/
>  - add 'pedantic' profile for the verification script.
> Now there a warning: [WARNING] The requested profile "pedantic" could not be activated
because it does not exist.
>  - tweak ${username} value: maybe rename to apache.username, and document how we can
set it in maven settings.xml file in the cases where the local username is not the same as
the apache username.
> feel free to add more ideas here.

--
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

        

Mime
View raw message