Re: [codesprints] [Tools-discuss] Codesprint at IETF 115.

[Robert Sparks <[e-mail]>]

You can fastforward at the commits link in the github ui or use the gh command line client. I recommend the latter. I’ll send more details when at a real kb tomorrow. 

Sent from my iPhone

> On Oct 26, 2022, at 6:38 PM, Russ Housley <[e-mail]> wrote:
> 
> Robert:
> 
> I have not touched https://github.com/russhousley/datatracker since the last codesprint.  What is the best way to get caught up.  The documentation talks about getting started, but it does not tell the best way to get caught up after being dormant for months.
> 
> Russ
> 
> 
>> On Oct 26, 2022, at 3:20 PM, Robert Sparks <[e-mail]> wrote:
>> 
>> If you're planning to sprint but haven't warmed up your development environment yet, please take some time now to do so.
>> 
>> Remember to switch to the feat/tzaware branch and rebuild your containers. Fetch a fresh copy of the database. Leave time this week and early next for us to help you work through any issues you might run into so that time is not lost on the Sprint Saturday.
>> 
>> If dataracker development is all you are using docker for, then I suggest:
>> ```
>> (cd docker; ./cleanall); docker volume prune
>> ```
>> to make sure you have new images once your at the head of feat/tzaware.
>> 
>> If you are using docker for other things, read the cleanall script and take a more selective approach to not disrupt your other activities.
>> 
>> RjS
>> 
>> p.s. I will be slow to respond to messages Oct 31, but other sprinters can help with any problems reported during that time.
>> 
>> 
>>> On 10/13/22 4:59 PM, Robert Sparks wrote:
>>> If you'll be joining us at the codesprint in London, please add yourself to the table at https://notes.ietf.org/notes-ietf-115-tools#.
>>> We're starting to collect the issues we hope people can work on, but of course, anyone is welcome to work on whatever is bothering them the most.
>>> If you have something that you would like to take on early, let me know and I'll add it to https://github.com/orgs/ietf-tools/projects/7/views/1.
>>> Please read through what's below, and make sure that you are ready to work on the /feat/tzaware branch.
>>> I hope to see you in London!
>>> RjS
>>> On 9/27/22 10:13 AM, Robert Sparks wrote:
>>>> All -
>>>> 
>>>> If you can participate in the Codesprint at IETF115, please take some time in the next week or so to bring your development environment up to current and switch it to the /feat/tzaware branch. My plan is to have all contributions at the sprint come into that branch (we expect to deploy it right after IETF 115).
>>>> 
>>>> Instructions for setting your environment up (which is even easier now than it was at IETF 114) are at https://github.com/ietf-tools/datatracker/blob/main/docker/README.md. At the step at the beginning replace `git checkout main` with `git checkout feat/tzaware` for this sprint.
>>>> 
>>>> RjS
>>>> 
>> 
>> ___________________________________________________________
>> Tools-discuss mailing list - [e-mail] - https://www.ietf.org/mailman/listinfo/tools-discuss
>