[PDB-3256] Drop PQL experimental status Created: 2017/01/11  Updated: 2017/04/06  Resolved: 2017/01/27

Status: Closed
Project: PuppetDB
Component/s: None
Affects Version/s: None
Fix Version/s: PDB 4.4.0

Type: Task Priority: Normal
Reporter: Wyatt Alt Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by PDB-2646 consider dropping experimental status... Closed
Template:
QA Risk Assessment: Needs Assessment

 Description   

People are starting to use it, and we haven't discussed any breaking features in some time. We should discuss removing the experimental status, possibly for the whole root endpoint.



 Comments   
Comment by Wyatt Alt [ 2017/01/19 ]

Beth Cornils to my knowledge ownership by the Enterprise group was just informally decided on yesterday. If it's not written down somewhere we should write it down, then get sign-off from Ken on dropping the experimental status (since I'm not sure where the next-gen stuff is at in relation to this), and after that we're good to go afaik.

Comment by Wyatt Alt [ 2017/01/19 ]

Ryan Coleman There's an old confluence page here: https://confluence.puppetlabs.com/display/enterprise/Search+-+PQL+for+PDB+API+CLI+Feature+Page , but I don't know that it's worth reviving since it has a lot of out of date information.

I was assuming that we had a place where group feature ownership was defined – it seems like that should exist, but if it doesn't I suppose this is probably okay. The people I'm aware of that would be likely to care are on this ticket already.

Generated at Fri Dec 13 08:51:38 PST 2019 using JIRA 7.7.1#77002-sha1:e75ca93d5574d9409c0630b81c894d9065296414.