User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-GB; rv:188.8.131.52) Gecko/20091204 Thunderbird/3.0
When a project transitions to Buckminster has little impact on other
projects. The final repos should be the same.
However, I think there will be considerable confusion if projects
transition to GIT at different times; there is already a little
confusion between CVS and SVN but fortunately few projects use SVN.
If GIT is not ready today, three weeks after Helios, then I think it
would be better for all non-incubation modelling projects to defer the
GIT migration till the day after Indigo.
To avoid confusion the PMC should make a strong recommendation to
either transition to GIT now or to transition after Indigo.
On 16/07/2010 11:29, Adolfo Sánchez-Barbudo Herrera wrote:
I'm definitely against to move to a different SCM system if they don't
provide an user friendly interface, as CVS and SVN related projects
I'm not familiar with GIT (just some conceptual knowledge) but I
suppose there is a good reason to do such transition, isn´t it ? Anyway
if it's a requirement from the PMC, I'll look into it when the project
provides a helpful UI after 0.9 release.
El 14/07/2010 14:50, Kenn Hussey escribió:
Glad that Buckminster is already part of your plans. I hope to
transition UML2 by end of summer as well. XSD is, of course, already on
Buckminster (since EMF is). That leaves BPMN2, MoDisco, Papyrus, Sphinx
(soon to be created/provisioned), and UML2 Tools.
Regarding git, I agree that the current tooling is not quite
ready for prime time. However, the 0.9 release, scheduled for end of
September, is expected to have everything people need so that they will
not have to resort to the command line interface. In the meantime, it
would be a good idea to become familiar with git and at least start
thinking about the impact that it will have on your project's
development and build processes.
We're happy to move to Buckminster; Adolfo is already working on it, so
hopefully we'll be there for M1.
I don't see GIT as part of Helios Modeling Package install, and have
just seen a GSoC email go past on improving EGit integration, so I
suspect that EGIT is not ready for prime time. I have also observed
significant concerns over GIT's bandwidth consumption on the servers.
Both EGIT and JGIT are in the incubation phase, and while they no doubt
offer useful benefits they are not essential. I would prefer to leave a
transition to EGIT till after Indigo.
On 13/07/2010 15:27, Kenn Hussey wrote:
Congratulations again on a successful Helios release! Now
the dust has settled a little bit, it's time to start thinking about
next year's release (Indigo).
At this point, I'd like to remind you that the Modeling
decided that all Modeling projects should use Buckminster for their
builds and that the Eclipse Foundation has chosen git as the preferred
SCM system going forward. Project leads, please factor these
initiatives into your plans; it would be ideal if each of you could let
the team know whether/when you plan to make these transitions. Of
course, it would be ideal to get this kind of work done sooner rather
than later, before development begins in earnest again in September.
If you have any questions or concerns, please don't