Re: [mylyn-docs-dev] Branch for Neon.2 contribution?

[David Green <david.green@xxxxxxxxxxx>]

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: 

https://git.eclipse.org/r/#/c/83024/ (Refactor editors into separate feature for standalone use)

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

--

David Green | VP of Architecture | Tasktop

email: david.green@xxxxxxxxxxx