incubator-isis-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Haywood (JIRA)" <j...@apache.org>
Subject [jira] Updated: (ISIS-20) Get all components ready for a 0.1 release
Date Wed, 15 Dec 2010 11:21:03 GMT

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

Dan Haywood updated ISIS-20:
----------------------------

    Affects Version/s:     (was: 0.1.0-incubating)
        Fix Version/s: 0.1.0-incubating
             Assignee: Dan Haywood

> Get all components ready for a 0.1 release
> ------------------------------------------
>
>                 Key: ISIS-20
>                 URL: https://issues.apache.org/jira/browse/ISIS-20
>             Project: Isis
>          Issue Type: Task
>            Reporter: Dan Haywood
>            Assignee: Dan Haywood
>             Fix For: 0.1.0-incubating
>
>
> This is an umbrella JIRA ticket to get all modules relating to getting 0.1 ready for
release.
> For all code modules, we have a single subtask to address all of the following:
> 1 - docbook PDF is coherent (can have placeholders, but what is there should be correct
or with notes to indicate in what way it might not be)
> 2 - site APT is complete (can be brief)
> 3 - copyright notices are in place
> 4 - Isis code formatting applied to all code, per standard Eclipse IDE settings (in particular:
brace location, spaces instead of tabs, indent size)
>    - in trunk/src/site/resources/ide/eclipse/templates
> 5 - For the objectstores and viewers, should have a module in the support/prototype project
> There are also some miscellaneous other modules that require work; each of these has
its own subtask also.  Specifically:
> - isis-parent (site, contributors guide, screencasts)
> - archetype (to be reverse engineered from support/prototype)
> - version Id should be set to: 0.1.0-incubating-SNAPSHOT
> NB, the following have been addressed already for code modules, so haven't included in
the above list:
> - all package names and Maven artifact IDs (should now be correct)
> - all license dependencies (have all been checked)
> - all code contributions (have IP has been accounted for, ICLAs on file or equivalent
direct email confirmation for minor patches to NOF)

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