Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Will API v5 be supported? #86

Open
myanaros opened this issue Jul 25, 2013 · 24 comments
Open

Will API v5 be supported? #86

myanaros opened this issue Jul 25, 2013 · 24 comments

Comments

@myanaros
Copy link

It looks like v5 will be using JSON instead of XML, among adding tons of functionality. Will support be added for v5?

@jasonnoble
Copy link
Collaborator

That is in the plan, yes.

@jasonnoble
Copy link
Collaborator

http://pivotallabs.com/new-pivotal-tracker-api-now-in-beta/ It's officially in Beta.

@jomsie1
Copy link

jomsie1 commented Aug 26, 2013

Hi! I'm assuming V5 will be supported when it is stable and finalized? (Also assuming it will change somewhat between beta and release)

@forest
Copy link

forest commented Sep 4, 2013

Please make the gem thread safe when updating to the new API. Using the gem in sidekiq workers exposed the fundamental flaw that the PivotalTracker::Client.token is global and not thread safe.

I'm happy to help with this.

@jasonnoble
Copy link
Collaborator

Will do.

@BartlomiejSkwira
Copy link

V5 is beta, but is the recommended one ;)

Dan Podsedly says:
Bartlomiej, thanks for pointing that out – we meant to say that V3 is no longer being enhanced and will eventually be removed. We’re clarifying the messaging in the API help docs.

V3 is still supported, but we recommend using V5 at this point. It’s quite stable, but we’re still adding some endpoints, and may tweak some minor things before removing the “beta” label.

V4 is mostly the same as V3, and was never officially released.

[edit]: any chance there is a deadline for v5 support? :P

@parkerl
Copy link
Contributor

parkerl commented Sep 3, 2014

Love to help in any way with the move to V5

@forest
Copy link

forest commented Sep 4, 2014

I started a new thread safe gem for the Pivotal Tracker v5 API. It currently supports most get requests (read-only) as that is my current need.

https://github.com/dashofcode/tracker_api

@jasonnoble
Copy link
Collaborator

https://t.e2ma.net/message/q7a3q/yhw4si API V5 is out of beta...

@FWDavide
Copy link

Is there any plan to move to V5 of the API ?

@jsmestad
Copy link
Owner

Let me see if I can reach out and get an answer to this. If not, maybe I suck it up and come back around to committing on this repo :)

@guiman
Copy link

guiman commented Feb 5, 2015

I'm currently building an application using V5 (using raw api calls), and I'm thinking about using this gem instead. Is there any current working branch to start from @jsmestad? I will start a fork but interested on keep posted about this.

@sbleon
Copy link
Contributor

sbleon commented Feb 5, 2015

I use this gem pretty extensively in a core business app, but I really also
need to make the switch to v5. I would contribute to a fork. I think the
public API of this gem is pretty solid and worth preserving, although the
internals will probably need a pretty extensive overhaul due to the switch
from v3's XML to v5's JSON.

On Thu, Feb 5, 2015 at 5:36 AM, Alvaro Fernando Lara <
notifications@github.com> wrote:

I'm currently building an application using V5 (using raw api calls), and
I'm thinking about using this gem instead. Is there any current working
branch to start from @jsmestad https://github.com/jsmestad? I will
start a fork but interested on keep posted about this.

Reply to this email directly or view it on GitHub
#86 (comment)
.

@guiman
Copy link

guiman commented Feb 5, 2015

I've already convinced a friend at work to get started into this. And completely agree on keeping the current gem API. Is there a tracking system setup for this gem in particular? If not, Pivotal Could be a good place to get one started for it.

@sbleon
Copy link
Contributor

sbleon commented Feb 5, 2015

I don't know of any tracking system. Pivotal does seem like an obvious
choice!

On Thu, Feb 5, 2015 at 9:53 AM, Alvaro Fernando Lara <
notifications@github.com> wrote:

I've already convinced a friend at work to get started into this. And
completely agree on keeping the current gem API. Is there a tracking system
setup for this gem in particular? If not, Pivotal Could be a good place to
get one started for it.

Reply to this email directly or view it on GitHub
#86 (comment)
.

@jasonnoble
Copy link
Collaborator

Hey all, @jsmestad reached out to me a while back, and the following was my response. I'd love to see this get worked on, unfortunately, I don't have the time.

