[squid-dev] Bzr to git migration schedule

[Eliezer Croitoru]

NOC NOC, anybody there?

Please take a minute to look at the subject.

Thanks,
Eilezer
----
Eliezer Croitoru
Linux System Administrator
Mobile: +972-5-28704261
Email: eliezer at ngtech.co.il



-----Original Message-----
From: Alex Rousskov [mailto:rousskov at measurement-factory.com] 
Sent: Friday, July 21, 2017 08:02
To: Eliezer Croitoru <eliezer at ngtech.co.il>; 'Kinkie' <gkinkie at gmail.com>; squid-dev at lists.squid-cache.org
Subject: Re: [squid-dev] Bzr to git migration schedule

On 07/20/2017 02:52 PM, Eliezer Croitoru wrote:
> And... I must say that I am experiencing something weird with the wiki in the last month or more.
> I mean that for example I received the message in the top left side of the wiki:
> "Thank you for your changes. Your attention to detail is appreciated.
> Only minutes after I already seen the page exists in another tab.
> Should I open a new bug in the bugzilla?

I have already whined to NOC about this problem. They were going to look at it soon. If you do not see improvements for another week or so, it may be a good idea to file a bug report with Bugzilla.

Alex.


> From: Kinkie [mailto:gkinkie at gmail.com]
> Sent: Thursday, July 20, 2017 10:59
> To: Amos Jeffries <squid3 at treenet.co.nz>; Eliezer Croitoru 
> <eliezer at ngtech.co.il>; squid-dev at lists.squid-cache.org
> Subject: Re: [squid-dev] Bzr to git migration schedule
> 
> I believe we are talking about updating the pages that reference bzr 
> with pages that reference the current repositories and best practices
> 
> On Thu, 20 Jul 2017 at 08:27, Eliezer Croitoru <mailto:eliezer at ngtech.co.il> wrote:
> I didn't knew we are trying to "re-write" the wiki.
> To what scale are we talking?
> Mover everything from the http://wiki.squid-cache.org to github or just specific articles?
> 
> Eliezer
> 
> ----
> Eliezer Croitoru
> Linux System Administrator
> Mobile: +972-5-28704261
> Email: mailto:eliezer at ngtech.co.il
> 
> 
> 
> -----Original Message-----
> From: squid-dev 
> [mailto:mailto:squid-dev-bounces at lists.squid-cache.org] On Behalf Of 
> Amos Jeffries
> Sent: Tuesday, July 18, 2017 11:59
> To: mailto:squid-dev at lists.squid-cache.org
> Subject: Re: [squid-dev] Bzr to git migration schedule
> 
> On 18/07/17 16:40, Alex Rousskov wrote:
>> On 07/15/2017 10:43 PM, Alex Rousskov wrote:
>>> On 07/11/2017 10:20 PM, Alex Rousskov wrote:
>>>
>>>>    2017-07-11: No more new tags in the official bzr repo.
>>>>    2017-07-13: No more new commits(*) in the official bzr repo.
>>>>    2017-07-14: Migration starts.
>>>>    2017-07-15: Anticipated optimistic migration end.
>>>>    2017-07-18: Anticipated pessimistic migration end.
>>>>
>>>> All times are noon UTC.
>>
>>
>>> The migration steps are done. According to the automated tests, all 
>>> bzr and git commits match (except for bzr commits containing empty 
>>> directories, as expected). However, I suggest _not_ declaring the 
>>> migration over yet and keeping both the old bzr and the new git 
>>> repository intact for 24 hours in case somebody notices problems 
>>> with the new official git repository at
>>>
>>>      https://github.com/squid-cache/squid
>>
>> I think we should declare the migration over, and the official 
>> repository to be at the above Github URL.
> 
> +1.
> 
>>
>> I saw no problem reports about the new repository. We found and fixed 
>> one bug in the migration tool when migrating some of the Factory 
>> branches, but that bug did not affect the official repository which 
>> has a simpler structure. We could still go back to bzr in the face of 
>> disaster, but I hope that would not be necessary.
>>
>> Needless to say, this git migration is just the first step towards 
>> decent Project QA. The next steps are updating various maintenance 
>> scripts (thank you, Amos, for working on that) and pre-commit build 
>> tests of pull requests (Eduard is leading that effort). The basic 
>> build test enabled on Github should detect many serious problems 
>> today, but I hope to see a lot more powerful Jenkins-driven tests in the coming weeks.
>>
> 
> We also need someone to lead the wiki re-writing, most of the 
> DeveloperResources mentioning the repository and how-to for certain 
> development activities.
> 
> 
> Amos
> _______________________________________________
> squid-dev mailing list
> mailto:squid-dev at lists.squid-cache.org
> http://lists.squid-cache.org/listinfo/squid-dev
> 
> _______________________________________________
> squid-dev mailing list
> mailto:squid-dev at lists.squid-cache.org
> http://lists.squid-cache.org/listinfo/squid-dev
>