You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Frank Bille Jensen (JIRA)" <ji...@apache.org> on 2007/12/06 19:56:52 UTC

[jira] Updated: (WICKET-662) Release process needs documenting

     [ https://issues.apache.org/jira/browse/WICKET-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Frank Bille Jensen updated WICKET-662:
--------------------------------------

    Fix Version/s:     (was: 1.3.0-rc2)
                   1.3.0-rc3

> Release process needs documenting
> ---------------------------------
>
>                 Key: WICKET-662
>                 URL: https://issues.apache.org/jira/browse/WICKET-662
>             Project: Wicket
>          Issue Type: Task
>          Components: site
>            Reporter: Alastair Maw
>            Assignee: Martijn Dashorst
>            Priority: Minor
>             Fix For: 1.3.0-rc3
>
>
> We could really do with having more than one person able to do a release.
> To that end, the release process could do with documenting. "Run release.sh" isn't quite sufficient here - we could do with some information about getting your PGP key signed by the Apache folk, or whatever is required for that, and what SSH karma, etc. is necessary to deploy things to the Maven 2 repo, and whatever else.
> Any chance you could scribble something on the wiki about this?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.