-
Notifications
You must be signed in to change notification settings - Fork 4.2k
Nick/dnm hint - do not merge, just using jenkins #5530
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
Conversation
|
Thanks for the pull request, @nparlante! I've created OSPR-133 to keep track of it in JIRA. JIRA is a place for product owners to prioritize feature reviews by the engineering development teams. Supporting information that is good to add there is anything that can help Product understand the context for the PR - supporting documentation, edx-code email threads, timeline information ('this must be merged by XX date', and why that is), partner information (this is for a course on edx.org, for example), etc. All technical communication about the code itself will still be done via the Github pull request interface. As a reminder, our process documentation is here. |
|
@nparlante do you hve login access to jenkins? because there is a jenkins job that runs commits (so you don't have to open a PR) https://jenkins.testeng.edx.org/job/edx-all-tests-manual-commit/ |
|
Hmm, thanks Sarina. I have a jenkins account. I think it is based on my I'm using this scheme where I commit to the Stanford repo, and then Cheers, Nick On 10/8/14 5:22 PM, Sarina Canelake wrote:
|
|
FYI everyone: per discussion on hipchat, me pushing to this PR really is the way I'm running Jenkins, so er, nothing to see here! |
fe22f4e to
8766a8d
Compare
|
@nparlante does this supercede #4788? |
51759c0 to
f44e9fd
Compare
|
@sarina Hey Sarina, I thought I replied in email, but I don't see it here. Anyway, yes, I'm cleaning up and finishing off 4788. Right now I'm just cleaning it up, getting tests to pass etc, so it's WIP. Ultimately I can make a new PR for it, or we can figure out a way for me to commit it back to 4788. Whichever way you all prefer. |
|
@nparlante I think it will be fine for you to submit your ultimate PR on this, or even a new, PR. The comments on #4788 were overwhelmingly about style and test coverage, and less about functional issues with the code or design choices, so I don't think there is a lot of value in trying to reuse that PR as the comments will be outdated and inapplicable. |
329b0a7 to
e7fbcd5
Compare
8a97a37 to
4bcb95d
Compare
|
There used to be 31 commits here. Now there is one. |
|
@nparlante are you ready for review? please let me know when you want us to start looking at this. |
|
Thanks Sarina, you're pretty on top of things to ask before I ping you! I am indeed about done with it. I'll ping you next week, plus I hear Cheers, Nick On 11/26/14 12:44 PM, Sarina Canelake wrote:
|
|
Sounds great! & yep I'll be out for a few days the week prior to Christmas, On Wed, Nov 26, 2014 at 6:57 PM, Nick Parlante notifications@github.com
|
3c8acab to
756496b
Compare
73b7457 to
5f8a12c
Compare
|
Happy New Year! 🎊 How's it going? We're trying to estimate what work we're going to accomplish in the next 3 months. It would be good to be planful about this pull request, if possible. Along those lines, do you have an estimate as to when you think the code will be ready for review? |
|
Hey Sarina -- I'm actually super close. Maybe PR on Tue or so? Per your Cheers, Nick On 1/9/15 1:41 PM, Sarina Canelake wrote:
|
|
Great news! I think the best course will be to open a new PR, as this discussion isn't Be sure to include in the description a tarball of Ross's test course, and On Mon, Jan 12, 2015 at 1:31 AM, Nick Parlante notifications@github.com
|
ee86741 to
a390643
Compare
daed04e to
890588e
Compare
|
@nparlante closing this now, since the new PR is open! |
No description provided.