Meaning of PIPELINE and IN PROGRESS Tags
-
@pesala
The video pop-out feature has the pipeline tag for half a year, so it's not really informative. -
Off-topic posts moved to relevant thread
@nekomajin The Pipeline tag informs you that the feature is
plannedmore like in the waiting queue rather than planned and thus not currently being worked on. The only ETA we will get is βWhen It's Ready.β -
@pesala
Then you should rename the tag, because pipeline suggests that it's already being worked on. You should use theplanned
tag instead. -
@nekomajin We have the In Progress tag for that
-
@lonm
The tagin progress
is informative, because it means the given feature is under development. Either coding or testing, but someone is working on the feature.The tag
pipeline
is not informative, because it can refer to any stage of development from being planned to being almost ready. -
@nekomajin I feel that's part of the whole "When it's ready" thing we have going here.
Being tagged as in the pipeline means the developers want to include such functionality, in progress means it's actively being worked on.
Anything not tagged with either means it's just something that X members of the community want.
Perhaps "pipeline" should be renamed to "One day, for sure", with everything else left as "ehhhh, maybe" .
-
@nekomajin I moved the off-topic posts again.
The meaning of the tags is both clear and informative. If you don't understand the meaning of WIR it is not the fault of the developers.
- In Progress means that a feature is currently being worked on, but there is no ETA is ever given. Email has been in progress for over 3 years. The first technical preview even had a Mail Panel.
- Pipeline means that the feature is planned, but is not currently being worked on. When work starts on it in earnest, then the tag will likely be changed to "In Progress."
Please be patient. The team is small, and there is nothing that the moderators can do to speed up the development process, nor change the policies. Even insiders who are able to test the Email client, and see the bug-tracker, are not at liberty to discuss internal matters.
-
@pesala
My complaints have nothing to do with the speed of development.I am talking about the fact, that "pipeline" means any stage of development, including the planning phase. Just google it!
So using this tag indicates absolutely nothing, and can be confusing for the members of this forum. Just change it to "planned", and everything will be clear.
-
@lonm
That's the problem. The word "pipeline" does not mean "developers want to include such functionality". It means that it is under consideration OR being planned OR being worked on OR being ready to release. The given feature can be in any of these stages.We have "in progress" for the features that are actually being worked on in either the implementing or the testing phase, which is perfect. We should have "planned" or something similar for features, that are currently not being worked on, but the developers have the intention to deal with them in the future.
-
@nekomajin "Planned" is more accurate but it still invites the question of "OK, it's planned, but for when?".
What would be desirable is to find a word which indicates that it will eventually be implemented, but that doesn't invite the question of when or suggesting it might be soon.
-
@lonm said in Meaning of Pipeline and In Progress Tags:
Perhaps "pipeline" should be renamed to "One day, for sure", with everything else left as "ehhhh, maybe" .
Still not unambiguous, one could understand this as "the feature will be ready in one day"...
-
Arguing about the terminology is pointless.
The term Pipeline has been defined by the Vivaldi Team. That which we call a rose is by any other name just as prickly.
-
@lonm
This is correct, but it is also true for the "in progress" tag.Anyway, I think it would be best to distinguish features that are already available in the developer stream, and those that are only in closed alpha testing phase. A few of us, who browse the forum on a daily basis, is more or less clear, what the status of a given feature. But there are many people here, who don't necessarily read the blog posts or the discussions in the topics, just take a quick look at the features requests or the summarizing topic. They could benefit from the usage of unambiguous wording.
-
@pesala
I don't care who came up with this tag. The word is still meaningless in a context like this. I don't blame you or anyone else, just wanted to point out, that it can be and it is misleading for a lot of people here. -
I've just asked to change the PIPELINE tag to something less ambiguous, so maybe we'll get a better one. I can't promise anything though.
-
@pafflick
Thanks! -
The PIPELINE tag will remain as it is for now. I've updated the first reply by @Pesala to clarify the explanation that he provided.
-
@pafflick
Thanks for trying.