Eclipse Community Forums: Papyrus » Will there be a Papyrus SR2b?...

Home » Modeling » Papyrus » Will there be a Papyrus SR2b?...(...because there seems to be 0.10.2 nightly builds still coming...)

Show: Today's Messages :: Show Polls :: Message Navigator

Will there be a Papyrus SR2b?... [message #1268197]

Mon, 10 March 2014 07:16

Tomas Sandkvist

Messages: 149
Registered: October 2013

Senior Member

I had some issues with broken imports which Camille fixed in a snap through a nightly build. And I have seen newer builds as well, but I thought there would be no more development in this branch, focusing the effort for the Luna release in the summer?

So, you wizards of programming, how does this work? If there would be found "too many" things to correct will you make another SR2(b,c,d...) release? If not is there a way to collect the changes made in the nightly builds because there might be some fix one or two of us users actually could benefit from?

I've tried to figure out how to scan off the Bugzilla by filtered searches (see another post here), but I can't see how to find the relationship between a fixed bug/added feature and builds, if any. Perhaps I should use nothing but a date filter?

Regards,
Tomas Sandkvist

Report message to a moderator

Re: Will there be a Papyrus SR2b?... [message #1268291 is a reply to message #1268197]

Mon, 10 March 2014 09:58

Camille Letavernier

Messages: 952
Registered: February 2011

Senior Member

Hi Tomas,

There is no way to associate bugs to builds, because the Bugzilla task can be related to either Luna or Kepler, or both. We try to indicate (in the comments) the branch to which the commit applies (e.g. Commit abc1234 in master, 4321abc in kepler), but that's a good practice more than an absolute rule.

We usually keep building nightly builds after the SR2 release, for a few weeks/months, but it doesn't contain too many commits. Whether we provide a SR2b or a SR3 really depends on the user requests and needs, and time we have for releasing a new build (Often, we don't have too much time for a SR3; so unless there is a critical/blocker issue which makes SR2/SR2a unusable, we focus on Luna milestones).

The best way to retrieve the builds/commit mapping is from the Git repository. We have one tag per build, and each commit is (should be) associated to a Bugzilla task.

Regards
Camille

Camille Letavernier

Report message to a moderator