Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclemma-dev] EclipseCon Europe 2016 Meeting minutes

And continuing the discussion about Oxygen release train - below is my proposal regarding action plan.

Given that
- "First-time participants are expected to be in an aggregation build by M4, at the latest" [1]
- date for Oxygen M4 +0 is not that far = 9 Dec 2016 [2]
- will be really a shame to miss this train, btw, Marc, due to delay of train from Ludwigsburg missed all subsequent trains on my way back to France from EclipseCon ;)
- it might take some time before we'll be ready for first publicly available release under Eclipse Foundation umbrella
- as far as I understand - project can participate in release train without inclusion into EPP

and looking on EGerrit 1.0.0 [3]:
- stated intent to join Neon Simultaneous Release = 3 Nov 2015 [4]
- joined using milestone = 6 Nov 2015 [5], prior to Neon M4 +0 = 18 Dec 2015 [6]
- narrowed down the version added to the train = 31 Jul 2016 [7], btw I think that associated bug [8] can be closed
- had graduation and release review = 15 Jun 2016 [9], followed by release = 22 Jun 2016 as for Neon
- prior to that had initial release 0.1.0.241 = 30 Oct 2015 [10]

I'm proposing
- right now create release plan 3.0.0 and to state intent to join Oxygen release train with it
- use milestone for aggregation build and promise to narrow down the version of EclEmma added to the train
- might turn out that it actually will be 3.1.0 (taking into account "externally visible" changes such as support of Java 9 that depends on JaCoCo, addition of High Resolution Icons, e
tc)

In order to work properly towards release and finally inclusion into Oxygen EPP without rush.

WDYT - does this sound like a good and doable plan?

Best regards,
Evgeny

[1] https://wiki.eclipse.org/SimRel/Simultaneous_Release_Requirements#Integrate_Early_and_Often
[2] https://wiki.eclipse.org/Oxygen/Simultaneous_Release_Plan#Schedule
[3] https://projects.eclipse.org/projects/technology.egerrit/releases/1.0.0-neon
[4] https://dev.eclipse.org/mhonarc/lists//cross-project-issues-dev/msg12602.html
[5] https://bugs.eclipse.org/bugs/show_bug.cgi?id=481441
[6] https://wiki.eclipse.org/Neon/Simultaneous_Release_Plan#Schedule
[7] http://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/commit/?id=f6b9b5bc552bffee790a4ac4e000683895c92bb0
[8] https://bugs.eclipse.org/bugs/show_bug.cgi?id=481634
[9] https://projects.eclipse.org/projects/technology.egerrit/reviews/1.0.0-neon-release-review
[10] https://projects.eclipse.org/projects/technology.egerrit/releases/0.1.0.241


On Sat, Oct 29, 2016 at 3:26 AM Evgeny Mandrikov <mandrikov@xxxxxxxxx> wrote:
Hi all,

Below are meeting minutes from EclipseCon Europe 2016:

Due to renaming of packages from "com.mountainminds.eclemma.*" to "org.eclipse.eclemma.*" we break APIs, hence first release under Eclipse Foundation umbrella should have 3.0 version number.

We should keep compatibility with Eclipse 3.8, but increase of major version is a good opportunity to end support of older versions [1].

Work on P2 metadata should be continued by sending an email to the P2 mailing list [2].

Most likely we will not sign code in future releases of JaCoCo [3], hence we should start work towards addition of JaCoCo in Eclipse Orbit.

Transfer of domains and DNS records for eclemma.org and eclemma.com has failed on a first try, but thanks to Marc and Denis this was reverted quickly.
Second attempt was planned and should be smoother [4].

Site migration:
- prepare extracted JaCoCo site at [5]
- prepare extracted EclEmma site at [6]
- then switch to them [7] and [8] respectively
- thanks to Eclipse Foundation infrastructure we can setup redirects, so that existing links won't be broken

We don't believe that stackoverflow deserves any special treatment from us, because of  presence of a good traffic and interactions between developers and users in the current JaCoCo and EclEmma Users Mailing List [9].

According to discussion with Wayne:
To be part of an EPP package we should leave the incubation phase.
Incubation phase ends by graduation review that can be combined with release review.
Graduation is supposed to be easy for us.

It was a great pleasure to perform presentation together. We hope to find a chance to do that again.

And of course it was a great pleasure to be at EclipseCon and meet other Eclipse Community members.

Hope I haven't forgotten anything. Do not hesitate to supplement and correct, if this is not the case.



Back to the top