| Re: [mylyn-docs-dev] Branch for Neon.2 contribution? |
Hi Sam,
Thank you for the overview. Since you do the work, it is OK to follow your schedule and the version scheme you have defined. In my opinion the only requirement as you said: information and transparency (outside your company people should be able to follow the process and your reasoning).
For the change, I have cherry-picked the commit to the branch "e_4_5_m_3_21_x". Is that correct for the 2.10.1 service release you have described?
Can someone review this change (just a cherry pick of the already approved commit): https://git.eclipse.org/r/#/c/
85465/ Thank you in advance,
Jeremie
Le 21.11.2016 21:03, Sam Davis a écrit :
Hi Jeremie,
We aren't planning to release Mylyn 3.22, which includes Docs 2.11, until April 7. Unfortunately we don't have capacity to do releases "on demand." Also, the deadline for contributing our release build to Neon.2 is in two weeks so I think it's too late to start planning a full release now anyway. However, if you can backport the fix to Docs 2.10, I can try to make time to do a 2.10.1 service release and contribute that to Neon.2. How does that sound? Would you be able to do the backporting this week?
We have generally made an effort to line up Mylyn releases with Eclipse simultaneous releases when we can and this may have set up an expectation that we will release Mylyn every time there is a simultaneous release, but that should not be assumed. However, I think we should do a better job of making the community aware of release plans. The dates are visible at https://projects.eclipse.org/projects/mylyn/governance but I haven't been very good about sending out announcements about upcoming releases (partly due to lack of any response when I do send out announcements). In the future I will announce on the mylyn-dev list when we are planning to do our next release, with a link to the release bug so people can follow along.
Thanks,
Sam
On Thu, Nov 17, 2016 at 1:20 PM, David Green <david.green@xxxxxxxxxxx> wrote:
Jeremie,Sam has been coordinating our release train participation for the past couple of years and will likely have to be involved in this. Unfortunately he's currently on vacation and won't be able to deal with it until he's back, which is sometime next week.David
On Wed, Nov 16, 2016 at 10:26 PM Jeremie Bresson <dev@xxxxxxxx> wrote: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
______________________________
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/S
imultaneous_Release_Plan#Neon. 2 [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: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 --
_______________________________________________
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
_______________________________________________
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
_________________
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 --
_______________________________________________
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
_______________________________________________
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
_______________________________________________
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