Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [gef-dev] GitHub migration, Oxygen release plans
Hi all,

thank you for the great work, Alexander!

+1
I like the proposals very well, especially because changing the names will allow for associating the project name with the codebase of the current version again.

Best regards,
Matthias



2016-06-04 9:58 GMT+02:00 Alexander Nyßen <nyssen@xxxxxxxxx>:
Hi team,

while we have already agreed on migrating our code base from git.eclipse.org to GitHub (replacing the up to now mirrored repositories there), we had not clarified all the details. I want to initiate the migration soon after the Neon release (unfortunately there was no time to do so earlier) and had some thoughts about it in the mean time: 

1) We had discussed earlier whether to migrate only the GEF4 code base, but having considered this in detail in the last weeks, I would propose to migrate both Git repositories (GEF 3.x and GEF4). First, because this is the intended policy of the Eclipse foundation to have all repositories in a single place, so we would need an exception otherwise. Second, because, as GEF 3.x is in pure maintenance mode now, hosting its code base at GitHub would give adopters an easier chance to maintain a fork, if needed.

2) As GEF4 supersedes GEF 3.x, I would like to take the migration as an opportunity to ‚flip the switch‘ during the Oxygen train. That is, I would like to use 'eclipse/gef‘ accordingly as the name of GitHub ‚GEF4' repository, and introduce 'eclipse/gef3' as name for the repository that contains the old GEF 3.x code base. 

3) Further, I would propose to plan another major release (5.0.0) for Oxygen, and there adopt the ‚GEF4' code base to the original project namespace, migrating all ‚GEF4' bundles and features from the org.eclipse.gef4.* namespace to the original org.eclipse.gef.* namespace (and adopting their versions to 5.0.0 instead of 2.0.0). This could be done without colliding with the GEF 3.x bundles and features (so we would not have to rename these).

4) Last, I would propose to adopt our Hudson build jobs and update site urls, as well as artifacts names to use gef3 for the old code base, and gef for the new one.

What do you think? Comments welcome!

Regards,
Alexander
--
Dr. Alexander Nyßen
Dipl.-Inform.
Principal Engineer

Telefon: +49 (0) 231 / 98 60-202
Telefax: +49 (0) 231 / 98 60-211
Mobil: +49 (0) 151 /  17396743

http://www.itemis.de 
alexander.nyssen@xxxxxxxxx 

itemis AG
Am Brambusch 15-24
44536 Lünen

Rechtlicher Hinweis:

Amtsgericht Dortmund, HRB 20621

Vorstand: Jens Wagener (Vors.), Wolfgang Neuhaus

Aufsichtsrat: Prof. Dr. Burkhard Igel (Vors.), Michael Neuhaus, Jennifer Fiorentino




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



-- 
Matthias Wienand
Fachinformatiker

Telefon: +49 231 9860 202
Telefax: +49 231 9860 211
Mobil:   +49 152 26802283

matthias.wienand@xxxxxxxxx
http://www.xing.com/profile/Matthias_Wienand2
http://www.itemis.de

itemis AG
Niederlassung Lünen
Am Brambusch 15-24
44536 Lünen

Rechtlicher Hinweis:
Amtsgericht Dortmund, HRB 20621
Vorstand: Jens Wagener (Vors.), Wolfgang Neuhaus, Dr. Georg Pietrek, Jens Trompeter
Aufsichtsrat: Prof. Dr. Burkhard Igel (Vors.), Michael Neuhaus, Jennifer Fiorentino

Back to the top