[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [gmf-dev] Bi-weekly call agenda
|
This is what we do on the CDT, too. Future actually makes little sense. '--'
means that the owner of the bug hasn't committed to what release they will
fix it in, which essentially means Future. Bugs left on the inbox mean they
are untriaged.
Doug Schaefer, QNX Software Systems
Eclipse CDT Project Lead, http://cdtdoug.blogspot.com
> -----Original Message-----
> From: gmf-dev-bounces@xxxxxxxxxxx [mailto:gmf-dev-bounces@xxxxxxxxxxx] On
> Behalf Of Anthony Hunter
> Sent: Tuesday, June 19, 2007 10:05 AM
> To: GMF Project developer discussions.
> Subject: Re: [gmf-dev] Bi-weekly call agenda
>
> Yes, I agree with your original proposal:
>
> I've also added milestones 2.1 M1-M6, as well as a 3.0 target. I think we
> can sufficiently triage incoming bugs and assign to one of these, leaving
> the 2.1 for those under consideration for the next release, 3.0 for those
> in
> the next-next release, and --- for those not yet reviewed. To me, if it's
> in a component inbox, it's in the not yet reviewed/later state.
>
> Not sure why my replies came out of order.
>
> Cheers...
> Anthony
> --
> Anthony Hunter mailto:anthonyh@xxxxxxxxxx
> Software Development Manager: Eclipse Open Source Components
> IBM Rational Software: Aurora / Modeling Tools
> Phone: 613-591-7037
>
>
>
>
> From: Richard Gronback <richard.gronback@xxxxxxxxxxx>
>
> To: "GMF Project developer discussions." <gmf-dev@xxxxxxxxxxx>
>
> Date: 19/06/2007 10:00 AM
>
> Subject Re: [gmf-dev] Bi-weekly call agenda
> :
>
>
>
>
>
> I guess the problem I have with something like "future" is that it feels a
> lot like the RESOLVED/LATER problem we have agreed to not do at Eclipse
> anymore. Who will look at them again?
>
> It seems you're happy with the 2.1 and milestones, plus a 3.0 target.
> Artem, seem OK to you?
>
> Thanks,
> Rich
>
>
> On 6/19/07 9:37 AM, "Anthony Hunter" <anthonyh@xxxxxxxxxx> wrote:
>
> > Agreed, Perhaps we should add the target milestone "Future". Other
> > components have "Future".
> >
> > Then we can bulk move to Future:
> >
> > "Did not make 2.0, moving to a future release. Originator should comment
> or
> > change the priority if the request is critical in nature".
> >
> > Cheers...
> > Anthony
> > --
> > Anthony Hunter mailto:anthonyh@xxxxxxxxxx
> > Software Development Manager: Eclipse Open Source Components
> > IBM Rational Software: Aurora / Modeling Tools
> > Phone: 613-591-7037
> >
> >
> >
> >
> > From: "Artem Tikhomirov" <Artem.Tikhomirov@xxxxxxxxxxx>
> >
> > To: "GMF Project developer discussions." <gmf-dev@xxxxxxxxxxx>
> >
> > Date: 19/06/2007 09:30 AM
> >
> > Subject RE: [gmf-dev] Bi-weekly call agenda
> > :
> >
> >
> >
> >
> >
> > '---' is not very handy - newly submitted requests get it by default and
> > it's just inconvenient to see both 'later' and 'not yet processed' in
> the
> > same list.
> >
> > Artem
> >
> >
> >> -----Original Message-----
> >> From: gmf-dev-bounces@xxxxxxxxxxx
> >> [mailto:gmf-dev-bounces@xxxxxxxxxxx] On Behalf Of Richard Gronback
> >> Sent: Tuesday, June 19, 2007 1:31 PM
> >> To: GMF Project developer discussions.
> >> Subject: Re: [gmf-dev] Bi-weekly call agenda
> >>
> >> I added 2.0.1 and 2.0.2
> >>
> >> The 'future' milestone is usually indicated with '---'. I'm
> >> not sure what other kind of milestone we could set, or if we
> >> even should. Ideas?
> >>
> >> - Rich
> >>
> >>
> >> On 6/19/07 5:22 AM, "Artem Tikhomirov"
> >> <Artem.Tikhomirov@xxxxxxxxxxx> wrote:
> >>
> >>> Hello,
> >>>
> >>> I suggest we add 2.0.x target milestones to Bugzilla and
> >> perhaps some
> >>> kind of 'future' milestone to denote requests that are not
> >> planned for
> >>> next release but helpwanted/may be considered later. Bulk
> >> move to 2.1
> >>> is easy but not that sensible ;)
> >>>
> >>> Artem
> >>>
> >>>> -----Original Message-----
> >>>> From: gmf-dev-bounces@xxxxxxxxxxx
> >>>> [mailto:gmf-dev-bounces@xxxxxxxxxxx] On Behalf Of Richard Gronback
> >>>> Sent: Monday, June 18, 2007 11:57 PM
> >>>> To: GMF Project developer discussions.
> >>>> Subject: Re: [gmf-dev] Bi-weekly call agenda
> >>>>
> >>>> Let's all try to cleanup Bugzilla, then we'll have a clear view of
> >>>> what's left. I'm traveling this evening, but will try to sync
> >>>> Deskzilla and run through all those still in 2.0/RCM7.
> >>>>
> >>>> Sure, if you have some for 2.0 you'd like to discuss on the call
> >>>> tomorrow, please list on the wiki. If there are none
> >> listed, we'll
> >>>> know not to dial in.
> >>>>
> >>>> Thanks,
> >>>> Rich
> >>>>
> >>>>
> >>>> On 6/18/07 8:58 AM, "Anthony Hunter" <anthonyh@xxxxxxxxxx> wrote:
> >>>>
> >>>>> Maybe we should list the Bugzillas we plan to do for the release?
> >>>>> Should we do this today?
> >>>>>
> >>>>> Cheers...
> >>>>> Anthony
> >>>>> --
> >>>>> Anthony Hunter mailto:anthonyh@xxxxxxxxxx Software Development
> >>>>> Manager: Eclipse Open Source Components IBM Rational
> >>>> Software: Aurora
> >>>>> / Modeling Tools
> >>>>> Phone: 613-591-7037
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> From: Richard Gronback <richard.gronback@xxxxxxxxxxx>
> >>>>>
> >>>>> To: "GMF Project developer discussions."
> >> <gmf-dev@xxxxxxxxxxx>
> >>>>>
> >>>>> Date: 18/06/2007 06:52 AM
> >>>>>
> >>>>> Subject [gmf-dev] Bi-weekly call agenda
> >>>>> :
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> Is there anything to discuss this time, or are we all set
> >>>> to build 2.0?
> >>>>>
> >>>>> http://wiki.eclipse.org/index.php/GMF_Dev_Calls
> >>>>>
> >>>>> Thanks,
> >>>>> Rich
> >>>>> --
> >>>>> Richard C. Gronback
> >>>>> Borland Software Corporation
> >>>>> richard.gronback@xxxxxxxxxxx
> >>>>> +1 860 227 9215_______________________________________________
> >>>>> gmf-dev mailing list
> >>>>> gmf-dev@xxxxxxxxxxx
> >>>>> https://dev.eclipse.org/mailman/listinfo/gmf-dev
> >>>>>
> >>>>>
> >>>>> _______________________________________________
> >>>>> gmf-dev mailing list
> >>>>> gmf-dev@xxxxxxxxxxx
> >>>>> https://dev.eclipse.org/mailman/listinfo/gmf-dev
> >>>>
> >>>> --
> >>>> Richard C. Gronback
> >>>> Borland Software Corporation
> >>>> richard.gronback@xxxxxxxxxxx
> >>>> +1 860 227 9215
> >>>>
> >>>> _______________________________________________
> >>>> gmf-dev mailing list
> >>>> gmf-dev@xxxxxxxxxxx
> >>>> https://dev.eclipse.org/mailman/listinfo/gmf-dev
> >>>>
> >>> _______________________________________________
> >>> gmf-dev mailing list
> >>> gmf-dev@xxxxxxxxxxx
> >>> https://dev.eclipse.org/mailman/listinfo/gmf-dev
> >>
> >> --
> >> Richard C. Gronback
> >> Borland Software Corporation
> >> richard.gronback@xxxxxxxxxxx
> >> +1 860 227 9215
> >>
> >> _______________________________________________
> >> gmf-dev mailing list
> >> gmf-dev@xxxxxxxxxxx
> >> https://dev.eclipse.org/mailman/listinfo/gmf-dev
> >>
> > _______________________________________________
> > gmf-dev mailing list
> > gmf-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/gmf-dev
> >
> >
> > _______________________________________________
> > gmf-dev mailing list
> > gmf-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/gmf-dev
>
> --
> Richard C. Gronback
> Borland Software Corporation
> richard.gronback@xxxxxxxxxxx
> +1 860 227 9215
>
> _______________________________________________
> gmf-dev mailing list
> gmf-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/gmf-dev
>
>
> _______________________________________________
> gmf-dev mailing list
> gmf-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/gmf-dev