Tracker project is available at https://www.pivotaltracker.com/n/projects/1269684

I spent some time on this a year and a half ago…

https://github.com/jasonnoble/pivotal-tracker/tree/api_version5
This was my initial re-write. Last updated in August of 2013.

https://github.com/davincicoders/pivotal-tracker-v5
This was my student’s effort to expand on my repo above, it’s a little farther, but still a year outdated
Note: https://github.com/davincicoders/pivotal-tracker-v5/blob/master/spec/spec_helper.rb
This has some IMO helpful VCR stuff to filter out sensitive data from the VCR tapes (1)

I definitely think the gem needs to support V5 API, unfortunately I don’t have the time to take a leadership role on this.

Also… @forest commented on #86 that the updates need to be thread safe. Looks like he has some work at https://github.com/dashofcode/tracker_api, so you may want to consider pulling (some of?) that code back into the pivotal-tracker gem. Maybe @forest has some time to help out?

  1. My hope with these changes would be that someone who wants to contribute to the gem would simply have to do the following:
Login to Pivotal Tracker
Create Project -> Check the Add sample project data checkbox and click Create Project
*** Populate pivotal_credentials.yml *** (https://github.com/davincicoders/pivotal-tracker-v5/blob/master/config/pivotal_credentials.yml.example)
rake spec

This would then run all the tests. Maybe have an environment variable that would hit the live API?

@forest
Copy link

forest commented Feb 5, 2015

@jasonnoble I'm committed now to the new https://github.com/dashofcode/tracker_api gem. I am actively maintaing and have been accepting many pull requests from the community using this new gem. The read interface is mostly complete, but there is work to do still on updating data. I just pushed a version with the ability to update stories that lays a good foundation for adding update capabilities to the other resources.

The inteterface is similar to this gem as I use it heavely before I ran into thread safe issues and needed features from the v5 API. So it shouldn't be a big streach for people to change.

I'd be happy to have contributions.

@jasonnoble
Copy link
Collaborator

Would you consider combining the two? // @jsmestad

@jsmestad
Copy link
Owner

jsmestad commented Mar 2, 2015

@jasonnoble @forest definitely. I would love to move to using Faraday anyway.

@jsmestad
Copy link
Owner

jsmestad commented Mar 2, 2015

@forest I'm committing to re-writing this gem over the next month or two.

@jasonm23
Copy link

Have you looked at Blanket Wrapper gem, it's ideal for this sort of project.

@sbleon
Copy link
Contributor

sbleon commented Sep 19, 2015

@jsmestad how's the V5 rewrite going? Can you use any help with it? I'm trying to figure out if I should focus on https://github.com/dashofcode/tracker_api instead.

@jsmestad
Copy link
Owner

I have not had much time to work on it to be honest. the
dashofcode/tracker_api I have used and can say its lacking some features
and customization that this gem provides, but overall stable.

Regards,

Justin Smestad

justin.smestad@gmail.com

On Sat, Sep 19, 2015 at 7:32 AM, Leon Miller-Out notifications@github.com
wrote:

@jsmestad https://github.com/jsmestad how's the V5 rewrite going? Can
you use any help with it? I'm trying to figure out if I should focus on
https://github.com/dashofcode/tracker_api instead.


Reply to this email directly or view it on GitHub
#86 (comment)
.

@sbleon
Copy link
Contributor

sbleon commented Sep 21, 2015

Thanks for the update, @jsmestad.


Leon Miller-Out - Singlebrook Technology - 607-330-0191

On Sun, Sep 20, 2015 at 4:00 PM, Justin Smestad notifications@github.com
wrote:

I have not had much time to work on it to be honest. the
dashofcode/tracker_api I have used and can say its lacking some features
and customization that this gem provides, but overall stable.

Regards,

Justin Smestad

justin.smestad@gmail.com

On Sat, Sep 19, 2015 at 7:32 AM, Leon Miller-Out <notifications@github.com

wrote:

@jsmestad https://github.com/jsmestad how's the V5 rewrite going? Can
you use any help with it? I'm trying to figure out if I should focus on
https://github.com/dashofcode/tracker_api instead.


Reply to this email directly or view it on GitHub
<
#86 (comment)

.


Reply to this email directly or view it on GitHub
#86 (comment)
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests