Re: [cross-project-issues-dev] Info Center for Neon.3

I'm in favor of running just ONE help center labeled "latest". We don't have an official SLA around packages. Especially when a new major release is out we stop providing builds of an older release. -Gunnar -- Gunnar Wagenknecht gun...@wagenknecht.org, http://guw.io/ > On 11. Apr 2017,

Re: [cross-project-issues-dev] Info Center for Neon.3

+1 Greg > On Apr 11, 2017, at 11:03 AM, 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

Re: [cross-project-issues-dev] Info Center for Neon.3

Hi I think so too, but I'm old fashioned and think that .1, .2, .3 should be maintenance releases. Since it was agreed that .1, .2, .3 could ship new releases, they need correspondingly new documentation. Regards Ed Willink On 11/04/2017 16:03, Denis Roy wrote: I think we

Re: [cross-project-issues-dev] Info Center for Neon.3

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

Re: [cross-project-issues-dev] Info Center for Neon.3

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

[cross-project-issues-dev] Apache Maven 3.5.0

Hi, The latest version of Maven is now available at /shared/common/apache-maven-3.5.0 to be used on HIPP/JIPPs. Once we've gathered some positive feedback that everything works as expected, we will link /shared/common/apache-maven-latest against 3.5.0. If your project does not have admin