Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [papyrus-rt-dev] v0.8 release
​​
Hi,

Comments inline below.

/Peter Cigéhn

On 26 October 2016 at 15:14, charles+zeligsoft.com <charles@xxxxxxxxxxxxx> wrote:
Regarding bug 505416, I would propose the following (see inline below).


On 2016.10.26, at 03:45 , Peter Cigéhn <peter.cigehn@xxxxxxxxx> wrote:

Hi,

Regarding 505416 I am not sure how much to keep within the scope of that Bugzilla, and what we shall break out into separate new Bugzillas. Here are a few remaining issues identified during the work with this Bugzilla (and the related one regarding the Papyurs-RT Installer):

1) The version used for Designer needs to be updated (and aligned with the Oomph end-user setup). Rémi provided a Gerrit change, but it was decided to post-pone the merging of that one to post-0.8. See https://git.eclipse.org/r/#/c/83452/
<cr>
Are you sure about bug 83452 (org.eclipse.launchers feature missing linux/motif files) which is from 2005?

​The link is for a Gerrit change, not a Bugzilla. Please follow the link and you will see the Gerrit change the Rémi have proposed related to the update to version 1.0.3 of Designer.
​
 

My proposal:
  • Document the current state of RCP vs. Papyrus-RT installers (i.e., the differences) in the release notes. Could someone write up what these are and their consequences (if known)?
​I think that we first need to decide what to do regarding these three issues I have listed here, before documenting their consequences.
  • Consider the creation of a 0.8.1 version with the updated installations that provide installation parity.
We are still in incubation, so I think we can get away with describing the differences between the installer iff we have bugs to which we can point to show they will be fixed. There is already information on the download site and on the Early Adopter wiki page describing the differences in the installation capability, so we can just add to that.
</cr>

2) We need to get an updated integration build fo the custom builds of EGit and EMF Compare in place. The 0.8 RCP build used the nightly build, and the Oomph end-user setup uses the (too old) integration build (which in its turn casues the Oomph based installation to bring in the non-custom builds of EGit and EMF Compare part of the Neon.1 release). This needs to be aligned, based on updated integration builds. As I understood it from Philip, work is ongoing with providing updated integration builds of the custom builds of EGit and EMF Compare. When that has been provided, we need to update the .tpd-files to use the integration build repos instead.
<cr>
I haven’t tried the compare/merge feature yet. What is the impact on the user on leaving as is?
Based on this, we can decide to either document the impact (as above, taking advantage of incubation leeway), provide new v0.8.1 installers, or defer to 0.9.

</cr>

​Regarding the impact of having the older, non-custom builds of EGit and EMF Compare in the Ooomph based setup, I think that Philip and/or Alexandra need to answer. I myself have not tested the compare/merge feature enough either, and especially not trying to compare the behavior with the non-custom builds of EGit and EMF Compare with the latest (nightly) custom builds included in the RCP.

But the "only" thing that is needed, is to ensure that the integration p2 repos gets updated. No need to neither provide a new installer nor provide an updated setup file. Then users can update their installations (I even guess that Oomph might to this automatically if the user does not do a manual update). 

And the integration p2 repos is planned to be updated anyway (Philip indicated earlier "within 2 weeks"). We just need to track the work with getting the integration p2 repos updated.

3) The RCP still lacks the org.eclipse.platform.ide, which is part of the Oomph end-user setup, which suspectedly causes the welcome page to go missing in the RCP build. In general we need to provide some contents on the Welcome page as well, which I guess is best to be tracked with a completely separate Bugzilla. 

I guess we at least could include 1) in the scope of 505416 before we consider it to be resolved. 2) and 3) I guess it best tracked by separate Bugzillas.
<cr>
I would prefer splitting the bugs. This gives us more flexibility in determining the individual impacts of these to the current and future releases.
</cr>


/Peter Cigéhn

On 25 October 2016 at 17:05, charles+zeligsoft.com <charles@xxxxxxxxxxxxx> wrote:
There are still three bugs that need to be closed for Papyrus-RT 0.8 - let’s get these closed!



Status = Assigned:

505416  [RCP and Product] List of missing requirement for the RCP...  Celine.janssens@xxxxxxxxxxx  peter.cigehn@xxxxxxxxx  Celine.janssens@xxxxxxxxxxx  ASSI

Céline: Do you need any help in moving 505416 forward? What is still needed?
The last comment was on 10-21 and was a commit - who can review/test that?

Status = Resolved:

500287 [Releng] Build Process - Unify Codegen structure to be al... Celine.janssens@xxxxxxxxxxx Celine.janssens@xxxxxxxxxxx RESO 2016-09-30

Who can verify this fix?

503065 [RCPTT] Extract Rcptt test from the Product build Celine.janssens@xxxxxxxxxxx Celine.janssens@xxxxxxxxxxx RESO 2016-10-07

Who can verify this fix?


Regards,

Charles Rivet
Senior Product Manager, Papyrus-RT product lead


_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev


_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev


_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev


Back to the top