[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [cross-project-issues-dev] Info Center for Neon.3
|
Hi Fred,
> I tend to agree. Service releases *should* not add new features or
introduce breaking changes, but mostly fix bugs.
Can you confirm the "*should*" applies only to the platform? AFAIK the
whole idea of changing from SRx style to .x style was to acknowledge
that .x releases did indeed add new features. Projects such as CDT do
release new features in .x releases. (An example for CDT is the new
debugger console in Neon.2)
Thanks,
Jonah
~~~
Jonah Graham
Kichwa Coders Ltd.
www.kichwacoders.com
On 13 April 2017 at 13:53, Frederic Gurr <frederic.gurr@xxxxxxxxxxx> wrote:
> Hi,
>
> I tend to agree. Service releases *should* not add new features or
> introduce breaking changes, but mostly fix bugs. So I guess the
> documentation can be considered to only improve from GA to the .3 release.
> For example, it's unlikely that the latest version of the info center of
> Neon (from the .3 release) contains wrong or obsolete descriptions,
> because something changed between GA and .3. Otherwise we would need a
> info center for every service release to have the most accurate
> documentation for each release.
>
> Regards,
>
> Fred
>
>
> On 11.04.2017 17:03, Denis Roy wrote:
>> I think we should have only one infocenter per major release (ie, a
>> single Neon infocenter).
>>
>> Denis
>>
>> On 04/11/2017 05:22 AM, Frederic Gurr wrote:
>>> Hi,
>>>
>>> There was no feedback in two weeks, so I consider the info center for
>>> Neon.3 done.
>>>
>>> I'd like to gather some opinions about the following question:
>>>
>>> Should there be a separate info center for every release and service
>>> release (e.g. separate info center for Neon.0, Neon.1, Neon.2, Neon.3),
>>> or should there be only one info center per release with updated content?
>>> If this has already been decided and defined somewhere, please point me
>>> to it.
>>>
>>> Regards,
>>>
>>> Fred
>>>
>>> On 28.03.2017 19:44, Frederic Gurr wrote:
>>>> Hi,
>>>>
>>>> The info center for the Neon.3 release is now available here:
>>>> http://help.eclipse.org/neon3/index.jsp
>>>>
>>>> As proposed in Bug 499411
>>>> (https://bugs.eclipse.org/bugs/show_bug.cgi?id=499411), project's
>>>> participation in the info center has changed from opt-in to opt-out.
>>>>
>>>> Compared to the Neon info center the following user
>>>> guides/documentations have been added in Neon.3:
>>>>
>>>> * ACTF Visualization SDK Developer Guide
>>>> * ACTF Visualization User Guide
>>>> * BIRT Report Developer Guide
>>>> * BPEL User Guide
>>>> * BPMN2 Modeler Table of Contents
>>>> * Data Tools Platform Plug-in Developer Guide
>>>> * Data Tools Platform User Documentation
>>>> * ECF Remote Services Developer Guide
>>>> * Eclipse Marketplace User Guide
>>>> * EEF Javadoc
>>>> * EGF Eclipse Generation Factories Guide
>>>> * EGit GitHub Documentation
>>>> * GMF Developer Guide
>>>> * LDT User Guide
>>>> * Modeling Workflow Engine Reference
>>>> * RSE User Guide
>>>> * Sequoyah User Guide
>>>> * Shell Script Editor User Guide
>>>> * Sphinx Developer Guide
>>>> * Subversive User Guide
>>>> * Tcl/Xotcl Development User Guide
>>>> * WindowBuilder Pro User Guide
>>>> * Xpand Documentation
>>>> * XSD Developer Guide
>>>> * Xtend User Guide
>>>> * Xtext Documentation
>>>>
>>>> The following user guides/documentations are included in the Neon info
>>>> center, but not in Neon.3:
>>>>
>>>> * JavaServer Faces Tooling Developer Guide
>>>> * Oomph Utilities Documentation
>>>> * PTP Developer's Guide
>>>> * XSL Tools SDK Documentation
>>>>
>>>> If any user guide/documentation should NOT be included in the Neon.3
>>>> info center or is missing in error (e.g. PTP) please comment on bug
>>>> 514345 (https://bugs.eclipse.org/bugs/show_bug.cgi?id=514345).
>>>>
>>>> If something is missing, please provide the full path and all files that
>>>> should be included.
>>>>
>>>>
>>>> Regards,
>>>>
>>>> Fred
>>>> _______________________________________________
>>>> cross-project-issues-dev mailing list
>>>> cross-project-issues-dev@xxxxxxxxxxx
>>>> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
>>>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>>>
>>> _______________________________________________
>>> cross-project-issues-dev mailing list
>>> cross-project-issues-dev@xxxxxxxxxxx
>>> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
>>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>
>> _______________________________________________
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@xxxxxxxxxxx
>> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
>> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>
> _______________________________________________
> cross-project-issues-dev mailing list
> cross-project-issues-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev