[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Hi Axel
This should have migrated to mdt-ocl.dev from the outset.
If it was my choice:
Yes. I would put everything from org.eclipse.ocl.releng under
org.eclipse.ocl.git/releng.
But, I have no experience of GIT, so I would certainly see what other
projects were doing.
And I would like to know what our diligent releng thinks.
Regards
Ed
On 06/06/2011 19:16, Axel Uhl wrote:
Ok, then what about directory structures? Shall everything from
org.eclipse.ocl.releng go straight under org.eclipse.ocl.git/releng?
If not, then where?
-- Axel
On 06/06/2011 08:11 PM, Ed Willink wrote:
Hi Axel
The rationale for a separate releng was to be able to have a
less-privileged committer who could not 'corrupt' the main code.
It has been very clear in the last month that the releng is the most
trusted committer, since releng must be able to commit without review,
so I see no need for a separate repository.
Regards
Ed
On 06/06/2011 19:03, Axel Uhl wrote:
Ed,
what about org.eclipse.ocl.releng which currently resides next to
org.eclipse.ocl? Would you want its contents put under
gitroot/mdt/org.eclipse.ocl.git/releng? Or would you want a separate
git repository for that?
Best,
-- Axel
On 06/06/2011 06:24 PM, Ed Willink wrote:
Hi Axel
From looking at other projects: gef/mwe/xtext, I think we should be
/gitroot/mdt/org.eclipse.ocl.git
In general, we seem to trail itemis for modern technology so it's
always
worth looking at Xtext.
I'm inclined to keep plugins etc the same just split off features.
Releng can be a sibling of plugins, but again first choice is the same
as Xtext.
Regards
Ed
On 06/06/2011 17:13, Axel Uhl wrote:
I'm writing the git migration mail later tonight (currently seeing a
doctor for a sore knee). You should decide about repo structure.
Should it be under gitroot/mdt/org.eclipse.ocl to prepare for the
migration of other mdt projects?
Should we stay with examples, plugins, tests for now? Where should
the
relent stuff go.
Once we've decided, we open a bug for git migration so the webmaster
can perform repository creation and initial import.
Best,
-- Axel
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
Ed Willink <ed@xxxxxxxxxxxxx> wrote:
Hi
Sorry. I download the Update site ZIP from Hudson and then do Install
New Software from it. Then Help Contents ...
Are we ready to go on GIT. Do I need to request a repository?
Regards
Ed
On 06/06/2011 16:49, Axel Uhl wrote:
> What about my first question ("what's the easiest and fastest
way to
> review the docs?")? I've currently an Indigo RC2 installed into
which
> I can't seem to update the latest nightly build of OCL for some
> dependency problem. Please advise.
>
> -- Axel
>
> On 6/6/2011 5:40 PM, Ed Willink wrote:
>> Hi Axel
>>
>> Sorry, only just got back from work.
>>
>> Obviously everything's good for a review. The top level stuff is
most
>> important since that's wha
t
newbies see. I highlighted the '2 Eclipses'
>> section as something that was more than 'facts'.
>>
>> Regards
>>
>> ed
>>
>> On 06/06/2011 12:24, Axel Uhl wrote:
>>> Ed,
>>>
>>> what's the easiest and fastest way to review the docs? I may have
>>> about an hour before 16:30 to review some stuff. Which part
deserves
>>> the most attention?
>>>
>>> -- Axel
>>>
>>> On 6/6/2011 10:23 AM,bugzilla-daemon@xxxxxxxxxxx wrote:
>>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=304642
>>>> Product/Component: MDT / OCL
>>>>
>>>> --- Comment #27 from Edward Willink<ed@xxxxxxxxxxxxx> 2011-06-06
>>>> 04:23:13 EDT ---
>>>&
gt;
Created attachment 197373
>>>> --> https://bugs.eclipse.org/bugs/attachment.cgi?id=197373
>>>> Delegates and Partial OCLstdlib syntax documentation
>>>>
>>>
>>
>>
>
------------------------------------------------------------------------
No virus found in this message.
Checked by AVG - www.avg.com <http://www.avg.com>
Version: 10.0.1382 / Virus Database: 1511/3683 - Release Date:
06/05/11
