You are viewing a plain text version of this content. The canonical link for it is here.
Posted to muse-dev@ws.apache.org by Daniel Jemiolo <da...@us.ibm.com> on 2006/09/28 16:23:13 UTC
Cancelling today's call
Rather than have a short call today, I thought we could give everyone some
time back and discuss two small issues over email. The issues are:
1. Updating the deadline for 'new stuff' in 2.1 - it was supposed to be
today, but with the distraction of the new release date, we haven't had
time to attend to 2.1. I propose we move the deadline out a week to
Thursday, 10/5/06. Please add requests for new features to JIRA so the
team can review the impact before scheduling it for 2.1.
2. I'd like to make a branch for the 2.0.0 code before we start work on
2.1.0. At the same time, I'd like to clean up the current content of
/branches because there are a number of duplicate snapshots in there that
just hold Muse 1.0 content (for planned updates that never happened). I'd
like to leave the 1.0 branch so that anyone who needs to work off of that
code is clear on what to use. This would leave us with:
/branches
/1.0
/2.0.0
/2.1.0
...etc
Let me know if this is a problem. Otherwise I will make the new branch
after the release is out the door.
Dan
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org
Re: Cancelling today's call
Posted by Mark D Weitzel <we...@us.ibm.com>.
+1
_________________________________________
Mark Weitzel
Architect, IBM Software Group, Autonomic Computing
Phone (919) 543 0625
Andrew Eberbach/Durham/IBM@IBMUS
09/28/2006 10:27 AM
Please respond to
muse-dev@ws.apache.org
To
muse-dev@ws.apache.org
cc
Subject
Re: Cancelling today's call
Yeah sounds reasonable on both counts.
Thanks,
Andrew
Andrew Eberbach
Autonomic Computing
(919) 254-2645
T/L: 444-2645
aeberbac@us.ibm.com
Daniel Jemiolo/Durham/IBM@IBMUS
09/28/2006 10:23 AM
Please respond to
muse-dev@ws.apache.org
To
muse-dev@ws.apache.org
cc
Subject
Cancelling today's call
Rather than have a short call today, I thought we could give everyone some
time back and discuss two small issues over email. The issues are:
1. Updating the deadline for 'new stuff' in 2.1 - it was supposed to be
today, but with the distraction of the new release date, we haven't had
time to attend to 2.1. I propose we move the deadline out a week to
Thursday, 10/5/06. Please add requests for new features to JIRA so the
team can review the impact before scheduling it for 2.1.
2. I'd like to make a branch for the 2.0.0 code before we start work on
2.1.0. At the same time, I'd like to clean up the current content of
/branches because there are a number of duplicate snapshots in there that
just hold Muse 1.0 content (for planned updates that never happened). I'd
like to leave the 1.0 branch so that anyone who needs to work off of that
code is clear on what to use. This would leave us with:
/branches
/1.0
/2.0.0
/2.1.0
...etc
Let me know if this is a problem. Otherwise I will make the new branch
after the release is out the door.
Dan
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org
Re: Cancelling today's call
Posted by Andrew Eberbach <ae...@us.ibm.com>.
Yeah sounds reasonable on both counts.
Thanks,
Andrew
Andrew Eberbach
Autonomic Computing
(919) 254-2645
T/L: 444-2645
aeberbac@us.ibm.com
Daniel Jemiolo/Durham/IBM@IBMUS
09/28/2006 10:23 AM
Please respond to
muse-dev@ws.apache.org
To
muse-dev@ws.apache.org
cc
Subject
Cancelling today's call
Rather than have a short call today, I thought we could give everyone some
time back and discuss two small issues over email. The issues are:
1. Updating the deadline for 'new stuff' in 2.1 - it was supposed to be
today, but with the distraction of the new release date, we haven't had
time to attend to 2.1. I propose we move the deadline out a week to
Thursday, 10/5/06. Please add requests for new features to JIRA so the
team can review the impact before scheduling it for 2.1.
2. I'd like to make a branch for the 2.0.0 code before we start work on
2.1.0. At the same time, I'd like to clean up the current content of
/branches because there are a number of duplicate snapshots in there that
just hold Muse 1.0 content (for planned updates that never happened). I'd
like to leave the 1.0 branch so that anyone who needs to work off of that
code is clear on what to use. This would leave us with:
/branches
/1.0
/2.0.0
/2.1.0
...etc
Let me know if this is a problem. Otherwise I will make the new branch
after the release is out the door.
Dan
---------------------------------------------------------------------
To unsubscribe, e-mail: muse-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: muse-dev-help@ws.apache.org