Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Enforce Gerrit for Simrel?

Hi Mikael,

That looks nice! I'm a bit concerned, though, that we start to rely on tooling that's no longer actively maintained. For example, for me the editor doesn't work at all anymore (see my post "Simrel: Is the b3 Aggregator Editor broken?") and there seems to be nobody who can help me fix that.

IMHO the main reason to use that editor over a plain XML editor was the poor model/serialization design, in particular:

a) that path-based cross-references (which break easily when features or categories were added and removed) were used over ID-based references, and
b) that bidirectional references were used for Categories <-> Features instead of simple uni-directional references, and
c) that Contact persons are shared across contributions (again with bidi-refs, IIRC).

If the underlying model/serialization was fixed w.r.t. the above issues it would be way simpler to edit the XML directly without breaking the overall model so easily.

I know this is a little bit off-topic, but it demonstrates that this model+editor is not very well maintained. And that becomes a concern if we start to rely upon it.

Personally I like Matthias' proposal to automate the "version narrowing/fixing" as part of the aggregation.



Am 13.01.2016 um 19:31 schrieb Mickael Istria:
On 01/08/2016 10:44 PM, Mickael Istria wrote:
On 01/08/2016 07:13 PM, Eike Stepper wrote:
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.
Just to be sure I correctly understand your (and Marc's and Ed's) point: you're OK to have fully-qualified versions in the file, but you don't want to maintain it manually, right? So if the b3 model editor were providing that, would it suit you? Would you specify fully-qualified versions to the aggregator? If it's the only thing blocking you and others in using fully-qualified versions, I may be able to raise the priority of this improvement in my todo-list.
What do you think about ? Would you set fully-qualified versions with those 2 features?
Mickael Istria
Eclipse developer at JBoss, by Red Hat <>
My blog <> - My Tweets <>

cross-project-issues-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top