Hi!
Here is an update from Sage Days 54 of today!
- Development model:
=================
There are two ways to share code between collaborators on the trac server.
(a) If users vivienne and anne work on some feature, both could have their
own branches on trac in
/u/vivienne/combinat/partition/V-branch
/u/anne/combinat/partition/A-branch
respectively. If V makes a change, A would need to pull from V's branch
to get the
changes, but would push her changes to A's branch and vice versa.
(b) Users V and A could work on the same branch in
/public/combinat/partition/our-branch
In this case anybody with trac access can in principle make changes to
this
branch.
If there are lots of collaborators, (a) might be cumbersome since a given
developer
needs to pull from the branches of all developers since it is not necessarily
clear
who made the last changes. But (a) is better if each developer wants to save
their
changes before merging.
- Tornado branches:
=================
If developers want to share functionalities with collaborators who
are not Sage developers which are in various branches, it is possible
to merge those and point the collaborators to that branch and put it
on /public/combinat/...
- Naming conventions for searching:
================================
It would be a good idea for searching purposes
to name branches using keywords. For example, if there is a branch related to
combinatorics, it is a good idea to put /combinat in the name. If it further
is about partitions and symmetric functions, one could put
partitions-symmetric_functions into the name, so that this is searchable for
other developers.
It is a good idea to label work-in-progress by <name of branch>-wip so that
other developers do not base anything off this branch.
It is a good idea to label tornado branches as <name of branch>-tornado
so that other developers do not base anything off this branch.
- We started playing with the trac-git functionalities by playing with ticket
15300. You can look at the log on the ticket there.
We will probably import some more patches from the sage-combinat queue tomorrow
to see how it works and how to play with the new development flow.
Best,
Anne
--
You received this message because you are subscribed to the Google Groups
"sage-combinat-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-combinat-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-combinat-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-combinat-devel.
For more options, visit https://groups.google.com/groups/opt_out.
