Hi Lars,
>How often does that happen and is it really that much of
>a problem for the person to Eclipse to see the Revision information?
We face this problem very often, during every milestone week and before the release when we test and review the N&N content and website.
We need the bug number during testing to find more details & test cases, add comments and open follow-up dependent bugs.
There are also cases when revision information of original entries is overwritten by another entry. Sometimes multiple entries are committed with a single commit. So, having the bug number in the entry itself is required.
Now with faster milestones/releases, we hit this problem very frequently and spend a lot of time in finding the associated bug numbers.
>I'm not sure if ease of use justifies the additional effort for the
>news creator.
Most of the times, a new entry is copied from an existing entry. Once the comment has been added to an existing entry, the copied entry will have the comment. The only change required from the news creator is changing the bug number which he already has for adding to the commit message.
IMHO this is a small change. To make this change easier, I volunteer to add any missing bug numbers in the entries for 4.10 M1 so that entries in M3 and later can follow suit.
Thanks & Regards,
Lakshmi
----- Original message -----
From: Lars Vogel <lars.vogel@xxxxxxxxxxx>
Sent by: eclipse-dev-bounces@xxxxxxxxxxx
To: "General development mailing list of the Eclipse project." <eclipse-dev@xxxxxxxxxxx>
Cc:
Subject: Re: [eclipse-dev] New and Noteworthy instructions updated
Date: Mon, Sep 17, 2018 3:38 PM
Hi Lakshmi,
> The bug number comment will be visible in the source view and we can easily find the bug without having to open the news repo.
I'm not sure if ease of use justifies the additional effort for the
news creator. How often does that happen and is it really that much of
a problem for the person to Eclipse to see the Revision information?
I'm -1 on this process change, if that is important for you or the
team, please bring this to the PMC.
Best regards, Lars
On Mon, Sep 17, 2018 at 11:54 AM, Lakshmi P Shanmugam
<lshanmug@xxxxxxxxxx> wrote:
> Hi Lars,
>
>>can we change the requirement "add a link to the associated bug number
>>as a comment" to the requirement to include the bug number in the
>>commit message for the N&N entry?
>
> Although this is not added as a requirement, we already do this. Most of the
> entries have the bug number in the commit message.
> I'll add this to the instructions page as well.
>
>>I don't like adding invisible content to the N&N and I think the
>>commit message combined with "Show revision information" in Eclipse
>>serves the same purpose.
>
> Finding the bug for an entry becomes a problem when looking at the news
> website using the browser.
> The bug number comment will be visible in the source view and we can easily
> find the bug without having to open the news repo.
>
> Thanks & Regards,
> Lakshmi
>
>
> ----- Original message -----
> From: Lars Vogel <lars.vogel@xxxxxxxxxxx>
> Sent by: eclipse-dev-bounces@xxxxxxxxxxx
> To: "General development mailing list of the Eclipse project."
> <eclipse-dev@xxxxxxxxxxx>
> Cc:
> Subject: Re: [eclipse-dev] New and Noteworthy instructions updated
> Date: Sun, Sep 16, 2018 3:50 PM
>
> Hi Lakshmi,
>
> can we change the requirement "add a link to the associated bug number
> as a comment" to the requirement to include the bug number in the
> commit message for the N&N entry?
>
> I don't like adding invisible content to the N&N and I think the
> commit message combined with "Show revision information" in Eclipse
> serves the same purpose.
>
> Best regards, Lars
>
>
>
> On Fri, Sep 14, 2018 at 1:37 PM, Lakshmi P Shanmugam
> <lshanmug@xxxxxxxxxx> wrote:
>> Hi all,
>>
>> The instructions for the rolling New and Noteworthy document has been
>> updated for Eclipse 4.9 and later releases. Please read the updated
>> instructions.html.
>> Please note that starting from 4.10, the developers are requested to add a
>> link to the associated bug number as a comment in the N&N entry for
>> further
>> reference. See more details here.
>>
>> Thanks & Regards,
>> Lakshmi
>>
>>
>> _______________________________________________
>> eclipse-dev mailing list
>> eclipse-dev@xxxxxxxxxxx
>> To change your delivery options, retrieve your password, or unsubscribe
>> from
>> this list, visit
>> https://dev.eclipse.org/mailman/listinfo/eclipse-dev
>
>
>
> --
> Eclipse Platform project co-lead
> CEO vogella GmbH
>
> Haindaalwisch 17a, 22395 Hamburg
> Amtsgericht Hamburg: HRB 127058
> Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
> USt-IdNr.: DE284122352
> Fax (040) 5247 6322, Email: lars.vogel@xxxxxxxxxxx, Web:
> http://www.vogella.com
> _______________________________________________
> eclipse-dev mailing list
> eclipse-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/eclipse-dev
>
>
>
>
> _______________________________________________
> eclipse-dev mailing list
> eclipse-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/eclipse-dev
--
Eclipse Platform project co-lead
CEO vogella GmbH
Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Fax (040) 5247 6322, Email: lars.vogel@xxxxxxxxxxx, Web: http://www.vogella.com
_______________________________________________
eclipse-dev mailing list
eclipse-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipse-dev
