Hi,
All Papyrus-RT committers should have write access to the website; this is not restricted to project leaders. For standard
contributors, you can request the migration to Gerrit on Bugzilla/Community/Gerrit:
https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Community&component=Gerrit
This won’t break compatibility with the current repo (Although ‘remote’ git URLs will need to be updated, for the committers
who already cloned the git repo. You won’t be able to ‘push’ to the Git URLs anymore after the migration)
Regards,
Camille
De : papyrus-rt-dev-bounces@xxxxxxxxxxx [mailto:papyrus-rt-dev-bounces@xxxxxxxxxxx]
De la part de Peter Cigéhn
Envoyé : mardi 12 avril 2016 08:51
À : papyrus-rt developer discussions <papyrus-rt-dev@xxxxxxxxxxx>
Objet : Re: [papyrus-rt-dev] repositories, installations, etc.
As Remi already pointed earlier on the mailing list, the website repo probably should be hooked up with Gerrit to ensure that anyone can contribute updates/changes/improvements to the website.
This is also how the website repo for the Papyrus project is configured.
I guess the Eclipse webmasters should be able to help out with getting that configured.
On 12 April 2016 at 00:21, charles+zeligsoft.com <charles@xxxxxxxxxxxxx> wrote:
The web site would be a better location as the URL would be less intimidating.
I could do this if I had write-access to the repo… I think only the project leaders have such access - I’ll check.
/Charles
Well, since we are discussing to place the project setup files (for developers) in the website repo (and not include it at all in the source code repo, to avoid issues experienced with maintaining
the setup file for Papyrus in relations to maintenance branches), I guess that we probably could/should include the discussion of moving the product setup files to the website repo as well (and thus also publishing it on the Papyrus-RT website).
Then end-users will not have any plain resource links to the Git repo (which someone on the Papyrus mailing list pointed out as being "strange"), but instead they will reference a "normal" file
on the Papyrus-RT website which probably makes more sense.
With that approach we can remove the "offending" directory completely from the source code repo for Papyrus-RT after the 1.0 release.
On 11 April 2016 at 17:27, charles+zeligsoft.com <charles@xxxxxxxxxxxxx> wrote:
Hi Peter,
Could we temporarily have two directories?
-
A new directory for Neon/1.0 that conforms to Céline’s rules and that would only allow installation of both 0.7.x and 0.8.x Neon-based releases
-
The current directory uniquely for the 0.7.x releases that are currently in use (i.e., no 0.8.x+ installations). After the Papyrus-RT 1.0 release, we can then remove the old directories and that link for the old setup files.
I would modify the installation instructions to indicate that the old setup file is deprecated and will be removed after 1.0 is released and that users should move to the new setup file, leaving plenty of time for people to move.
After 1.0, the installation instructions would be changed to remove mention of the old setup files.
And, as this is a wiki, the old pages would still be kept anyway…
Yes, there have been quite some discussion about the *product* setup files (for end-users) and *project* setup files (for developers). Both are currently placed in the directory that you refer
to.
Initially Celiné proposed to change the name of this directory, but as I pointed out in the Gerrit change for that update we needed your input to whether this was okay or not, since it would
have an impact on the installation instructions, as well as users that already have followed the instructions and now have the Eclipse installer setup to reference the current location (those references will become broken if we change the directoy name). So
it is not about changing or impacting the setup file itself, it is the external reference to the setup file that will change if we change the name of the directory in which it is placed. Since then Celiné have reverted that proposed change, but I have not
seen any response to Celiné why she reverted or if she is okay with keeping the current name.
I think that we need Celíné's input regarding her view on the name of this directory, and if she still feels that it is important to change (Christian indicated that he could not see any issue
with having a - in the name, which was what Celiné argued was not allowed to the naming rules of directories for plugin projects). And we need your input if it is okay to change the name. It will have an impact on the Wiki (not the setupfile itself). And do
we see an issue with impacting any possible existing users that already have setup their Eclipse Installer to reference the setup file, since those users will be forced to setup Eclipse Installer once again. I cannot judge if we see that as an issue or not.
On 11 April 2016 at 16:47, charles+zeligsoft.com <charles@xxxxxxxxxxxxx> wrote:
I’ve seen many messages on this mailing lists talking about builds, repositories, and installation setup files.
I do understand that this is work in progress and, I believe, that the installation setup files are for developer (project) setups.
However, there are two end user-targeted, product installation setup available on the wiki, as part of the user and tester guides.
It may be that, because of all the current refactoring/reorganizing work, these end-user-targeted installation no longer work, and that would obviously be a problem.
Please let me know if that happens so I can update these setup files. Or simply correct the setup files yourselves, they are in:
* org.eclipse.papyrus-rt/releng/org.eclipse.papyrus-rt.oomph/setups/
Sincerely,
Charles Rivet
Senior Product Manager
charles@xxxxxxxxxxxxx
_______________________________________________
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
_______________________________________________
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
|
