[ http://issues.apache.org/jira/browse/JS2-153?page=all ]
Ate Douma updated JS2-153:
--------------------------
Summary: 2.0-M1 release planning - features to include (was: J2
release planning - features to include)
Fix Version: (was: 2.0-FINAL)
Description:
Yesterday night (or very, very early in the morning, depending on the person
involved) we had an IRC meeting about the upcoming release(s).
Several subjects were discussed (a log of the discussion will also be made
available) and one of it was the features which should be in the release.
It was decided to create an issue in JIRA (this one) to collect all these
features. All are invited to contribute.
After completion of this (initial) list, one big Vote request for all the items
will be presented on the developers mailing list.
For each feature a vote for inclusion in the upcoming M1 release or inclusion
in the FINAL release will then be requested:
<item>
part of M1 :
part of FINAL:
For each item voted in, we will of course need someone to step in for
realization.
Without proper commitment the item will have to be dropped off the feature list
eventually.
For each of these items an issue will be created in JIRA (if not there
already). The developer assigned should then make some prediction when it
can/will be ready by filling in the Due Date field.
Based on that information we can get a first idea when the related release
might be possible.
To be clear: signing up for a feature and predicting a date when its due,
doesn't implicate any obligation to do so, in accordance with the Apache
policy. But it will help use get a better picture of what to do and to expect.
Furthermore, this initial list of voted in features is not a closed or final.
Item may be dropped or postponed and new items may be added. At least, with
enough support.
I kindly ask everyone to be careful with proposing new features and with voting
them in. If we want a release as soon as possible (but no sooner), we should
try to restrain ourselves to must have features alone or mostly. Better to have
a limited initial version and quickly crank out additional features in short
release cycles than an endless postponed one.
Because we are planning to have a second IRC meeting next Monday (9 GMT again)
it would be nice if everyone could have its requested features added to this
list by then. During the meeting we will discuss the list further and hopefully
put out a Vote request real soon.
An initial feature list was already prepared by David Sean Taylor, and a few
others were proposed during the IRC meeting.
These features are:
* Close Open Issues (Bugs)
* Portal CSS
- consistency to all admin portlets
- use css from style.tigris.org as PLT.C styles
* Cleanup and Reorganize the demo portal
-- add help to all admin portlets
-- remove old portlets that are simple programmer tests
-- move portlet applications to tlp
* Portlet Selector for the customizer
* User Admin Portlets (JS2-121)
-- Add/Remove Users, Filter Users
-- maintainance for roles, groups
* Site Manager
-- add/edit/remove folders, pages, links, metadata
-- import/export
-- integrate customizer
-- global site settings from edit mode
* Web Content Component
* JCMS backend for Page Manager
* SSO
* Secure Access to Site Resources (JS2-111)
-- Pages, Folders, Navigations
-- Portlets
-- Windows
* Documentation (JS2-83)
* JMX Component Configurator Portlet
* Portlets
-- HTML
-- DB Browser
-- Web Services (Stock Quote)
-- XSLT
-- RSS
* Bridges
-- Velocity Bridge
-- PHP Bridge
-- Perl (?)
* Enhanced credential security and validation (JS2-151)
* TCK compliance
* Dhtml horizontal menu with pulldown submenus for navigation
-- support for grouped pages/folders/documentSets
-- possibly based on JCookMenu
* Page decoration configuration defining allowable actions
including none
* Fixing Portlet info, resourcebundle and LanguageSet storage
was:
Yesterday night (or very, very early in the morning, depending on the person
involved) we had an IRC meeting about the upcoming release(s).
Several subjects were discussed (a log of the discussion will also be made
available) and one of it was the features which should be in the release.
It was decided to create an issue in JIRA (this one) to collect all these
features. All are invited to contribute.
After completion of this (initial) list, one big Vote request for all the items
will be presented on the developers mailing list.
For each feature a vote for inclusion in the upcoming M1 release or inclusion
in the FINAL release will then be requested:
<item>
part of M1 :
part of FINAL:
For each item voted in, we will of course need someone to step in for
realization.
Without proper commitment the item will have to be dropped off the feature list
eventually.
For each of these items an issue will be created in JIRA (if not there
already). The developer assigned should then make some prediction when it
can/will be ready by filling in the Due Date field.
Based on that information we can get a first idea when the related release
might be possible.
To be clear: signing up for a feature and predicting a date when its due,
doesn't implicate any obligation to do so, in accordance with the Apache
policy. But it will help use get a better picture of what to do and to expect.
Furthermore, this initial list of voted in features is not a closed or final.
Item may be dropped or postponed and new items may be added. At least, with
enough support.
I kindly ask everyone to be careful with proposing new features and with voting
them in. If we want a release as soon as possible (but no sooner), we should
try to restrain ourselves to must have features alone or mostly. Better to have
a limited initial version and quickly crank out additional features in short
release cycles than an endless postponed one.
Because we are planning to have a second IRC meeting next Monday (9 GMT again)
it would be nice if everyone could have its requested features added to this
list by then. During the meeting we will discuss the list further and hopefully
put out a Vote request real soon.
An initial feature list was already prepared by David Sean Taylor, and a few
others were proposed during the IRC meeting.
These features are:
* Close Open Issues (Bugs)
* Portal CSS
- consistency to all admin portlets
- use css from style.tigris.org as PLT.C styles
* Cleanup and Reorganize the demo portal
-- add help to all admin portlets
-- remove old portlets that are simple programmer tests
-- move portlet applications to tlp
* Portlet Selector for the customizer
* User Admin Portlets (JS2-121)
-- Add/Remove Users, Filter Users
-- maintainance for roles, groups
* Site Manager
-- add/edit/remove folders, pages, links, metadata
-- import/export
-- integrate customizer
-- global site settings from edit mode
* Web Content Component
* JCMS backend for Page Manager
* SSO
* Secure Access to Site Resources (JS2-111)
-- Pages, Folders, Navigations
-- Portlets
-- Windows
* Documentation (JS2-83)
* JMX Component Configurator Portlet
* Portlets
-- HTML
-- DB Browser
-- Web Services (Stock Quote)
-- XSLT
-- RSS
* Bridges
-- Velocity Bridge
-- PHP Bridge
-- Perl (?)
* Enhanced credential security and validation (JS2-151)
* TCK compliance
* Dhtml horizontal menu with pulldown submenus for navigation
-- support for grouped pages/folders/documentSets
-- possibly based on JCookMenu
* Page decoration configuration defining allowable actions
including none
* Fixing Portlet info, resourcebundle and LanguageSet storage
Environment:
> 2.0-M1 release planning - features to include
> ---------------------------------------------
>
> Key: JS2-153
> URL: http://issues.apache.org/jira/browse/JS2-153
> Project: Jetspeed 2
> Type: New Feature
> Components: Other
> Versions: 2.0-FINAL, 2.0-M1
> Reporter: Ate Douma
> Assignee: Ate Douma
> Fix For: 2.0-M1
>
> Yesterday night (or very, very early in the morning, depending on the person
> involved) we had an IRC meeting about the upcoming release(s).
> Several subjects were discussed (a log of the discussion will also be made
> available) and one of it was the features which should be in the release.
> It was decided to create an issue in JIRA (this one) to collect all these
> features. All are invited to contribute.
> After completion of this (initial) list, one big Vote request for all the
> items will be presented on the developers mailing list.
> For each feature a vote for inclusion in the upcoming M1 release or inclusion
> in the FINAL release will then be requested:
> <item>
> part of M1 :
> part of FINAL:
> For each item voted in, we will of course need someone to step in for
> realization.
> Without proper commitment the item will have to be dropped off the feature
> list eventually.
> For each of these items an issue will be created in JIRA (if not there
> already). The developer assigned should then make some prediction when it
> can/will be ready by filling in the Due Date field.
> Based on that information we can get a first idea when the related release
> might be possible.
> To be clear: signing up for a feature and predicting a date when its due,
> doesn't implicate any obligation to do so, in accordance with the Apache
> policy. But it will help use get a better picture of what to do and to expect.
> Furthermore, this initial list of voted in features is not a closed or final.
> Item may be dropped or postponed and new items may be added. At least, with
> enough support.
> I kindly ask everyone to be careful with proposing new features and with
> voting them in. If we want a release as soon as possible (but no sooner), we
> should try to restrain ourselves to must have features alone or mostly.
> Better to have a limited initial version and quickly crank out additional
> features in short release cycles than an endless postponed one.
> Because we are planning to have a second IRC meeting next Monday (9 GMT
> again) it would be nice if everyone could have its requested features added
> to this list by then. During the meeting we will discuss the list further and
> hopefully put out a Vote request real soon.
> An initial feature list was already prepared by David Sean Taylor, and a few
> others were proposed during the IRC meeting.
> These features are:
> * Close Open Issues (Bugs)
> * Portal CSS
> - consistency to all admin portlets
> - use css from style.tigris.org as PLT.C styles
> * Cleanup and Reorganize the demo portal
> -- add help to all admin portlets
> -- remove old portlets that are simple programmer tests
> -- move portlet applications to tlp
> * Portlet Selector for the customizer
> * User Admin Portlets (JS2-121)
> -- Add/Remove Users, Filter Users
> -- maintainance for roles, groups
> * Site Manager
> -- add/edit/remove folders, pages, links, metadata
> -- import/export
> -- integrate customizer
> -- global site settings from edit mode
> * Web Content Component
> * JCMS backend for Page Manager
> * SSO
> * Secure Access to Site Resources (JS2-111)
> -- Pages, Folders, Navigations
> -- Portlets
> -- Windows
> * Documentation (JS2-83)
> * JMX Component Configurator Portlet
> * Portlets
> -- HTML
> -- DB Browser
> -- Web Services (Stock Quote)
> -- XSLT
> -- RSS
> * Bridges
> -- Velocity Bridge
> -- PHP Bridge
> -- Perl (?)
> * Enhanced credential security and validation (JS2-151)
> * TCK compliance
> * Dhtml horizontal menu with pulldown submenus for navigation
> -- support for grouped pages/folders/documentSets
> -- possibly based on JCookMenu
> * Page decoration configuration defining allowable actions
> including none
> * Fixing Portlet info, resourcebundle and LanguageSet storage
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
