removing the dev scripts

[Vincent Delecroix]

Hello,

dev script are a mess (see #18356). Could I remove everthing in
sage/dev/ that is related to communication with the git server or the
trac server? The function would provide help and links to the
documentation instead.

I also want to keep the import-patch feature that is definitely useful.

Cheers,
Vincent

[Jeroen Demeyer]

On 2015-05-07 12:06, Vincent Delecroix wrote:
> Hello,
>
> dev script are a mess (see #18356). Could I remove everthing in
> sage/dev/ that is related to communication with the git server or the
> trac server?

Please don't!

I still use the dev script occasionally for read-only access to the Trac
server. One major advantage that the dev scripts have over "git trac" is
that they work out of the box, without installing or configuring anything.

[Volker Braun]

We could add "git trac" as a standard package now, I haven't made any changes outside of the release management stuff in a while....

[kcrisman]

> Hello,
>
> dev script are a mess (see #18356). Could I remove everthing in
> sage/dev/ that is related to communication with the git server or the
> trac server?

Were they already deprecated, though?  In that event there should be a well-defined time at which they could be removed.

[Nathann Cohen]

> Were they already deprecated, though? In that event there should be a
> well-defined time at which they could be removed.

The documentation has been removed in #17555. If I remember correctly,
the associated sage-devel thread settled on something like "we stop
advertising them but will keep the code for a while, for those who
still use them".

Nathann

[Dima Pasechnik]

undocumented things don't exist!

Nathann

[Jeroen Demeyer]

On 2015-05-07 22:36, Volker Braun wrote:
> We could add "git trac" as a standard package now, I haven't made any
> changes outside of the release management stuff in a while....

It's not just about installing them, it's also about making it work
without configuration:

$ ./sage --git trac checkout 18330
...
git_trac.git_error.UserEmailException: user/email is not configured,
cannot make commits

It should not be required to configure email to checkout a ticket.

[Vincent Delecroix]

This is very bad. I agree that pulling from trac should work without any
configuration. What about explicit deprecation of the scripts that
modifies tickets/remote git branches?

Vincent

[Jeroen Demeyer]

On 2015-05-08 10:26, Vincent Delecroix wrote:
> What about explicit deprecation of the scripts that
> modifies tickets/remote git branches?

I agree 100% with *deprecating* the dev scripts, I was just complaining
about *removing* them.

[Dima Pasechnik]

this is surely a small change to be done; I opened
https://github.com/sagemath/git-trac-command/issues/22

Dima

[Nicolas M. Thiery]

On Fri, May 08, 2015 at 07:56:51AM +0200, Jeroen Demeyer wrote:
> On 2015-05-07 22:36, Volker Braun wrote:
> >We could add "git trac" as a standard package now, I haven't made any
> >changes outside of the release management stuff in a while....

This would be nice! As well as for configuration-free read only
operations. During the recent Sage days I attended, this was one of
those little-yet-annoying hurdles we faced when training new devs.

Cheers,
Nicolas
--
Nicolas M. Thiéry "Isil" <nth...@users.sf.net>
http://Nicolas.Thiery.name/