Re: [squid-dev] [RFC] Disable Github issue tracker

[Alex Rousskov]

On 07/18/2017 09:26 PM, Amos Jeffries wrote:
> On 19/07/17 09:22, Alex Rousskov wrote:
>>  With Squid official repository now at Github, a lot more folks will
>> be tempted to report bugs and file feature requests there. I propose to
>> remove that functionality from the Github interface (for now). Any
>> objections or better ideas?


> Sounds good to me.

> I suspect the issues from Nov/Dec last year have duplicate discussions
> either in squid-users or bugzilla - but that would be worth checking up
> with the submitters before the github issues are lost.

Done. There are two open DevOps issues remaining. I will disable the
interface once those issues are closed. I will try to export/archive the
closed issues before disabling the interface.


> There are maintainer workflow scripts still todo, but before going to
> the trouble I'm considering whether that workflow still makes any sense
> - it was designed for CVS, and adapted to bzr in absence of good bzr
> tooling. If anyone knows of some good branch management tools for git
> I'm interested.

I wish I could help, but I do not really know what the old tools did,
and do not have enough git expertise to advice on such general topics as
"good branch management tools for git". If nobody answers here, consider
enumerating the primary needs in general terms. Such a list would make
it easier to solicit external advice.


Thank you,

Alex.
P.S. Congratulations on the first PR merge via Github!
___
squid-dev mailing list
squid-dev@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-dev

Re: [squid-dev] [RFC] Disable Github issue tracker

[Amos Jeffries]

On 19/07/17 09:22, Alex Rousskov wrote:

Hello,

 With Squid official repository now at Github, a lot more folks will
be tempted to report bugs and file feature requests there. I propose to
remove that functionality from the Github interface (for now). Any
objections or better ideas?



Sounds good to me.

 I suspect the issues from Nov/Dec last year have duplicate discussions 
either in squid-users or bugzilla - but that would be worth checking up 
with the submitters before the github issues are lost.


Some other migration things;

a) I have now completed the updates for code maintenance scripts and 
re-enabled the cron jobs.


There are maintainer workflow scripts still todo, but before going to 
the trouble I'm considering whether that workflow still makes any sense 
- it was designed for CVS, and adapted to bzr in absence of good bzr 
tooling. If anyone knows of some good branch management tools for git 
I'm interested.



Amos
___
squid-dev mailing list
squid-dev@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-dev

[squid-dev] [RFC] Disable Github issue tracker

[Alex Rousskov]

Hello,

With Squid official repository now at Github, a lot more folks will
be tempted to report bugs and file feature requests there. I propose to
remove that functionality from the Github interface (for now). Any
objections or better ideas?

FWIW, I have considered and rejected the idea of immediately migrating
from our Bugzilla to the Github issue tracker. Yes, it is tempting to
keep "everything" in one place, and making bug reporting "easy" is a
serious Github advantage, but I do not think we should move right now:

1. Migration itself will not address any current critical problems.

2. Migration is a significant overhead and/or a serious inconvenience,
depending on whether Bugzilla entries are copied to Github or simply
allowed to rot while being "archived" at their current location.

3. Virtually all the primary features missing in Squid Bugzilla today
are either also missing from Github Issues or can be enabled in Bugzilla
by upgrading our Bugzilla installation and adding extensions. This will
not be easy, especially fixing one of the biggest Bugzilla-driven
collaboration limitations[1], but it is doable long-term if we decide to
stay with Bugzilla.


Needless to say, the arguments for staying with Bugzilla and the
decision to stay itself may change in the foreseeable future. We can
revisit this question as needed.


Thank you,

Alex.
[1] https://bugzilla.mozilla.org/show_bug.cgi?id=540
___
squid-dev mailing list
squid-dev@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-dev

Re: [squid-dev] Bzr to git migration schedule

[Kinkie]

On Tue, Jul 18, 2017 at 9:36 PM, Alex Rousskov
 wrote:
> On 07/18/2017 02:59 AM, Amos Jeffries wrote:
>> We also need someone to lead the wiki re-writing, most of the
>> DeveloperResources mentioning the repository and how-to for certain
>> development activities.
>
> Agreed.
>
> BTW, I trust it is OK to delete bzr/launchpad-specific instructions when
> they are replaced with git/github-specific ones, but please correct me
> if I am wrong. The wiki history will preserve bzr instructions for
> posterity, of course.

I agree on all.

-- 
Francesco
___
squid-dev mailing list
squid-dev@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-dev

Re: [squid-dev] Bzr to git migration schedule

[Alex Rousskov]

On 07/18/2017 02:59 AM, Amos Jeffries wrote:
> We also need someone to lead the wiki re-writing, most of the
> DeveloperResources mentioning the repository and how-to for certain
> development activities.

Agreed.

BTW, I trust it is OK to delete bzr/launchpad-specific instructions when
they are replaced with git/github-specific ones, but please correct me
if I am wrong. The wiki history will preserve bzr instructions for
posterity, of course.

Alex.

___
squid-dev mailing list
squid-dev@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-dev

Re: [squid-dev] Bzr to git migration schedule

[Amos Jeffries]

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
squid-dev@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-dev