Hello Sanjiva,
The students who will be doing the Metro web services are completely new to web
services in general, let along the Metro stack, let alone the stonehenge code,
let alone their other classes. Therefore it is impossible to make any estimates
at this time.
We've been doing background work until now. We should be starting to look at
the stonehenge code soon, but again, we can't provide any estimates.
I would suggest proceeding without Metro and working in the Metro version as it
becomes available.
Regards,
Harold
Sanjiva Weerawarana wrote:
Drew, I'd like to get CXF and/or Metro code also done before we do a full
release.
Dan/Harold, is that a realistic thing? I think we can help with refactoring
the Java code to be common and Axis2/WSAS to be separated.
Sanjiva.
On Sat, Feb 21, 2009 at 4:10 AM, Abu Obeida Bakhach <
[email protected]> wrote:
Today is the 20th of Feb. Do we really 40 days to do these tasks?
I think Drew is close ( or already done?) moving the code to contrib.. I am
blocked by few things but should have my PHP install working out pretty
soon.
Who is willing to test the interop part between the contributions?
Thanks,
-----Original Message-----
From: Kamaljit Bath [mailto:[email protected]]
Sent: Tuesday, February 17, 2009 12:17 PM
To: [email protected]
Subject: Defining the next milestone
Hello fellow Stonehenge committers,
As we get prepared to move all the existing code from contrib to trunk, I
will like to start a thread to define the goals and exit criteria for the
next milestone.
Here are a few suggestions - please help in solidifying these over the next
couple of days so that we can come to an agreed set of goals, exit criteria
and timeline by the end of this week (please excuse if there are more
structured ways of doing/defining these at Apache - we are still learning
our ropes over here):
- All the contributions are moved over to the new tree structure
and they can be independently downloaded and build
- Documentation and install instructions for each platform are
uploaded on the wiki page
- Each individual contribution has been independently tested and
verified by some other committer who has not contributed to that particular
branch. Do we need some kind of a sign-off mechanism for this?
- Interoperability between individual contribution is achieved and
can be tested and verified. Goal is to be able use different components from
multiple contributions to create a heterogeneous, multi-tier application
running on multiple platforms (for example, configure the front-end from one
contribution with the backend of another contribution) At the minimum, we
should try to achieve the scenarios that were demo'ed last summer by WSO2
and Microsoft [1].
- List of bugs identified and fixed in various contributions to
achieve the above
I think we should set-up an exit date of March 31st for this milestone.
Thanks
Kamal
[1]
http://video.msn.com/video.aspx?mkt=en-us&vid=7019fbb8-4d12-4f56-93a1-a39b9d2ccb00
