[tracecompass-dev] Neon Development

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[tracecompass-dev] Neon Development

From: Bernd Hufmann <bernd.hufmann@xxxxxxxxxxxx>
Date: Thu, 25 Jun 2015 11:23:51 -0400
Delivered-to: tracecompass-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/tracecompass-dev>
List-help: <mailto:tracecompass-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/tracecompass-dev>, <mailto:tracecompass-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/tracecompass-dev>, <mailto:tracecompass-dev-request@eclipse.org?subject=unsubscribe>
Organization: Ericsson AB
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0

Hi

As previously discussed and agreed, master branch will be used for themain development for Neon and we'll allow API breakage for that. ForNeon Trace Compass plan to release 2.0.

I would like to propose that major API breakage is backed-up by abugzilla bug so that the API design can be discussed by developers usingthis API. With major API breakage I mean that core functions aresignificantly changed or even removed.


Any thoughts?

Thanks
Bernd

Follow-Ups:
- Re: [tracecompass-dev] Neon Development
  - From: Alexandre Montplaisir
- Re: [tracecompass-dev] Neon Development
  - From: Matthew Khouzam

Prev by Date: Re: [tracecompass-dev] Branching for 1.1
Next by Date: Re: [tracecompass-dev] Neon Development
Previous by thread: [tracecompass-dev] Branching for 1.1
Next by thread: Re: [tracecompass-dev] Neon Development
Index(es):
- Date
- Thread

Breadcrumbs