BTW, when you "release" a version in JIRA, you have the option of bumping existing issues to the next, so this can just be one-click.
On Tue, Jan 8, 2013 at 2:22 PM, Jesse <[email protected]> wrote: > My message was actually a gentle nudge, maybe too gentle. > If you have an issue assigned to you and scheduled to be fixed for 2.3.0, > please deal with it, either by resolving it, or re-scheduling it. > > TIA > > Half of gardening is weeding > > On Tue, Jan 8, 2013 at 1:59 PM, Joe Bowser <[email protected]> wrote: > > > The three assigned to Android appear to be low-priority issues that > > can be bumped to the next version or unscheduled. We need to get > > better at gardening issues, since we're getting a lot of old, crufty > > issues that are starting to not be relevant. > > > > On Tue, Jan 8, 2013 at 1:57 PM, Don Coleman <[email protected]> > wrote: > > > CB-1130, CB-1131, CB-1132, CB-1133 are about the plugin guide. > > > > > > I think these can be closed. The current plugins docs > > > > > > http://docs.phonegap.com/en/2.3.0/guide_plugin-development_index.md.html#Plugin%20Development%20Guidelook > > > have been updated and look good. > > > > > > > > > On Tue, Jan 8, 2013 at 4:48 PM, Jesse <[email protected]> wrote: > > > > > >> There are still 41 unresolved issues 'scheduled' for 2.3.0 > > >> I suspect most are complete, but I'm not sure. > > >> > > >> > > >> > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20CB%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20%222.3.0%22%20ORDER%20BY%20priority%20DESC > > >> > > >> -- > > >> @purplecabbage > > >> risingj.com > > >> > > > > > > -- > @purplecabbage > risingj.com >
