You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@isis.apache.org by "Dan Haywood (JIRA)" <ji...@apache.org> on 2010/12/15 12:21:03 UTC
[jira] Created: (ISIS-20) Get all components ready for a 0.1
release
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.
[jira] Updated: (ISIS-20) Get all components ready for a 0.1
release
Posted by "Dan Haywood (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ISIS-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Haywood updated ISIS-20:
----------------------------
Component/s: isis-parent (build plugins + site)
> 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
> Components: isis-parent (build plugins + site)
> 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.
[jira] [Closed] (ISIS-20) Get all components ready for a 0.1
release
Posted by "Dan Haywood (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ISIS-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Haywood closed ISIS-20.
---------------------------
> 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
> Components: isis-parent (build plugins + site)
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Fix For: 0.1.2-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
> 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/quickstart)
> - version Id should be set to: 0.1.1-incubating-SNAPSHOT
> - screencasts linked from site
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (ISIS-20) Get all components ready for a 0.1
release
Posted by "Dan Haywood (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ISIS-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Haywood updated ISIS-20:
----------------------------
Due Date: 15/Jan/11 (was: 15/Jan/11)
Description:
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
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/quickstart)
- version Id should be set to: 0.1.1-incubating-SNAPSHOT
- screencasts linked from site
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)
was:
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)
> 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
> Components: isis-parent (build plugins + site)
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Fix For: 0.1.1-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
> 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/quickstart)
> - version Id should be set to: 0.1.1-incubating-SNAPSHOT
> - screencasts linked from site
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (ISIS-20) Get all components ready for a 0.1
release
Posted by "Dan Haywood (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/ISIS-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dan Haywood resolved ISIS-20.
-----------------------------
Resolution: Fixed
> 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
> Components: isis-parent (build plugins + site)
> Reporter: Dan Haywood
> Assignee: Dan Haywood
> Fix For: 0.1.2-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
> 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/quickstart)
> - version Id should be set to: 0.1.1-incubating-SNAPSHOT
> - screencasts linked from site
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (ISIS-20) Get all components ready for a 0.1
release
Posted by "Dan Haywood (JIRA)" <ji...@apache.org>.
[ 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.