|
Hi,
According to this mail [1] on the cross-project-issues-dev mailing list, the staging repository for Neon.2 RC1 is ready.
When I look at the Mylyn Wikitext Feature there, I see that the version is "2.9.0.v20160601-1831" and not in the "2.11.0.xxx" range.
As I wrote in my previous email, I am not sure what the required steps are, but I would appreciate to have the latest version from master contributed with Neon.2.
Thank you in advance,
Jeremie
[1] https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg13864.html
Le 06.11.2016 10:42, Jeremie Bresson a écrit :
Hi David,
Thank you for your answer. It makes absolutely sense not to create too much branches for this project.
According to the Neon.2 schedule [1], the first RC release (Neon.2 RC1) should be available in 2 weeks (Friday 2016-11-18). I would be great to have the latest build included. This is the easiest way for the community try it and provide feedback.
Correct me if I am wrong, for the moment I see in the mylyn.b3aggrcon file [2], that the version 2.9.0.xxxx of wikitext is contributed for Neon. The version on the master branch of mylyn wikitext is at 2.11.0-SNAPSHOT. I am not familiar with the release train and those aggregations concepts, but I guess something needs to be corrected.
By the way, I am closing Bug 505984 [3] since no backport to an other branch is necessary.
Thank you,
Jérémie
[1] http://wiki.eclipse.org/Neon/Simultaneous_Release_Plan#Neon.2
[2] https://git.eclipse.org/c/simrel/org.eclipse.simrel.build.git/tree/mylyn.b3aggrcon?h=Neon_maintenance
[3] https://bugs.eclipse.org/bugs/show_bug.cgi?id=505984
Le 04.11.2016 16:15, David Green a écrit :
Jeremie,
Normally we'd contribute the latest version that doesn't have any significant new functionality (e.g. api breakage or major new features). This can mean just doing a normal release and contributing that.
I agree that bug 505984 should be included. Looking at commits since the last release, I only see one that has me thinking about stability:
With a little manual testing (i.e. trying WikiText out in the latest Neon development build) I'd feel confident going with a standard release, and avoid a back-port. What do you think?
David
On Tue, Nov 1, 2016 at 10:59 PM Jeremie Bresson < dev@xxxxxxxx> wrote: Hi,
Correct me if I am wrong, but I have the feeling that the version
contained in the "Neon.1" (September 2016) Update Site is the same as
with "Neon" (June 2016). I am not sure if this was intentionally or not.
I guess this is OK, because there was not a lot of activity on the
repository.
This raises the next question:
What is the plan for the Mylyn Wikitext Contribution for "Neon.2"?
Which version will be contributed and what is the corresponding Branch?
In my opinion Bug 505984 [1] should be fixed with "Neon.2", because this
NPE is ugly. If the corresponding branch is master, everything is OK. If
there is another branch, I will be happy to backport the commit.
Thank you in advance,
Jeremie
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=505984
_______________________________________________
mylyn-docs-dev mailing list
mylyn-docs-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mylyn-docs-dev
--
|
