Version 2 (modified by 11 years ago) ( diff ) | ,
---|
Development Report
General Updates
- Migrated the astrobear repository revision control system from Mercurial to Git
- Plan is to use the GitFlow workflow for managing code development
- This is what are current repository looks like - AstroBearGraph
- Rich setup the gitolite plugin so developers and users can now use git commands 'clone, push, pull' to access the code repository provided they have a wiki account and the appropriate permissions instead of needing a local account on our machines.
- If you have an existing mercurial repository with code that needs to be checked in - you can still push to
hg push -f ssh://<username>@botwin.pas.rochester.edu//data/repositories/astrobear_dev
- However there is a new development procedure for working with the astrobear git repository.
- I worked on prioritizing development tasks for Scrambler 3.0 Release and setting a timeline for completion of development tasks for most developers (still waiting for feedback from Shule).
- Tickets now have due dates and priorities - Development Ticket Query
- If you are working on a paper with a collaborator - and you want to use a revision control system to manage the collaborative process, you can use the gitolite plugin on the wiki to host the source code / tex files / figures and to control access provided your collaborators register for an account on our wiki. For more information see the Gitolite Page
Development ticket activity
Modified in the last weeks
Modified in the last month
Modified in the last 6 months
Modified in the last year
Modified in over a year
Note:
See TracWiki
for help on using the wiki.