db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Assigned: (DERBY-4400) Document the process of producing Maven 2 artifacts for Derby
Date Wed, 25 Nov 2009 11:08:39 GMT

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

Kristian Waagan reassigned DERBY-4400:
--------------------------------------

    Assignee: Kristian Waagan

> Document the process of producing Maven 2 artifacts for Derby
> -------------------------------------------------------------
>
>                 Key: DERBY-4400
>                 URL: https://issues.apache.org/jira/browse/DERBY-4400
>             Project: Derby
>          Issue Type: Task
>          Components: Documentation
>    Affects Versions: 10.5.4.0, 10.6.0.0
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>         Attachments: derby-4400-1a-SetDerbyVersion.diff
>
>
> The process of producing Maven 2 artifacts for Derby should be documented.
> Good and clear documentation is important for the following reasons:
>  - The process is only carried out each time a Derby release is produced.
>  - A part of our users are using Maven in their projects, and they depend on the Maven
2 artifacts to upgrade Derby.
>  - It is likely that it isn't the same person carrying out the process from release to
release.
> As a rough starting point, some points to cover:
>  - Prerequisites, installation and environment setup.
>  - The artifact build process.
>  - Testing the artifacts.
>  - Deploying the artifacts.
>  - Verifying the deployment (with the central repository).

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


Mime
View raw message