> And after this discussion, it seems we
probably shouldn’t wait for July, but do it right after Indigo
releases.
I'm sure there will be headaches, but I think it will
be for the greater good.
+1
Agreed.
I use it daily for my non-CDT projects. I’m pretty happy with
it.
The
patch process is still a bit rough, but the good news is that it’s really no
worse than it is with CVS. And I will document that along with our other
processes before we move.
And
after this discussion, it seems we probably shouldn’t wait for July, but do it
right after Indigo releases.
Doug.
From:
cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf
Of Andrew Gvozdev
Sent: Friday, May 06, 2011 5:05
PM
To: CDT General developers list.
Subject: Re: [cdt-dev]
Eclipse C/C++ IDE for Indigo M7 ready
And egit is pretty solid by now. Maybe it is still a bit
rough on edges but it provides for productive work. The team did fantastic
work.
Andrew
On Fri, May 6, 2011 at 5:00 PM, Schaefer, Doug <Doug.Schaefer@xxxxxxxxxxxxx>
wrote:
Well, two more months and you'll be forced, I
guess.
> Sent: Friday, May 06, 2011 4:57 PM
> To: CDT General developers list.
> Subject: Re:
[cdt-dev] Eclipse C/C++ IDE for Indigo M7 ready
>
> I am not
really an early adopter sorry. I won't switch to git unless
forced
>
> On Fri, May 6, 2011 at 4:46 PM, Andrew Gvozdev <angvoz.dev@xxxxxxxxx>
>
wrote:
> > Maybe that is a good occasion to get ready for git for you
and your student.
> > You can just clone CDT repository
> >
from http://dev.eclipse.org/git/index.html.
> >
Andrew
> >
> > On Fri, May 6, 2011 at 4:41 PM, Schaefer,
Doug
> > <Doug.Schaefer@xxxxxxxxxxxxx>
>
> wrote:
> >>
> >> No, we don't have rules like
that. But that's an aside.
> >>
> >> If you want to
create a private branch for the work, go ahead. Or you
> >> can
just maintain a master patch in bugzilla that the student keeps
>
updating.
> >>
> >> At either rate, I would like to
keep us to the rule we've always had,
> >> no branch until the
release. (In fact, we once had the rule that we
> >> didn't branch
until SR1 so it's still an improvement).
> >>
> >> And
yes, once we move to git, all this becomes moot. Branches are
> >>
super easy to create and you don't even have to commit them to
the
> master repo.
> >>
> >> D.
>
>>
> >> > -----Original Message-----
> >>
> From: cdt-dev-bounces@xxxxxxxxxxx
>
>> > [mailto:cdt-dev-bounces@xxxxxxxxxxx]
>
>> > On Behalf Of Alena Laskavaia
> >> > Sent: Friday,
May 06, 2011 4:18 PM
> >> > To: James Blackburn
>
>> > Cc: CDT General developers list.
> >> > Subject:
Re: [cdt-dev] Eclipse C/C++ IDE for Indigo M7 ready
> >>
>
> >> > First time I hear about these rules. Are we (cdt
commiters) signing
> >> > up for this?
> >> > We
have a commit log we can check, if we want to enforce it we need
>
>> > to put
> >> > CI: <name> in the commit
comment (CI = code inspect) and everybody
> >> > who violate
this would be kicked out of committers (just kidding)
> >> >
But seriously?
> >> >
> >> > On Fri, May 6, 2011
at 4:08 PM, James Blackburn
> >> > <jamesblackburn@xxxxxxxxx>
wrote:
> >> > > This is precisely why we need git to make
working on a feature
> >> > > branch
> >> >
easier...
> >> > > The platform have effectively frozen -
all fixes need +1 by
> >> > > another committer before
commit.
> >> > > As per the rules, any non-bugfix work
should go on a branch, or
> >> > > more likely remain as
patches on bugzilla.
> >> > >
> >> > > See
the rules of engagement:
> >> > >
> http://www.eclipse.org/eclipse/development/plans/freeze_plan_3_7.
>
>> > > php
> >> > >
> >> > >
Cheers,
> >> > > James
> >> > >
>
>> > > On 6 May 2011, at 20:30, Alena Laskavaia
> >>
> > <elaskavaia.cdt@xxxxxxxxx>
>
>> > wrote:
> >> > >
> >> > >>
I have a student for GSOC where he suppose o add new features?
>
>> > >>
> >> > >> On Fri, May 6, 2011 at
2:56 PM, Schaefer, Doug
> >> > >> <Doug.Schaefer@xxxxxxxxxxxxx>
wrote:
> >> > >>> As with previous releases, we won't
branch until the last build
> >> > >>> for Indigo. And
even then, we may want to wait until the move
> >> >
>>> to git is finished. Consider it a Jedi mind trick to get us
to
> >> > >>> fix bugs instead of working on new
features. :)
> >> > >>>
> >> >
>>> Doug.
> >> > >>>
> >> >
>>>> -----Original Message-----
> >> >
>>>> From: cdt-dev-bounces@xxxxxxxxxxx
>
>> > >>>> [mailto:cdt-dev-bounces@xxxxxxxxxxx]
>
>> > >>>> On Behalf Of Alena Laskavaia
> >>
> >>>> Sent: Friday, May 06, 2011 2:53 PM
> >> >
>>>> To: CDT General developers list.
> >> >
>>>> Subject: Re: [cdt-dev] Eclipse C/C++ IDE for Indigo M7
ready
> >> > >>>>
> >> >
>>>> Are we branching it? Where to commit new features?
>
>> > >>>>
> >> > >>>> On Fri,
May 6, 2011 at 11:10 AM, Schaefer, Doug
> >> > >>>>
<Doug.Schaefer@xxxxxxxxxxxxx>
wrote:
> >> > >>>>> BTW, huge thanks to Vivian
again for getting this all together!
> >> >
>>>>>
> >> > >>>>>
>
>> > >>>>>
> >> > >>>>>
From: cdt-dev-bounces@xxxxxxxxxxx
[mailto:cdt-dev-
> >> >
>>>> bounces@xxxxxxxxxxx]
> >>
> >>>>> On Behalf Of Schaefer, Doug
> >> >
>>>>> Sent: Friday, May 06, 2011 10:48 AM
> >> >
>>>>> To: cdt-dev@xxxxxxxxxxx
> >>
> >>>>> Subject: [cdt-dev] Eclipse C/C++ IDE for Indigo M7
ready
> >> > >>>>>
> >> >
>>>>>
> >> > >>>>>
>
>> > >>>>> Hey gang,
> >> >
>>>>>
> >> > >>>>>
>
>> > >>>>>
> >> > >>>>>
The Eclipse C/C++ IDE for Indigo M7 is ready for your
> >> >
>>>>> download. It is available on the developers page on
the
> >> > >>>>> Eclipse download site, or just
click
> >> > >>>>> here:
> >> >
>>>>>
> >> > >>>>>
>
>> > >>>>>
> >> > >>>>>
http://www.eclipse.org/downloads/index-developer.php
>
>> > >>>>>
> >> >
>>>>>
> >> > >>>>>
>
>> > >>>>> This marks the feature freeze for CDT 8.0.
I encourage
> >> > >>>>> everyone to take some
time and give the IDE a spin so we can
> >> >
>>>>> make sure we have a great quality Indigo release. Only
4-ish
> weeks left!
> >> > >>>>>
>
>> > >>>>>
> >> >
>>>>>
> >> > >>>>>
End Date
Span
> >> > >>>>>
>
>> > >>>>> M1 Friday, August 20, 2010
08/06 to 08/20
> >> >
>>>>>
> >> > >>>>> M2
Friday, October 1
09/17 to 10/01
> >> > >>>>>
>
>> > >>>>> M3 Friday, November 12
10/29 to 11/12
> >> >
>>>>>
> >> > >>>>> M4
Friday, December 17
12/10 to 12/17 (shift
> >> > >>>>> from 2 week
window to 1 week window)
> >> > >>>>>
>
>> > >>>>> M5 Friday, February 4, 2011
01/28 to 02/04
> >> >
>>>>>
> >> > >>>>> M6
Friday, March 18
03/11 to 03/18
> >> > >>>>>
>
>> > >>>>> EclipseCon! March 21
03/21 to 03/24
> >> >
>>>>>
> >> > >>>>> M7
Friday, May 6
04/29 to 05/06
> >> >
>>>>>
> >> > >>>>> RC1 Friday,
May 20
05/13 to 05/20
> >> > >>>>>
>
>> > >>>>> RC2 Friday, May 27
05/20 to 05/27
>
>> > >>>>>
> >> > >>>>>
RC3 Friday, June 3
05/27 to 06/03
> >> > >>>>>
>
>> > >>>>> RC4 Friday, June 10
06/03 to 06/10
> >> >
>>>>>
> >> > >>>>> Quiet time,
June 11 to June 22
> >> > >>>>>
> >>
> >>>>> (no builds during "quiet time", assumed all
code is done by
> >> > >>>>> June
>
>> > >>>>> 10
> >> >
>>>>> (RC4)
> >> > >>>>>
>
>> > >>>>> Release Wednesday, June 22, 2011
>
>> > >>>>>
> >> >
>>>>>
> >> > >>>>>
>
>> > >>>>>
_______________________________________________
> >> >
>>>>> cdt-dev mailing list
> >> >
>>>>> cdt-dev@xxxxxxxxxxx
> >>
> >>>>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
>> > >>>>>
> >> >
>>>>>
> >> > >>>>
_______________________________________________
> >> >
>>>> cdt-dev mailing list
> >> > >>>>
cdt-dev@xxxxxxxxxxx
> >>
> >>>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
>> > >>>
> >> > >>
_______________________________________________
> >> > >>
cdt-dev mailing list
> >> > >> cdt-dev@xxxxxxxxxxx
> >>
> >> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
>> > >
> >> >
_______________________________________________
> >> > cdt-dev
mailing list
> >> > cdt-dev@xxxxxxxxxxx
> >>
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
>> _______________________________________________
> >>
cdt-dev mailing list
> >> cdt-dev@xxxxxxxxxxx
> >> https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
>
> >
> >
_______________________________________________
> > cdt-dev mailing
list
> > cdt-dev@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/cdt-dev
>
>
> >
>
_______________________________________________
> cdt-dev mailing
list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev
_______________________________________________
cdt-dev
mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
|
