I'm fine with it.
Am 06.12.2018 um 08:52 schrieb Yoann Rodiere:
> The WildFly team is moving from Slack to Zulip, because Zulip seems to be
> the only solution that is free, provides unlimited history, and allows
> unlimited users even in private rooms (for OSS projects, at least). Gitter
> has al
So, I'm using Zulip right now on a daily basis.
I maintain my first impression that it's really not user friendly.
The fact that you are required to create topics for discussions (or find a
suitable topic in a list of a gazillion topics previously created,
obviously without a search engine where
> You also need to use ctrl+enter to send a message, the default enter is a
new line in your message
There's a checkbox to change that, and its value is persisted, so you only
have to tick it once. It's located just beside the "Send" button, I'm sure
you saw it :)
But apart from that, yes, I agree
On 12/06/2018 10:40 AM, Guillaume Smet wrote:
> So, I'm using Zulip right now on a daily basis.
>
> I maintain my first impression that it's really not user friendly.
>
> The fact that you are required to create topics for discussions
Why is creating a new topic (=typing three extra words) an issu
If it helps, Guillaume, the desktop client made all the difference for me.
And I hated the idea of moving to Gitter based on just the web client.
On Thu, Dec 6, 2018 at 4:25 AM Yoann Rodiere wrote:
> > You also need to use ctrl+enter to send a message, the default enter is a
> new line in your m
Today, I promise ;), I will release 6.0 Alpha1. But I wanted to start a
discussion about managing the master and 6.0 branches in terms of
commit/push. To date we (mostly Andrea and Chris, thanks guys!) have had
to perform very painful "merging" from master to 6.0. As 6.0 was in a
pre-Alpha state
I personally don't have a problem with that, since I don't contribute very
often, but I'd like to point out this moves most of the workload of merging
changes into 6 from Andrea/Chris to Gail/Guillaume.
Another problem being that the tests created/changed in 5.x may not work in
6 for completely dif
Hi Steve,
I don't particularly like it.
We have very few resources to work on 5.x and clearly we won't be able to
do that + learn about 6 in parallel and fix issues in both, probably in 2
completely different ways. And we won't really be able to know if it
doesn't work because it's not implemente
If you really "don't push that many things to 5.x", then no worries - it
does not really affect you. I suppose what you really mean is that when
you do contribute to 5 you do not want to "waste time" porting that to
6.0. Well the same is true on the flip side - while we are (very actively)
develo
Also, keep in mind that's so far we've been merging from master to 6.0. In
other words, so far any changes you have made on master have automatically
been moved to 6. That will no longer be the case moving forward. Outside
of some specific action, things pushed to 5 will not be on 6.
On Thu, Dec
In my opinion we have to distinguish between the types of issues:
- improvements, I think they must be done only in 6.0 and backported
only if it is easy
- minor bugs or bugs with a workaround, I think they should be resolved
in 6.0 (in case the feature causing the issue is not yet imp
Good points. I should have mentioned that.
At this point no new features, no improvements, no enhancements should be
done on 5. Just bug fixes.
And to be clear, I am actually fine with continuing to develop the bug
fixes on 5. The point was more about pushing something to 5 and then that
is it
On Thu, 6 Dec 2018 at 10:25, Yoann Rodiere wrote:
>
> > You also need to use ctrl+enter to send a message, the default enter is a
> new line in your message
>
> There's a checkbox to change that, and its value is persisted, so you only
> have to tick it once. It's located just beside the "Send" bu
On Thu, 6 Dec 2018 at 13:17, Guillaume Smet wrote:
>
> Hi Steve,
>
> I don't particularly like it.
>
> We have very few resources to work on 5.x and clearly we won't be able to
> do that + learn about 6 in parallel and fix issues in both, probably in 2
> completely different ways. And we won't rea
I am never on HipChat at this point. So don't expect any important matters
to be discussed there ;)
On Thu, Dec 6, 2018 at 9:08 AM Sanne Grinovero wrote:
> On Thu, 6 Dec 2018 at 10:25, Yoann Rodiere wrote:
> >
> > > You also need to use ctrl+enter to send a message, the default enter
> is a
>
> Hey wait a second :) You invited us to try Gitter. That's fine but we
> never decided we're migrating to Gitter.
Sure. What I meant was that we are *de facto* done migrating to gitter. Not
that we meant it, but almost everyone is there already and almost no one is
on HipChat.
I wouldn't expect
> Le 6 déc. 2018 à 16:03, Sanne Grinovero a écrit :
> It's 200,000 lines of code difference. Just don't make any change on 5
> - it's not a good use of our time either, since the future is 6.
Make 5.x a dead branch is not a good option.
Especially, since we don’t know when we will release 6.
Gave it some thoughts while walking a bit.
Note: it's just my personal opinion so sharing as such.
IMHO, there are a couple of important things:
== Triaging
We need to keep triaging bugs that are created: this is *very* important
because otherwise it will just be a pile of issues added on top o
I completely agree with everything you say. A few thoughts in-line...
On Thu, Dec 6, 2018 at 12:37 PM Guillaume Smet
wrote:
> == What to do then
>
> There are a couple of options:
> 1/ no workaround, then we should consider it for 5.x
>
If it is fixed in 5 then it should be fixed in 6 as well
19 matches
Mail list logo
