Re: [eclipse-dev] Eclipse Juno M6 N&N needed by Wed. March 14 - Instruct

[Deepak Azad <deepak.azad@xxxxxxxxxx>]

Is everyone supposed to directly edit the one file mentioned? Given that
everyone would be writing N&N on the same day wouldn't this result in merge
conflicts for many people and as a result wasted time?

I think a better model could be to create a directory per component and
each component creates their separate N&N which are merged in the end, as
used to happen so far.

Deepak



From:	John Arthorne <John_Arthorne@xxxxxxxxxx>
To:	eclipse-dev@xxxxxxxxxxx
Date:	03/08/2012 01:14 AM
Subject:	[eclipse-dev] Eclipse Juno M6 N&N needed by Wed. March 14 -
            Instructions Changed!!
Sent by:	eclipse-dev-bounces@xxxxxxxxxxx



Committers,

NOTE! THIS IS NOT THE USUAL EMAIL. PLEASE READ IT.

Please coordinate with your component team lead and push your new and
noteworthy items for Eclipse Juno (3.8 & 4.2) M6 by Wed. March 14. I'll
edit your contributions to produce an HTML document that will accompany the
milestone build when it wraps on Friday.

Please push your new & noteworthy items directly to the git repository:

http://git.eclipse.org/c/platform/eclipse.platform.news.git/tree/platform/4.2/M6/eclipse-news-M6.html


This doesn't mean you can wait until Friday to push your contributions. The
document still needs to be edited and exported to the downloads page which
takes some time. Changes pushed to the New & Noteworthy after we promote
the build will not be included.

Thanks,
John_______________________________________________
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