Re: [cdt-dev] RE: API tooling for CDT 8.0 and CDT 7.0.1

[Doug Schaefer <cdtdoug@xxxxxxxxx>]

This is philosophical :).

The real question is what is the CDT? Is the CDT the thing that people
download as part of the C/C++ IDE? Is is the entire master zip? I
believe from the Eclipse EMO perspective, it is the master zip which
EDC is currently part of.

Technically, the API decision is plug-in by plug-in. You could
up-version the EDC plug-ins to signal API changes. Philosophically,
though, should that be a part of CDT 7.0.1? No, it should not. There
are no API changes allowed in a maintenance release.

At any rate, I won't hide my disappointment here. Components are not
free to define their own release schedule. Yet it appears that's what
has been requested. Over the summer, I will be proposing a few
subprojects for CDT, maybe this would be a better place for EDC to
facilitate its development cycle.

On Thu, Jun 17, 2010 at 10:40 AM, John Cortell <rat042@xxxxxxxxxxxxx> wrote:
> This can quickly become a philosophical debate. Do we stand as one, or are
> we autonomous components? I wouldn't touch that with a ten foot pole. Civil
> Wars have resulted from asking such questions :-)
>
> At 09:15 AM 6/17/2010, Madan Teodor-TEMADAN1 wrote:
>>
>> As far as I know, bundle versioning should have a separate life-cycle
>> representing the API evolution then product versioning.
>>
>> If CDT product version would stick to 7.0.1 that does not mean that EDC
>> bundle/feature could not move from 1.0 to 1.1 or even 2.0.
>> Though in this case you should be careful with how you would make
>> distinction of EDC on head or on 7_0 branch.
>>
>> Teo
>> -----Original Message-----
>> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
>> On Behalf Of David.Dubrow@xxxxxxxxx
>> Sent: Thursday, June 17, 2010 4:57 PM
>> To: cdt-dev@xxxxxxxxxxx
>> Subject: Re: [cdt-dev] RE: API tooling for CDT 8.0 and CDT 7.0.1
>>
>> I understand there are benfits to API tooling, but the restriction Doug
>> mentioned that no new API can be added for 7.0.1 because it's only a
>> maintenance release (same minor version) hamstrings development for us
>> since we plan our first EDC-based release on 7.0.1.
>>
>>
>> On 6/17/10 8:51 AM, "ext John Cortell" <rat042@xxxxxxxxxxxxx> wrote:
>>
>> > The API tooling is very useful, even for something that is in flux.
>> > Among other things, it's critical for identifying what is being
>> > exposed as API. Prior to it, such identification required proactive,
>> > manual inspection. Now, you can code away and not worry about
>> > accidentally introducing API.
>> > And that's just one
>> > of many benefits API tooling brings to the table.
>> >
>> > The EDC plugins are configured for API tooling and I'd give a big -1
>> > to undoing that.
>> >
>> > John
>> >
>> > At 08:50 AM 6/17/2010, David.Dubrow@xxxxxxxxx wrote:
>> >> I thought EDC was exempt from API tooling issues for now since it's
>> >> still in early development and likely to change quite a bit for some
>> >> time. To some degree, the CDT 7.0 release is an arbitrary point in
>> EDC development, right?
>> >>
>> >> --David Dubrow
>> >>
>> >>
>> >> On 6/17/10 8:46 AM, "ext Doug Schaefer" <cdtdoug@xxxxxxxxx> wrote:
>> >>
>> >>> Actually, 7.0.1 should still be against the 6.0 baseline, no? There
>> >>> are no API changes at all allowed on the maintenance stream.
>> >>>
>> >>> On Thu, Jun 17, 2010 at 9:35 AM, Marc Khouzam
>> >>> <marc.khouzam@xxxxxxxxxxxx>
>> >>> wrote:
>> >>>> I've updated our policy wiki with this procedure.
>> >>>> http://wiki.eclipse.org/CDT/policy
>> >>>>
>> >>>>
>> >>>> ________________________________
>> >>>> From: cdt-dev-bounces@xxxxxxxxxxx
>> >>>> [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Marc Khouzam
>> >>>> Sent: Thursday, June 17, 2010 8:29 AM
>> >>>> To: 'CDT General developers list.'
>> >>>> Subject: [cdt-dev] API tooling for CDT 8.0 and CDT 7.0.1
>> >>>>
>> >>>> Hi all,
>> >>>>
>> >>>> just a reminder that now that we have moved to developing new
>> >> CDT versions,
>> >>>> you should update
>> >>>> your API baselines to the CDT 7.0 code for both 8.0 and 7.0.1.
>> >>>>
>> >>>> There has already been some commits to CDT 8.0 that broke API
>> >>>> tooling :-)
>> >>>>
>> >>>> Here is how I do it, takes 30 seconds:
>> >>>>
>> >>>> 1- download CDT 7.0 from
>> >>>>
>> >> http://download.eclipse.org/tools/cdt/builds/7.0.0/I.I201006141710/in
>> >> dex.html
>> >>>> 2- unzip it in some directory (I create a CDT7.0 dir)
>> >>>> 3- in eclipse go to Preferences->Plug-in Development->API Baselines
>> >>>> 4- Press the Add Baselines... button
>> >>>> 5- Name your new baseline (I use CDT7.0)
>> >>>> 6- Choose the directory of point #2 and press OK
>> >>>> 7- make sure the new baseline is the selected one.
>> >>>>
>> >>>> Thanks
>> >>>>
>> >>>> Marc
>> >>>>
>> >>>>
>> >>>> _______________________________________________
>> >>>> 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
>