What is preventing us from using GIT right now ?

[Nathann Cohen]

Helloooooo Everybody !

I just noticed that I had stopped (or slowed down) working on Sage recently, because it feels like whatever you write cannot be reviewed and will not be merged anyway. Soooooooooooooo I wondered : what is preventing us from starting to make GIT releases right now ? It really feels like no Sage development can occur until git patches begin to be merged into releases, so perhaps we could just skip the development scripts (as some of us already began to work on patches using git manually) and see what happens this way ? It's not like we cannot work without those scripts, and well.... It would be nice if we could continue to work on Sage in the meantime :-P

Though of course there may be other required things that I am not aware of ?...

Have fuuuuuuuuuuuuuuuuuuuuuuuuun !!

Nathann

[Volker Braun]

I think we need some more time to finish up the documentation and dev scripts. Andrew and I will be at the sage days in UC Davis in a month, so that would be a good point to start making a sage-git release. Realistically, it should probably be done by one of us two anyways (unless somebody else volunteers).

In the meantime you can just keep working on git branches. As long as you don't introduce unnatural dependencies (merge unrelated tickets) you'll be fine. And nobody stops you from reviewing tickets ;-)

[Nathann Cohen]

Yooooooooooo !!

> I think we need some more time to finish up the documentation and dev scripts. Andrew and I will be at the sage days in UC Davis in a month, so that would be a good point to start making a sage-git release. Realistically, it should probably be done by one of us two anyways (unless somebody else volunteers).

Hmmmm.... Okay.

> In the meantime you can just keep working on git branches. As long as you don't introduce unnatural dependencies (merge unrelated tickets) you'll be fine. And nobody stops you from reviewing tickets ;-)

I began to lose hope when my "green light" patches switched to "red light".

http://trac.sagemath.org/ticket/15044

On which commit should I base them so that the patchbot accepts them ? :-P

Nathann

[Volker Braun]

Don't rely on the patchbot too much for now, there are stills some kinks to be ironed out I think.

The reason why your branch on #15044 is broken is that cc9d0c3c814ffcd464765b0d24ff835062bef587 has merge conflict markers checked in.

[Nathann Cohen]

Thaaaaaaaaaaaaaaaanks !!

I just rebased the loooooong sequence 15044 - 15049 - 15054 :-)

Nathann

> --
> You received this message because you are subscribed to the Google Groups
> "sage-git" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-git+u...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.

[Cesar Chew]

NobleProg is a Training and Consulting provider and we run all types of GIT Training Courses.

If you are interested please go to: http://www.nobleprog.us/git-training-courses

http://www.nobleprog.us/

for Classroom or Remote GIT Training Courses in USA

Or contact us directly

Tel. 646 461 6132 - 415 692 4083