Hi Edy,
> On 31 Jan 2019, at 11:23, Eduard Moraru wrote:
>
> Hi,
>
> What I don't like about this is the fact that, because of the rule that
> says that all closed issues must have assigned documentation links
> (including in the RN), the developer now has to make yet another decision,
> and a
Hi Denis,
> On 31 Jan 2019, at 09:24, Denis Gervalle wrote:
>
> Hi Vincent,
>
> Maybe, we need to introduce an Advanced checkbox in the RN, and publish it in
> two parts. One part would be expanded, and very visible, and the other one,
> need some action from the user to be shown. Normal
Hide devs,
From this ongoing discussion, I see the following points being discussed:
* Problem 1: Quality of individual change doc in the RN, especially for
developers ones.
* Problem 2: Cost of creating the RN vs real need and what would be enough. For
a given doc budget how do we spend it
Hi,
What I don't like about this is the fact that, because of the rule that
says that all closed issues must have assigned documentation links
(including in the RN), the developer now has to make yet another decision,
and a pretty subjective one, this time. You (the dev) need to decide if the
> On 31 Jan 2019, at 09:24, Denis Gervalle wrote:
>
> Hi Vincent,
>
> Maybe, we need to introduce an Advanced checkbox in the RN, and publish it in
> two parts. One part would be expanded, and very visible, and the other one,
> need some action from the user to be shown. Normal users will
Hi Vincent,
Maybe, we need to introduce an Advanced checkbox in the RN, and publish it in
two parts. One part would be expanded, and very visible, and the other one,
need some action from the user to be shown. Normal users will therefore get
what you expect, and more interested people still
> On 30 Jan 2019, at 18:09, Marius Dumitru Florea
> wrote:
>
> Yes, it looks nice, but SonarQube is a different kind of product. I don't
> think it's a development platform like us..
Yes (although you could argue about that). However I still believe that to
attract and keep users (which is
Yes, it looks nice, but SonarQube is a different kind of product. I don't
think it's a development platform like us..
On Wed, Jan 30, 2019 at 6:41 PM Vincent Massol wrote:
> BTW I really like the quality of the SonarQube release notes:
> * Not too much (nobody reads when there’s too much)
> *
BTW I really like the quality of the SonarQube release notes:
* Not too much (nobody reads when there’s too much)
* Only document important highlights and make the RN nice for them (nice
screenshots, nice doc)
https://www.sonarqube.org/sonarqube-7-6/
WDYT?
Thanks
-Vincent
> On 25 Jan 2019, at
I agree with Caty, but by "Developers" I understand "Extension Developers",
who might be interested in new Java APIs (e.g. related to writing
Java-based rendering macros).
Of course, we should provide examples in the RN.
Thanks,
Marius
On Wed, Jan 30, 2019 at 12:41 PM Ecaterina Moraru (Valica) <
I would also keep the term "Developers". Not sure why we would change that
name. XWiki is a development platform, we have users that are developers.
Thanks,
Caty
On Wed, Jan 30, 2019 at 12:37 PM Simon Urli wrote:
> Hi Vincent,
>
> On 30/01/2019 09:05, Vincent Massol wrote:
> > Hi guys,
> >
> >
Hi Vincent,
On 30/01/2019 09:05, Vincent Massol wrote:
Hi guys,
No opinions ?
Thanks
-Vincent
On 25 Jan 2019, at 09:31, Vincent Massol wrote:
Hi devs,
Context
===
It’s been since we’ve deviated from the original purpose of the Release Notes
by also adding developer-oriented release
Hi guys,
No opinions ?
Thanks
-Vincent
> On 25 Jan 2019, at 09:31, Vincent Massol wrote:
>
> Hi devs,
>
> Context
> ===
>
> It’s been since we’ve deviated from the original purpose of the Release Notes
> by also adding developer-oriented release notes.
>
> The goal of the Release
> On 25 Jan 2019, at 09:31, Vincent Massol wrote:
>
> Hi devs,
>
> Context
> ===
>
> It’s been since we’ve deviated from the original purpose of the Release Notes
> by also adding developer-oriented release notes.
>
> The goal of the Release Notes was to **highlight** important
Hi devs,
Context
===
It’s been since we’ve deviated from the original purpose of the Release Notes
by also adding developer-oriented release notes.
The goal of the Release Notes was to **highlight** important novelties for our
**users**, because looking at the JIRA list is too technical
15 matches
Mail list logo
