You are viewing a plain text version of this content. The canonical link for it is here.
Posted to muse-user@ws.apache.org by "Vinh Nguyen (vinguye2)" <vi...@cisco.com> on 2008/02/02 00:35:16 UTC
plans for next Muse release?
Hi,
Is there a target date set for the next Muse release? There are several
bugs outstanding, and most importantly to me is MUSE-270.
Chris has submitted a test patch which I haven't been able to test yet,
but I'm sure it works. To avoid licensing/copyright issues, I'd prefer
not patching the Muse code myself since the distribution of our end
product includes not just the Muse-based server application, but also
the client proxy APIs which customers will integrate into their client
apps. So customers will also need to use the patched Muse jars.
Activity on this forum has dropped for sometime now, and I'm wondering
if there's still plans to keep Muse active.
Aloha,
-Vinh
RE: plans for next Muse release?
Posted by "Hawkins, Joel" <Jo...@compuware.com>.
Dan,
When are you thinking of posting the vote for 2.3? I'd like to write an
isolation layer for CXF, assuming I've got this weekend to work on it...
Cheers,
Joel
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
RE: plans for next Muse release?
Posted by "Vinh Nguyen (vinguye2)" <vi...@cisco.com>.
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
<Ch...@swisscom.com> 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]
> 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
> 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
>
RE: plans for next Muse release?
Posted by Daniel Jemiolo <da...@us.ibm.com>.
I agree - both 270 and 283 must be included for 2.3 to be worth voting for.
Dan
<Ch...@swisscom.com> 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]
> 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
> 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
>
RE: plans for next Muse release?
Posted by Ch...@swisscom.com.
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]
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
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
Re: plans for next Muse release?
Posted by Daniel Jemiolo <da...@us.ibm.com>.
The first thing you can do it upload the code in JIRA and grant it the ASF
license. Make sure everyone who is contributing significantly has filled
out the Apache CLA form and faxed it in; the project needs new committers,
so if there are one or more people who are leading the development effort,
we should try to get them committer access. We should also open the floor
to some of the developers who've been working with Muse since 2.0 and have
made lots of reports, improvements, etc. - off the top of my head that
includes Chris Twiner and Lenni Madsen.
Thoughts?
Dan
"Kam K. Yee" <op...@gmail.com> wrote on 04/03/2008 11:18:06 AM:
>
> 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.html
> 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
>
Re: plans for next Muse release?
Posted by "Kam K. Yee" <op...@gmail.com>.
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.html
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
AW: plans for next Muse release?
Posted by Oliver Wäldrich <ol...@gmx.de>.
Hi,
please consider the bug MUSE-232 also fort the next Muse release. At least
for our systems this bug is a blocker.
Best regards,
Oliver
Von: Vinh Nguyen (vinguye2) [mailto:vinguye2@cisco.com]
Gesendet: Samstag, 2. Februar 2008 00:35
An: muse-user@ws.apache.org; muse-dev@ws.apache.org
Betreff: plans for next Muse release?
Hi,
Is there a target date set for the next Muse release? There are several
bugs outstanding, and most importantly to me is MUSE-270.
Chris has submitted a test patch which I haven't been able to test yet, but
I'm sure it works. To avoid licensing/copyright issues, I'd prefer not
patching the Muse code myself since the distribution of our end product
includes not just the Muse-based server application, but also the client
proxy APIs which customers will integrate into their client apps. So
customers will also need to use the patched Muse jars.
Activity on this forum has dropped for sometime now, and I'm wondering if
there's still plans to keep Muse active.
Aloha,
-Vinh