ws-muse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rluce...@xecu.net
Subject Re: RE: plans for next Muse release?
Date Fri, 04 Apr 2008 01:42:31 GMT
 How is the patch coming for 270?  I remember Chris Twiner posting a
potential fix several months ago, but it needed further testing.  For
me, thread stability is the number one issue.
 I recently got approval from my employer to submit patches back to
muse.  I'm looking to take Muse into production in a couple of months
with a large customer as part of a WS-Notification based messaging
framework.
 Let me know how I can help with the fix for 270.
 - Rich
 On Thu 03/04/08  2:40 PM , "Vinh Nguyen (vinguye2)"
vinguye2@cisco.com sent:
    I agree, too!  These two are essential, whereas the  testing fw
and dynamic discovery items are enhancements.   Looks like I'll be
working with Muse code again soon for my  current project, so I'll be
an active participant again:) -Vinh
-------------------------
 From: Daniel Jemiolo  [mailto:danjemiolo@us.ibm.com] 
 Sent: Thursday, April 03, 2008 8:30  AM
 To: muse-dev@ws.apache.org
 Subject: RE: plans for next  Muse release?
	I agree - both 270 and 283 must be included for 2.3 to be worth
voting  for.
 Dan
  wrote on  04/03/2008 11:25:29 AM:
 > 270, 283 are essentials.  I'd also like  to see 271 in there (I
have my
 > own similar patch). 
 > 
 >  -----Original Message-----
 > From: Kam K. Yee [mailto:open.zourcerer@gmail.com [1]]  
 > Sent: Thursday, April 03, 2008 5:18 PM
 > To:  muse-dev@ws.apache.org
 > Subject: Re: plans for next Muse release?
 >  
 > 
 > I would like to re-post the same question...
 > 
 >  We, the team from IBM, have gotten the necessary internal
approvals for
 >  contributing code for the following JIRA line items:
 > 
 > 242 -  Security
 > 243 - Dynamic discovery and aggregation of resource  types
 > 256 - Discovery based bootstrapping for advertisements
 > 281  - Subscription Manager must throw faults on publish back to
 > notification  producer
 > 244 - Test/compliance framework for Muse
 > 259 - Flexible  test infrastructure and initial set of extensible
 > functional tests  
 > 
 > We would like to request these to be included in the 2.3  release.
 > 
 > What would be the best way to contribute the  code?
 > 
 > Also, JIRA items 102, 207, 252, 272, and 278 have patches 
attached which
 > we'd like to include also.
 > 
 > --
 >  View this message in context:
 >
http://www.nabble.com/plans-for-next-Muse-release--tp15237415p16467556.h
[2]
 >  tml
 > Sent from the Muse - Dev mailing list archive at Nabble.com.
 >  
 > 
 > 
---------------------------------------------------------------------
 > To  unsubscribe, e-mail: muse-dev-unsubscribe@ws.apache.org
 > For additional  commands, e-mail: muse-dev-help@ws.apache.org
 > 
 > 
 > 
---------------------------------------------------------------------
 > To  unsubscribe, e-mail: muse-dev-unsubscribe@ws.apache.org
 > For additional  commands, e-mail: muse-dev-help@ws.apache.org
 >  


Links:
------
[1]
http://webmail.xecu.net/javascript:top.opencompose(\'open.zourcerer@gmail.com\',\'\',\'\',\'\')
[2]
http://www.nabble.com/plans-for-next-Muse-release--tp15237415p16467556.h

Mime
View raw message