Am 08.01.2016 um 17:29 schrieb Marc Khouzam:
I also would not like to have to change versions.
Changing the URL only allows me to change one line quickly.
Changing each version of each feature group is more work and more error prone.
Exactly. I also don't want to look *into* my repos for each contribution and
copy multiple versions around.
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
And when speaking about tests, isn't it possible to verify that each URL is not
a composite repo?
------------------------------------------------------------------------------------------------------------------------
*From:* [email protected] [[email protected]] on behalf of
Mickael Istria [[email protected]]
*Sent:* January 8, 2016 11:23 AM
*To:* [email protected]
*Subject:* Re: [cross-project-issues-dev] Enforce Gerrit for Simrel?
On 01/08/2016 05:15 PM, Eike Stepper wrote:
I may misunderstand this fixed version stuff, so I better ask explicitely. I will not be forced to author exact
feature versions in my contribution files, right?
I'm fine with the rule of contributing only fixed content, but I prefer to
achieve that goal with non-changing repos.
The rule currently accepts version ranges with "changing" repository URL. However, it seems very difficult to write
good tests that guarantee that the rule is respected... That's why I'm trying to push towards the 4-digits version
rule as "de-facto standard", since it can trivially be checked.
From your contributor point-of-view, what makes changing the version more difficult that changing an URL? In any case,
you'll have to make a change in the b3aggrcon file whenever you want to contribute something new. It seems to me that
the extra-cost of changing the version when also changing the URL is not that high, is it?
Cheers,
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
_______________________________________________
cross-project-issues-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/cross-project-issues-dev
_______________________________________________
cross-project-issues-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/cross-project-issues-dev
