will make all our lives a little easier. Projects that don't want
to use them can disable the default labels.
blocked -> anyone really filtering for that?
The status is not only about filtering. It is also about being able to
immediately see the status of an issue when you open it up.
rganization
BR,
Jens Lideström
___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/platform-dev
+1 for protecting master from direct pushes
2022-03-25 16:09 skrev Andrey Loskutov:
I'm also in favour of requiring validation before push, but there
should be still possibility to manually merge anything.
We often have cases where builds aren't running at all, so to fix it
we have to be able to
estions,
feedback, or just think this is a good or bad idea!
https://bugs.eclipse.org/bugs/show_bug.cgi?id=552667
Best regards,
Jens Lideström
___
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit
https://ww
vider<>();
IObservableSet knownElements = contentProvider.getKnownElements();
IObservableMap streetName = BeanProperties.value("address")
.value(BeanProperties.value("street"))
.observeDetail(knownElements);
BR,
Jens Lideström
On 2021-04-21 10:04, Christoph Läubric
Maybe it would be useful if the version number had an additional
segement:
major.new-segment.minor.service
new-segment could be increased for removals, and an increase would
signal something like this:
"This change is backwards compatible EXCEPT for the removal of
deprecated things which ha
> What do you think about a documentation what event field is filled with
what value for certain event types?
That sounds like a good idea! I've noticed that it's often hard to
understand exactly what the different event types are for.
Sometimes there is detailed information in the documentation
>
> On Sat, May 23, 2020 at 5:33 PM Jens Lideström wrote:
>> I'm in the process of marking some old databinding API for removal. I'm
>> not really sure how to write the Javadoc comment on the removed API.
>>
>> Is the following a good comment?
>>
&g
I'm in the process of marking some old databinding API for removal. I'm
not really sure how to write the Javadoc comment on the removed API.
Is the following a good comment?
/**
* XXX
* @deprecated This class will be removed in a future release. See
* https://bugs.eclipse.org/bugs/
Hello!
Is anyone still using the e4 databinding fork?
I though there were no users of e4 databinding, but a person Veselin
Markov left a comment on a bug report for it last winter:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=453796#c10
It would be interesting to hear from you! Please replay a
10 matches
Mail list logo
