I'd like to propose the following plan for the remainder of the month. Spend the first half of the month focusing on bug fixes. We currently have over 200 bugs marked for 1.8. This number is growing at a much slower rate than it was a few months ago, but we really need to get this number down. While blockers and criticals are the most important, they're not necessarily the tickets we should be focusing on right now. These tickets are often the hardest to track down and/or the most time consuming to fix. What we should be looking for right now is quantity. So if you can fix ten minor/majors in the same time it takes to fix one or two blockers/criticals, that would be a good compromise right now.
We could then spend the second half of the month focusing on the new plugins planned for 1.8. Jörn has made some really good progress on buttons, menu, and autocomplete. We should spend this time figuring out how well the plugins work, where the holes are and what we need to release a rock solid minimalistic implementation. We can build demos (both functional and real world), write tests, finalize specs, etc. If we can know exactly where we are with each of these plugins and what still needs to be fleshed out both for design and implementation, we'll be in a great position to start the move to trunk.
There are some other areas we need to focus on as well, such as increasing test coverage, getting ready for the new directory structure and core plugins, finalizing the new widget factory, etc. but those things can wait till December. As always, people should be aware of where they can be utilized the best regardless of what the team's main focus is. For example, even while the focus would be on bug fixes during the beginning of the month, Jörn's time will probably be better spent continuing work on autocomplete and menu since that is where he has the most momentum. Likewise, having six or seven people trying to work on implementation for the new plugins at the same time probably won't be the most productive.
Do people have time to devote to this plan? Does anyone have any other suggestions or recommendations? I'd like to try to get the same kind of momentum we had this time last year; we've got a lot of work ahead of us for the 1.8 release.
> I'd like to propose the following plan for the remainder of the month.
> Spend the first half of the month focusing on bug fixes. We currently have
> over 200 bugs marked for 1.8. This number is growing at a much slower rate
> than it was a few months ago, but we really need to get this number down.
> While blockers and criticals are the most important, they're not necessarily
> the tickets we should be focusing on right now. These tickets are often the
> hardest to track down and/or the most time consuming to fix. What we should
> be looking for right now is quantity. So if you can fix ten minor/majors in
> the same time it takes to fix one or two blockers/criticals, that would be a
> good compromise right now.
> We could then spend the second half of the month focusing on the new
> plugins planned for 1.8. Jörn has made some really good progress on buttons,
> menu, and autocomplete. We should spend this time figuring out how well the
> plugins work, where the holes are and what we need to release a rock solid
> minimalistic implementation. We can build demos (both functional and real
> world), write tests, finalize specs, etc. If we can know exactly where we
> are with each of these plugins and what still needs to be fleshed out both
> for design and implementation, we'll be in a great position to start the
> move to trunk.
> There are some other areas we need to focus on as well, such as increasing
> test coverage, getting ready for the new directory structure and core
> plugins, finalizing the new widget factory, etc. but those things can wait
> till December. As always, people should be aware of where they can be
> utilized the best regardless of what the team's main focus is. For example,
> even while the focus would be on bug fixes during the beginning of the
> month, Jörn's time will probably be better spent continuing work on
> autocomplete and menu since that is where he has the most momentum.
> Likewise, having six or seven people trying to work on implementation for
> the new plugins at the same time probably won't be the most productive.
> Do people have time to devote to this plan? Does anyone have any other
> suggestions or recommendations? I'd like to try to get the same kind of
> momentum we had this time last year; we've got a lot of work ahead of us for
> the 1.8 release.
> Scott, I think your plan sounds great, and I'm board.
> - Richard
> 2009/11/4 Scott González <scott.gonza...@gmail.com>
> I'd like to propose the following plan for the remainder of the month.
>> Spend the first half of the month focusing on bug fixes. We currently have
>> over 200 bugs marked for 1.8. This number is growing at a much slower rate
>> than it was a few months ago, but we really need to get this number down.
>> While blockers and criticals are the most important, they're not necessarily
>> the tickets we should be focusing on right now. These tickets are often the
>> hardest to track down and/or the most time consuming to fix. What we should
>> be looking for right now is quantity. So if you can fix ten minor/majors in
>> the same time it takes to fix one or two blockers/criticals, that would be a
>> good compromise right now.
>> We could then spend the second half of the month focusing on the new
>> plugins planned for 1.8. Jörn has made some really good progress on buttons,
>> menu, and autocomplete. We should spend this time figuring out how well the
>> plugins work, where the holes are and what we need to release a rock solid
>> minimalistic implementation. We can build demos (both functional and real
>> world), write tests, finalize specs, etc. If we can know exactly where we
>> are with each of these plugins and what still needs to be fleshed out both
>> for design and implementation, we'll be in a great position to start the
>> move to trunk.
>> There are some other areas we need to focus on as well, such as increasing
>> test coverage, getting ready for the new directory structure and core
>> plugins, finalizing the new widget factory, etc. but those things can wait
>> till December. As always, people should be aware of where they can be
>> utilized the best regardless of what the team's main focus is. For example,
>> even while the focus would be on bug fixes during the beginning of the
>> month, Jörn's time will probably be better spent continuing work on
>> autocomplete and menu since that is where he has the most momentum.
>> Likewise, having six or seven people trying to work on implementation for
>> the new plugins at the same time probably won't be the most productive.
>> Do people have time to devote to this plan? Does anyone have any other
>> suggestions or recommendations? I'd like to try to get the same kind of
>> momentum we had this time last year; we've got a lot of work ahead of us for
>> the 1.8 release.
> I'd like to propose the following plan for the remainder of the month.
> Spend the first half of the month focusing on bug fixes. We currently have
> over 200 bugs marked for 1.8. This number is growing at a much slower rate
> than it was a few months ago, but we really need to get this number down.
> While blockers and criticals are the most important, they're not necessarily
> the tickets we should be focusing on right now. These tickets are often the
> hardest to track down and/or the most time consuming to fix. What we should
> be looking for right now is quantity. So if you can fix ten minor/majors in
> the same time it takes to fix one or two blockers/criticals, that would be a
> good compromise right now.
> We could then spend the second half of the month focusing on the new
> plugins planned for 1.8. Jörn has made some really good progress on buttons,
> menu, and autocomplete. We should spend this time figuring out how well the
> plugins work, where the holes are and what we need to release a rock solid
> minimalistic implementation. We can build demos (both functional and real
> world), write tests, finalize specs, etc. If we can know exactly where we
> are with each of these plugins and what still needs to be fleshed out both
> for design and implementation, we'll be in a great position to start the
> move to trunk.
> There are some other areas we need to focus on as well, such as increasing
> test coverage, getting ready for the new directory structure and core
> plugins, finalizing the new widget factory, etc. but those things can wait
> till December. As always, people should be aware of where they can be
> utilized the best regardless of what the team's main focus is. For example,
> even while the focus would be on bug fixes during the beginning of the
> month, Jörn's time will probably be better spent continuing work on
> autocomplete and menu since that is where he has the most momentum.
> Likewise, having six or seven people trying to work on implementation for
> the new plugins at the same time probably won't be the most productive.
> Do people have time to devote to this plan? Does anyone have any other
> suggestions or recommendations? I'd like to try to get the same kind of
> momentum we had this time last year; we've got a lot of work ahead of us for
> the 1.8 release.
Plan sounds good to me and I'm happy to hear that all the new plugins
Jörn have been working on are scheduled in. We're really swamped
through the end of the year finishing our book but we're happy to help
out with markup and CSS so just give us a shout when you need us.
_t
todd.parker .: . filament group inc.
102 south street #3 boston, ma 02111
On Nov 4, 2009, at 9:59 AM | November 4, 2009, Scott González wrote:
I'd like to propose the following plan for the remainder of the month.
Spend the first half of the month focusing on bug fixes. We currently
have over 200 bugs marked for 1.8. This number is growing at a much
slower rate than it was a few months ago, but we really need to get
this number down. While blockers and criticals are the most important,
they're not necessarily the tickets we should be focusing on right
now. These tickets are often the hardest to track down and/or the most
time consuming to fix. What we should be looking for right now is
quantity. So if you can fix ten minor/majors in the same time it takes
to fix one or two blockers/criticals, that would be a good compromise
right now.
We could then spend the second half of the month focusing on the new
plugins planned for 1.8. Jörn has made some really good progress on
buttons, menu, and autocomplete. We should spend this time figuring
out how well the plugins work, where the holes are and what we need to
release a rock solid minimalistic implementation. We can build demos
(both functional and real world), write tests, finalize specs, etc. If
we can know exactly where we are with each of these plugins and what
still needs to be fleshed out both for design and implementation,
we'll be in a great position to start the move to trunk.
There are some other areas we need to focus on as well, such as
increasing test coverage, getting ready for the new directory
structure and core plugins, finalizing the new widget factory, etc.
but those things can wait till December. As always, people should be
aware of where they can be utilized the best regardless of what the
team's main focus is. For example, even while the focus would be on
bug fixes during the beginning of the month, Jörn's time will probably
be better spent continuing work on autocomplete and menu since that is
where he has the most momentum. Likewise, having six or seven people
trying to work on implementation for the new plugins at the same time
probably won't be the most productive.
Do people have time to devote to this plan? Does anyone have any other
suggestions or recommendations? I'd like to try to get the same kind
of momentum we had this time last year; we've got a lot of work ahead
of us for the 1.8 release.
On Thu, Nov 5, 2009 at 9:49 PM, Todd Parker <t...@filamentgroup.com> wrote:
> Plan sounds good to me and I'm happy to hear that all the new plugins Jörn
> have been working on are scheduled in. We're really swamped through the end
> of the year finishing our book but we're happy to help out with markup and
> CSS so just give us a shout when you need us.
> _t
> todd.parker .: . filament group inc.
> 102 south street #3 boston, ma 02111
> On Nov 4, 2009, at 9:59 AM | November 4, 2009, Scott González wrote:
> I'd like to propose the following plan for the remainder of the month.
> Spend the first half of the month focusing on bug fixes. We currently have
> over 200 bugs marked for 1.8. This number is growing at a much slower rate
> than it was a few months ago, but we really need to get this number down.
> While blockers and criticals are the most important, they're not necessarily
> the tickets we should be focusing on right now. These tickets are often the
> hardest to track down and/or the most time consuming to fix. What we should
> be looking for right now is quantity. So if you can fix ten minor/majors in
> the same time it takes to fix one or two blockers/criticals, that would be a
> good compromise right now.
> We could then spend the second half of the month focusing on the new
> plugins planned for 1.8. Jörn has made some really good progress on buttons,
> menu, and autocomplete. We should spend this time figuring out how well the
> plugins work, where the holes are and what we need to release a rock solid
> minimalistic implementation. We can build demos (both functional and real
> world), write tests, finalize specs, etc. If we can know exactly where we
> are with each of these plugins and what still needs to be fleshed out both
> for design and implementation, we'll be in a great position to start the
> move to trunk.
> There are some other areas we need to focus on as well, such as increasing
> test coverage, getting ready for the new directory structure and core
> plugins, finalizing the new widget factory, etc. but those things can wait
> till December. As always, people should be aware of where they can be
> utilized the best regardless of what the team's main focus is. For example,
> even while the focus would be on bug fixes during the beginning of the
> month, Jörn's time will probably be better spent continuing work on
> autocomplete and menu since that is where he has the most momentum.
> Likewise, having six or seven people trying to work on implementation for
> the new plugins at the same time probably won't be the most productive.
> Do people have time to devote to this plan? Does anyone have any other
> suggestions or recommendations? I'd like to try to get the same kind of
> momentum we had this time last year; we've got a lot of work ahead of us for
> the 1.8 release.
> I'd like to propose the following plan for the remainder of the month.
> Spend the first half of the month focusing on bug fixes. We currently have
> over 200 bugs marked for 1.8. This number is growing at a much slower rate
> than it was a few months ago, but we really need to get this number down.
> While blockers and criticals are the most important, they're not necessarily
> the tickets we should be focusing on right now. These tickets are often the
> hardest to track down and/or the most time consuming to fix. What we should
> be looking for right now is quantity. So if you can fix ten minor/majors in
> the same time it takes to fix one or two blockers/criticals, that would be a
> good compromise right now.
> We could then spend the second half of the month focusing on the new
> plugins planned for 1.8. Jörn has made some really good progress on buttons,
> menu, and autocomplete. We should spend this time figuring out how well the
> plugins work, where the holes are and what we need to release a rock solid
> minimalistic implementation. We can build demos (both functional and real
> world), write tests, finalize specs, etc. If we can know exactly where we
> are with each of these plugins and what still needs to be fleshed out both
> for design and implementation, we'll be in a great position to start the
> move to trunk.
> There are some other areas we need to focus on as well, such as increasing
> test coverage, getting ready for the new directory structure and core
> plugins, finalizing the new widget factory, etc. but those things can wait
> till December. As always, people should be aware of where they can be
> utilized the best regardless of what the team's main focus is. For example,
> even while the focus would be on bug fixes during the beginning of the
> month, Jörn's time will probably be better spent continuing work on
> autocomplete and menu since that is where he has the most momentum.
> Likewise, having six or seven people trying to work on implementation for
> the new plugins at the same time probably won't be the most productive.
> Do people have time to devote to this plan? Does anyone have any other
> suggestions or recommendations? I'd like to try to get the same kind of
> momentum we had this time last year; we've got a lot of work ahead of us for
> the 1.8 release.
In the past 12 days, I closed 60 tickets (22 fixed, 2 enhancements, 1 feature, 1 new effect, 2 duplicate, 10 worksforme, 11 wontfix, 11 invalid). At this point class animations should work properly in all browsers. The only remaining tickets for class animations are feature requests.
There are currently 487 open tickets, so there's still a lot of triaging, testing and fixing that needs to occur. Jörn made some good progress on tooltip, menu, and autocomplete during this time as well. The rest of the month will be focusing on these plugins, as well as button. I think we should skip modal for this release.
We'll need to triage all tickets by the end of the month so that we know exactly how much work is left before we can push 1.8. As part of this prep, I'd like to push out 1.8a2 ASAP so we can start getting some feedback.
On Nov 15, 2009, at Nov 15, 2009 |10:27 PM, Scott González wrote:
> In the past 12 days, I closed 60 tickets (22 fixed, 2 enhancements, 1 feature, 1 new effect, 2 duplicate, 10 worksforme, 11 wontfix, 11 invalid). At this point class animations should work properly in all browsers. The only remaining tickets for class animations are feature requests.
> There are currently 487 open tickets, so there's still a lot of triaging, testing and fixing that needs to occur. Jörn made some good progress on tooltip, menu, and autocomplete during this time as well. The rest of the month will be focusing on these plugins, as well as button. I think we should skip modal for this release.
> We'll need to triage all tickets by the end of the month so that we know exactly how much work is left before we can push 1.8. As part of this prep, I'd like to push out 1.8a2 ASAP so we can start getting some feedback.
todd.parker .: . filament group inc.
102 south street #3 boston, ma 02111
> On Nov 15, 2009, at Nov 15, 2009 |10:27 PM, Scott González wrote:
> In the past 12 days, I closed 60 tickets (22 fixed, 2 enhancements, 1
> feature, 1 new effect, 2 duplicate, 10 worksforme, 11 wontfix, 11 invalid).
> At this point class animations should work properly in all browsers. The
> only remaining tickets for class animations are feature requests.
> There are currently 487 open tickets, so there's still a lot of triaging,
> testing and fixing that needs to occur. Jörn made some good progress on
> tooltip, menu, and autocomplete during this time as well. The rest of the
> month will be focusing on these plugins, as well as button. I think we
> should skip modal for this release.
> We'll need to triage all tickets by the end of the month so that we know
> exactly how much work is left before we can push 1.8. As part of this prep,
> I'd like to push out 1.8a2 ASAP so we can start getting some feedback.
> todd.parker .: . filament group inc.
> 102 south street #3 boston, ma 02111
> On Sun, Nov 15, 2009 at 11:02 PM, Todd Parker <t...@filamentgroup.com>wrote:
>> Thanks for all your hard work Scott (and Jörn)!
>> _t
>> On Nov 15, 2009, at Nov 15, 2009 |10:27 PM, Scott González wrote:
>> In the past 12 days, I closed 60 tickets (22 fixed, 2 enhancements, 1
>> feature, 1 new effect, 2 duplicate, 10 worksforme, 11 wontfix, 11 invalid).
>> At this point class animations should work properly in all browsers. The
>> only remaining tickets for class animations are feature requests.
>> There are currently 487 open tickets, so there's still a lot of triaging,
>> testing and fixing that needs to occur. Jörn made some good progress on
>> tooltip, menu, and autocomplete during this time as well. The rest of the
>> month will be focusing on these plugins, as well as button. I think we
>> should skip modal for this release.
>> We'll need to triage all tickets by the end of the month so that we know
>> exactly how much work is left before we can push 1.8. As part of this prep,
>> I'd like to push out 1.8a2 ASAP so we can start getting some feedback.
>> todd.parker .: . filament group inc.
>> 102 south street #3 boston, ma 02111
> --~--~---------~--~----~------------~-------~--~----~
> You received this message because you are subscribed to the Google Groups
> "jQuery UI Development" group.
> To post to this group, send email to jquery-ui-dev@googlegroups.com
> To unsubscribe from this group, send email to
> jquery-ui-dev+unsubscribe@googlegroups.com<jquery-ui-dev%2Bunsubscribe@goog legroups.com>
> For more options, visit this group at
> http://groups.google.com/group/jquery-ui-dev?hl=en > -~----------~----~----~----~------~----~------~--~---
May I humbly suggest that you put some info about the progress and the
hard work actually going on, on the jQuery UI blog?
The blog has the tagline "Check back frequently for development status
updates and news about the jQuery UI library and community." but
there's been no new post since August 12 and I don't know if people
are aware of threads like this one.
/Adrian
On Nov 26, 2:44 am, Ralph Whitbeck <ralph.whitb...@gmail.com> wrote:
> On Mon, Nov 16, 2009 at 12:07 AM, Richard D. Worth <rdwo...@gmail.com>wrote:
> > Indeed. You guys are on fire.
> > - Richard
> > On Sun, Nov 15, 2009 at 11:02 PM, Todd Parker <t...@filamentgroup.com>wrote:
> >> Thanks for all your hard work Scott (and Jörn)!
> >> _t
> >> On Nov 15, 2009, at Nov 15, 2009 |10:27 PM, Scott González wrote:
> >> In the past 12 days, I closed 60 tickets (22 fixed, 2 enhancements, 1
> >> feature, 1 new effect, 2 duplicate, 10 worksforme, 11 wontfix, 11 invalid).
> >> At this point class animations should work properly in all browsers. The
> >> only remaining tickets for class animations are feature requests.
> >> There are currently 487 open tickets, so there's still a lot of triaging,
> >> testing and fixing that needs to occur. Jörn made some good progress on
> >> tooltip, menu, and autocomplete during this time as well. The rest of the
> >> month will be focusing on these plugins, as well as button. I think we
> >> should skip modal for this release.
> >> We'll need to triage all tickets by the end of the month so that we know
> >> exactly how much work is left before we can push 1.8. As part of this prep,
> >> I'd like to push out 1.8a2 ASAP so we can start getting some feedback.
> >> todd.parker .: . filament group inc.
> >> 102 south street #3 boston, ma 02111
> > --~--~---------~--~----~------------~-------~--~----~
> > You received this message because you are subscribed to the Google Groups
> > "jQuery UI Development" group.
> > To post to this group, send email to jquery-ui-dev@googlegroups.com
> > To unsubscribe from this group, send email to
> > jquery-ui-dev+unsubscribe@googlegroups.com<jquery-ui-dev%2Bunsubscribe@goog legroups.com>
> > For more options, visit this group at
> >http://groups.google.com/group/jquery-ui-dev?hl=en > > -~----------~----~----~----~------~----~------~--~---
|
