Mailing-List: contact isis-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: isis-dev@incubator.apache.org
Message-ID: <9619403.133311292412063225.JavaMail.jira@thor>
Date: Wed, 15 Dec 2010 06:21:03 -0500 (EST)
From: "Dan Haywood (JIRA)" <jira@apache.org>
To: isis-dev@incubator.apache.org
Subject: [jira] Created: (ISIS-20) Get all components ready for a 0.1
 release
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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
    Affects Versions: 0.1.0-incubating
            Reporter: Dan Haywood


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.