Hi John, On 2013-12-29, John Cremona <john.crem...@gmail.com> wrote: > I vote for making this an extension to git, as it makes interacting > with trac easier while also allowing developers to learn git if they > did not already know it. If we think about the previous development > process using mercurial, I am pretty sure that very few people used > the sage-wrapped functions such as hg_sage once there was a simple > tutorial on mercurial queues to get them started.
... with one difference: Interaction with trac in the mercurial (queue) workflow was as easy as using a browser to upload a (patch) file. Now, one has to learn how to do the same with git. Not terribly difficult, but I think it would be nice to have some support ready to let git interact with trac. My experience with the dev scripts: - I find them very convenient for creating a new ticket, to checkout the branch attached to a ticket, and to push a branch to a ticket. - I don't find it useful to write a comment or change the status of a ticket. I tried both, but eventually returned to using a browser. Currently, while working on tickets, it happens that I find myself on a branch that does not support the dev scripts. Hence, I had to learn how to "set upstream" to a branch for pushing it to trac. That's a lot to type, and it would be nice to have a custom (git) command that automatically pushes to a reasonably named branch on trac and attaches it to a ticket. I.e., it would be handy to have a command that behaves similar to sage --dev push --ticket=12345 Speaking of "reasonably named branch": If I am not mistaken, if I pull from a trac ticket using the dev scripts and the attached branch is in public/bla, and then push my changes using the dev scripts, it would create a new branch u/SimonKing/ticket/bla, rather than pushing back to public/bla. I find this inconvenient. So, the custom git commands resp. the dev scripts should more carefully keep track of where I branch was gotten from, and push changes back, provided permissions allow it. And: I'd find it nice to have a command that not just pulls a branch attached to a ticket, but automatically pulls the branches from the dependencies of the ticket and merges them in. And even nicer: Something should prevent one from accidentally pushing merges with master or develop branch or with the dependencies (this has already happened at least twice to me). Merging master or develop branch is one of the required (or at least recommended) steps in reviewing a ticket, but pushing a merge with master is not recommended. Best regards, Simon -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
