That is *Tuesday 6pm CEST*. I think we should not makle the 'old' repository readonly, but push one delete-all commit on master at that time. Then update the readme and point to the different repositories. We can keep the eclipse/xtext repository as the umbrella entry level repo, that provides an overview and contains the website for xtext.
Sven 2016-06-10 13:24 GMT+02:00 Sven Efftinge <[email protected]>: > Hi all, > > Miro made some good progress this week with the restructuring effort and > we would like to do the actual migration next Wednesday. > We will have to freeze (read-only) our repository the evening before at > 6pm so we can run scripts over night that will produce the individual > repositories. On Wednesday we will upload them to the new repositories. > > The old repository will stay as read-only for some time before we are > going to archive it. There are still some pending PRs which we won't be > able to discuss before that. But applying the changes on the new structure > shouldn't be a big problem. > > Also not, that some of the work needs to be done after the migration. Some > test projects for instance need to be splitted. In order to preserve > history we are going to copy them as is to more than one repository. > Afterwards we will delete the unwanted code in the individual repositories > and rename the projects if needed. > > So again the *repository will be* *read-only from Tuesday 6pm *on. > > Sven > > 2016-05-25 13:32 GMT+02:00 Moritz Eysholdt <[email protected]>: > >> Hi all, >> >> this Bugzilla ticket may serve as umbrella for all issues that need to be >> resolved for the restructuring: >> https://bugs.eclipse.org/bugs/show_bug.cgi?id=494527 >> >> regards, >> Moritz >> >> >> On 25 May 2016, at 13:16, Sven Efftinge <[email protected]> wrote: >> >> Hi all, >> >> the Xtext repository has grown a bit fat and I think it's time for diet. >> People coming to Xtext get overwhelmed by the amount of code and features >> it offers and especially for contributors it has become a bit hard to >> understand what the thousand projects are supposed to be used for. >> >> A user not interested in IDEA should not be faced with IDEA projects. A >> user not interested in Eclipse should not be faced with eclipse projects. A >> user not interested in Java-integration should not be faced with Xbase >> projects. >> >> I started a wiki page a couple of days ago, where I proposed a >> restructuring of the projects into separate git repositories [1]. Please >> have a look and give your feedback. >> >> This will also have an effect on how we build the projects. Currently we >> have a big build comprising of Buckminster, Gradle and Maven. The >> non-Eclipse projects should be built with a standard Java build system (I'd >> prefer Gradle over Maven). It should be possible to clone and build. >> >> Also it should be easy to have a workspace with those projects >> checked-out in any standard Java IDE. Currently these projects are PDE >> projects so only Eclipse works. At the same time these projects need to >> work nicely in a workspace where the Eclipse plug-ins are checked out as >> well. I.e. in that case they still need to have the PDE nature and of >> course all the core projects need to be proper OSGi bundles. >> >> The restructuring shouldn't change any API of course. >> >> We've started in a branch 'restructuring' to get the core projects >> isolated (still using Maven Tycho). We will merge this into the master >> after the release and keep working on modeling the project groups and their >> builds. At some point when we have the structure we want, we need to do the >> big repo-splitting. At that point it is important that no-one has any >> pending changes (we will send another notification) and the repository gets >> freezed. We will try to keep the history as much as possible when splitting >> up the repository into individual ones. >> >> Please let me know who is interested in participating in the doing of all >> this. >> Also please respond with the concerns you have. I know this is a big >> change and will have a big impact on the project and how we work on it. >> >> Cheers, >> Sven >> >> [1] - https://github.com/eclipse/xtext/wiki/Restructuring >> >> _______________________________________________ >> xtext-dev mailing list >> [email protected] >> To change your delivery options, retrieve your password, or unsubscribe >> from this list, visit >> https://dev.eclipse.org/mailman/listinfo/xtext-dev >> >> >> >> _______________________________________________ >> xtext-dev mailing list >> [email protected] >> To change your delivery options, retrieve your password, or unsubscribe >> from this list, visit >> https://dev.eclipse.org/mailman/listinfo/xtext-dev >> > > > > -- > Sven Efftinge > > TypeFox GmbH > Am Germaniahafen 1 > 24143 Kiel > > Sitz: Kiel, Registergericht: Amtsgericht Kiel, HRB 17385 > Managing Directors: Sven Efftinge, Moritz Eysholdt, Dr. Jan Köhnlein > -- Sven Efftinge TypeFox GmbH Am Germaniahafen 1 24143 Kiel Sitz: Kiel, Registergericht: Amtsgericht Kiel, HRB 17385 Managing Directors: Sven Efftinge, Moritz Eysholdt, Dr. Jan Köhnlein
_______________________________________________ xtext-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/xtext-dev
