Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [wtp-dev] [wtp-releng] Actions for JSDT Git repo refactoring?

I have opened: https://bugs.eclipse.org/bugs/show_bug.cgi?id=425220

Inactive hide details for Christopher Jaun---01/09/2014 01:06:13 PM---I'm in favor of the new repo. ChrisChristopher Jaun---01/09/2014 01:06:13 PM---I'm in favor of the new repo. Chris

From: Christopher Jaun/Durham/IBM@IBMUS
To: "General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>,
Cc: wtp-dev-bounces@xxxxxxxxxxx, wtp-releng@xxxxxxxxxxx
Date: 01/09/2014 01:06 PM
Subject: Re: [wtp-dev] [wtp-releng] Actions for JSDT Git repo refactoring?
Sent by: wtp-dev-bounces@xxxxxxxxxxx





I'm in favor of the new repo.

Chris


Inactive hide details for Mickael Istria ---01/09/2014 06:04:45 AM---Just an extra question before we do anything: Shouldn't weMickael Istria ---01/09/2014 06:04:45 AM---Just an extra question before we do anything: Shouldn't we rather create  a new "webtools.jsdt" repo

From:
Mickael Istria <mistria@xxxxxxxxxx>
To:
wtp-dev@xxxxxxxxxxx, wtp-releng@xxxxxxxxxxx,
Date:
01/09/2014 06:04 AM
Subject:
Re: [wtp-dev] [wtp-releng] Actions for JSDT Git repo refactoring?
Sent by:
wtp-dev-bounces@xxxxxxxxxxx




Just an extra question before we do anything: Shouldn't we rather create a new "webtools.jsdt" repository to avoid confusion with previous "splitted" repositories? So webtools.jsdt.* would remain the old splitted repositories, and webtools.jsdt would start for the new merged repo.

So the choice is between:
. "Keep-Old/Merge in .core"
.. Benefit: no extra repository
.. Drawback: It doesn't make clear that .core is the only active repository and that .debug and .tests are inactive
. "Keep-Old/Create-New"
.. Benefit: We can make clear that all webtools.jsdt.* are no more active and that only webtools.jsdt is
.. Drawback: One new repo

FWIW, I favor the Keep-Old/Create-New.

As there is a JSDT meeting later today, it would be nice if you could discuss it between JSDT committers and decide which one of this approach fits better for JSDT.
If you go for "Keep-Old/Create-New" then I think the very next step will be that project lead (Chris) immediatly open a bug to webmaster asking for creation of this repository. Once it available, a committer can push the branch
https://github.com/mickaelistria/webtools.jsdt.core/tree/424210-master as master to the new repositories.
And if you go for "Keep-Old/Merge in .core", then a committer can already push the branch
https://github.com/mickaelistria/webtools.jsdt.core/tree/424210-master into webtools.jsdt.core master.

Cheers,
--
Mickael Istria
Eclipse developer at
JBoss, by Red Hat
My blog - My Twee(_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx

https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev

GIF image


Back to the top