You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Matt Hogstrom <ma...@hogstrom.org> on 2006/06/16 16:21:03 UTC
1.1.1 Release Goals
Here is my proposal for defining the exit criteria for this release stream. I would like to
volunteer to lead the 1.1.1 release. Please respond if that is acceptable to you.
*Goals*
This is a maintenance release and as such it will be limited to:
*1. Bug fixes.*
There are approximately 50 JIRAs currently identified for 1.1.1. These are fixing issues related to
deployment, runtime, etc.
*2. Usability improvements.*
These will be limited in scope to correcting user interfaces issues, error messages, etc.
*3. Performance improvements.*
Examining performance using DayTrader and improving existing function as well as discussing some
limited functional improvements that are missing. These changes will not break applications
deployed on 1.1. Applications from 1.1 will be able to move forward without modification.
*Timeframe*
This is not time limited release. We will agree on the JIRA list and will focus on closing the
JIRAs that are agreed to for the release. Once those JIRAs are complete (or we decided to move one
or more out of the release for whatever reason) the project will be versioned and released.
*JIRA*
As noted earlier, JIRA will be used to manage the release. I proposed that the JIRA's that are
accepted into the 1.1 release are marked to unassigned. If someone is interested in working on the
JIRA they'll simply assign it to themselves. This way anyone that wants to participate can easily
identify what areas need more work.
*Next Steps*
Please review the JIRA's that are in 1.1. If there are fixes that should be included please propose
them for inclusion. Once we have a set of work items then we can get 1.1.1 done.
Comments or corrections to the above proposal welcome.
Matt
Re: 1.1.1 Release Goals
Posted by Matt Hogstrom <ma...@hogstrom.org>.
Kevan, I think that sounds like a good compromise. I'll create a 1.1.2 in JIRA. This will be part
of the triage process then.
Kevan Miller wrote:
> Matt,
> This is good. However, I think it's useful to think in terms of a 1.1.x
> release stream, or at least two 1.1.x releases. Where 1.1.1 is going to
> address our worst/highest priority problems. 1.1.x should be very soon
> (a few weeks?) after 1.1. This would be followed by a 1.1.2 which I
> think would be the target for the majority of the bug fixes and
> performance improvements that you're proposing. Thoughts?
>
> --kevan
>
> On Jun 16, 2006, at 10:21 AM, Matt Hogstrom wrote:
>
>> Here is my proposal for defining the exit criteria for this release
>> stream. I would like to volunteer to lead the 1.1.1 release. Please
>> respond if that is acceptable to you.
>>
>> *Goals*
>> This is a maintenance release and as such it will be limited to:
>> *1. Bug fixes.*
>> There are approximately 50 JIRAs currently identified for 1.1.1.
>> These are fixing issues related to deployment, runtime, etc.
>>
>> *2. Usability improvements.*
>> These will be limited in scope to correcting user interfaces issues,
>> error messages, etc.
>>
>> *3. Performance improvements.*
>> Examining performance using DayTrader and improving existing function
>> as well as discussing some limited functional improvements that are
>> missing. These changes will not break applications deployed on 1.1.
>> Applications from 1.1 will be able to move forward without modification.
>>
>> *Timeframe*
>> This is not time limited release. We will agree on the JIRA list and
>> will focus on closing the JIRAs that are agreed to for the release.
>> Once those JIRAs are complete (or we decided to move one or more out
>> of the release for whatever reason) the project will be versioned and
>> released.
>>
>> *JIRA*
>> As noted earlier, JIRA will be used to manage the release. I proposed
>> that the JIRA's that are accepted into the 1.1 release are marked to
>> unassigned. If someone is interested in working on the JIRA they'll
>> simply assign it to themselves. This way anyone that wants to
>> participate can easily identify what areas need more work.
>>
>> *Next Steps*
>> Please review the JIRA's that are in 1.1. If there are fixes that
>> should be included please propose them for inclusion. Once we have a
>> set of work items then we can get 1.1.1 done.
>>
>> Comments or corrections to the above proposal welcome.
>>
>> Matt
>
>
>
>
Re: 1.1.1 Release Goals
Posted by Kevan Miller <ke...@gmail.com>.
Matt,
This is good. However, I think it's useful to think in terms of a
1.1.x release stream, or at least two 1.1.x releases. Where 1.1.1 is
going to address our worst/highest priority problems. 1.1.x should be
very soon (a few weeks?) after 1.1. This would be followed by a 1.1.2
which I think would be the target for the majority of the bug fixes
and performance improvements that you're proposing. Thoughts?
--kevan
On Jun 16, 2006, at 10:21 AM, Matt Hogstrom wrote:
> Here is my proposal for defining the exit criteria for this release
> stream. I would like to volunteer to lead the 1.1.1 release.
> Please respond if that is acceptable to you.
>
> *Goals*
> This is a maintenance release and as such it will be limited to:
> *1. Bug fixes.*
> There are approximately 50 JIRAs currently identified for 1.1.1.
> These are fixing issues related to deployment, runtime, etc.
>
> *2. Usability improvements.*
> These will be limited in scope to correcting user interfaces
> issues, error messages, etc.
>
> *3. Performance improvements.*
> Examining performance using DayTrader and improving existing
> function as well as discussing some limited functional improvements
> that are missing. These changes will not break applications
> deployed on 1.1. Applications from 1.1 will be able to move
> forward without modification.
>
> *Timeframe*
> This is not time limited release. We will agree on the JIRA list
> and will focus on closing the JIRAs that are agreed to for the
> release. Once those JIRAs are complete (or we decided to move one
> or more out of the release for whatever reason) the project will be
> versioned and released.
>
> *JIRA*
> As noted earlier, JIRA will be used to manage the release. I
> proposed that the JIRA's that are accepted into the 1.1 release are
> marked to unassigned. If someone is interested in working on the
> JIRA they'll simply assign it to themselves. This way anyone that
> wants to participate can easily identify what areas need more work.
>
> *Next Steps*
> Please review the JIRA's that are in 1.1. If there are fixes that
> should be included please propose them for inclusion. Once we have
> a set of work items then we can get 1.1.1 done.
>
> Comments or corrections to the above proposal welcome.
>
> Matt
Re: 1.1.1 Release Goals
Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
I'm not comfortable with the idea of putting improvements in a patch
line but I will not do anything to try to stop it being done.
Regards,
Alan
Matt Hogstrom wrote:
> Here is my proposal for defining the exit criteria for this release
> stream. I would like to volunteer to lead the 1.1.1 release. Please
> respond if that is acceptable to you.
>
> *Goals*
> This is a maintenance release and as such it will be limited to:
> *1. Bug fixes.*
> There are approximately 50 JIRAs currently identified for 1.1.1.
> These are fixing issues related to deployment, runtime, etc.
>
> *2. Usability improvements.*
> These will be limited in scope to correcting user interfaces issues,
> error messages, etc.
>
> *3. Performance improvements.*
> Examining performance using DayTrader and improving existing function
> as well as discussing some limited functional improvements that are
> missing. These changes will not break applications deployed on 1.1.
> Applications from 1.1 will be able to move forward without modification.
>
> *Timeframe*
> This is not time limited release. We will agree on the JIRA list and
> will focus on closing the JIRAs that are agreed to for the release.
> Once those JIRAs are complete (or we decided to move one or more out
> of the release for whatever reason) the project will be versioned and
> released.
>
> *JIRA*
> As noted earlier, JIRA will be used to manage the release. I proposed
> that the JIRA's that are accepted into the 1.1 release are marked to
> unassigned. If someone is interested in working on the JIRA they'll
> simply assign it to themselves. This way anyone that wants to
> participate can easily identify what areas need more work.
>
> *Next Steps*
> Please review the JIRA's that are in 1.1. If there are fixes that
> should be included please propose them for inclusion. Once we have a
> set of work items then we can get 1.1.1 done.
>
> Comments or corrections to the above proposal welcome.
>
> Matt
Re: 1.1.1 Release Goals
Posted by Jeff Genender <jg...@apache.org>.
+1...very acceptable. Thanks for taking on 1.1.1. Matt...I know its a
tremendous amount of work. I would be happy to lend a hand.
Jeff
Matt Hogstrom wrote:
> Here is my proposal for defining the exit criteria for this release
> stream. I would like to volunteer to lead the 1.1.1 release. Please
> respond if that is acceptable to you.
>
> *Goals*
> This is a maintenance release and as such it will be limited to:
> *1. Bug fixes.*
> There are approximately 50 JIRAs currently identified for 1.1.1. These
> are fixing issues related to deployment, runtime, etc.
>
> *2. Usability improvements.*
> These will be limited in scope to correcting user interfaces issues,
> error messages, etc.
>
> *3. Performance improvements.*
> Examining performance using DayTrader and improving existing function as
> well as discussing some limited functional improvements that are
> missing. These changes will not break applications deployed on 1.1.
> Applications from 1.1 will be able to move forward without modification.
>
> *Timeframe*
> This is not time limited release. We will agree on the JIRA list and
> will focus on closing the JIRAs that are agreed to for the release.
> Once those JIRAs are complete (or we decided to move one or more out of
> the release for whatever reason) the project will be versioned and
> released.
>
> *JIRA*
> As noted earlier, JIRA will be used to manage the release. I proposed
> that the JIRA's that are accepted into the 1.1 release are marked to
> unassigned. If someone is interested in working on the JIRA they'll
> simply assign it to themselves. This way anyone that wants to
> participate can easily identify what areas need more work.
>
> *Next Steps*
> Please review the JIRA's that are in 1.1. If there are fixes that
> should be included please propose them for inclusion. Once we have a
> set of work items then we can get 1.1.1 done.
>
> Comments or corrections to the above proposal welcome.
>
> Matt
Re: 1.1.1 Release Goals
Posted by David Jencks <da...@yahoo.com>.
I like the plan and I like dain's timebox suggestion.
I think 2 weeks as a goal is ok and I hope we can get
1.1.1 out in 3 weeks.
thanks
david jencks
--- Dain Sundstrom <da...@iq80.com> wrote:
> I think this looks great except for one item. I
> think the release
> should be time boxed. I'm hoping for 2 weeks max and
> it ships. If we
> find something critical we move up the time, but 2
> weeks would be the
> max time. Three weeks would be ok also.
>
> -dain
>
> On Jun 16, 2006, at 7:21 AM, Matt Hogstrom wrote:
>
> > Here is my proposal for defining the exit criteria
> for this release
> > stream. I would like to volunteer to lead the
> 1.1.1 release.
> > Please respond if that is acceptable to you.
> >
> > *Goals*
> > This is a maintenance release and as such it will
> be limited to:
> > *1. Bug fixes.*
> > There are approximately 50 JIRAs currently
> identified for 1.1.1.
> > These are fixing issues related to deployment,
> runtime, etc.
> >
> > *2. Usability improvements.*
> > These will be limited in scope to correcting user
> interfaces
> > issues, error messages, etc.
> >
> > *3. Performance improvements.*
> > Examining performance using DayTrader and
> improving existing
> > function as well as discussing some limited
> functional improvements
> > that are missing. These changes will not break
> applications
> > deployed on 1.1. Applications from 1.1 will be
> able to move
> > forward without modification.
> >
> > *Timeframe*
> > This is not time limited release. We will agree
> on the JIRA list
> > and will focus on closing the JIRAs that are
> agreed to for the
> > release. Once those JIRAs are complete (or we
> decided to move one
> > or more out of the release for whatever reason)
> the project will be
> > versioned and released.
> >
> > *JIRA*
> > As noted earlier, JIRA will be used to manage the
> release. I
> > proposed that the JIRA's that are accepted into
> the 1.1 release are
> > marked to unassigned. If someone is interested in
> working on the
> > JIRA they'll simply assign it to themselves. This
> way anyone that
> > wants to participate can easily identify what
> areas need more work.
> >
> > *Next Steps*
> > Please review the JIRA's that are in 1.1. If
> there are fixes that
> > should be included please propose them for
> inclusion. Once we have
> > a set of work items then we can get 1.1.1 done.
> >
> > Comments or corrections to the above proposal
> welcome.
> >
> > Matt
>
>
Re: 1.1.1 Release Goals
Posted by Dain Sundstrom <da...@iq80.com>.
I think this looks great except for one item. I think the release
should be time boxed. I'm hoping for 2 weeks max and it ships. If we
find something critical we move up the time, but 2 weeks would be the
max time. Three weeks would be ok also.
-dain
On Jun 16, 2006, at 7:21 AM, Matt Hogstrom wrote:
> Here is my proposal for defining the exit criteria for this release
> stream. I would like to volunteer to lead the 1.1.1 release.
> Please respond if that is acceptable to you.
>
> *Goals*
> This is a maintenance release and as such it will be limited to:
> *1. Bug fixes.*
> There are approximately 50 JIRAs currently identified for 1.1.1.
> These are fixing issues related to deployment, runtime, etc.
>
> *2. Usability improvements.*
> These will be limited in scope to correcting user interfaces
> issues, error messages, etc.
>
> *3. Performance improvements.*
> Examining performance using DayTrader and improving existing
> function as well as discussing some limited functional improvements
> that are missing. These changes will not break applications
> deployed on 1.1. Applications from 1.1 will be able to move
> forward without modification.
>
> *Timeframe*
> This is not time limited release. We will agree on the JIRA list
> and will focus on closing the JIRAs that are agreed to for the
> release. Once those JIRAs are complete (or we decided to move one
> or more out of the release for whatever reason) the project will be
> versioned and released.
>
> *JIRA*
> As noted earlier, JIRA will be used to manage the release. I
> proposed that the JIRA's that are accepted into the 1.1 release are
> marked to unassigned. If someone is interested in working on the
> JIRA they'll simply assign it to themselves. This way anyone that
> wants to participate can easily identify what areas need more work.
>
> *Next Steps*
> Please review the JIRA's that are in 1.1. If there are fixes that
> should be included please propose them for inclusion. Once we have
> a set of work items then we can get 1.1.1 done.
>
> Comments or corrections to the above proposal welcome.
>
> Matt