The following comment has been added to this issue:
Author: David Le Strat
Created: Wed, 13 Oct 2004 9:36 AM
Body:
+1 on the 3 points above.
Regarding future new code contributions, are we freezing the code base (new features)
for a specific period to prepare for M1?
What is the targetted release date?
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/JS2-148?page=comments#action_54001
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/JS2-148
Here is an overview of the issue:
---------------------------------------------------------------------
Key: JS2-148
Summary: Pre-2.0 Milestone 1 Release Cleanup task
Type: Task
Status: Open
Priority: Major
Project: Jetspeed 2
Fix Fors:
2.0-a1
2.0-M1
Versions:
2.0-a1
2.0-M1
Assignee: Scott T Weaver
Reporter: Scott T Weaver
Created: Wed, 13 Oct 2004 8:32 AM
Updated: Wed, 13 Oct 2004 9:36 AM
Description:
To get the ball rolling on getting a 2.0 M1 release out I have started cleaning up the
Jetspeed 2 source tree, removing things that are no longer used.
current progress:
- I have tagged a cleanup-20041013 which is a snapshot of HEAD prior to the clean up.
- Removed all pico/nano/groovy deps.
- Resolved any compile issues tied to the preceeding dep cleanup.
- Removed any pico/nano/groovy specific classes/tests/artifacts.
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
