Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #2620

Closed
Open
Created Feb 23, 2011 by Tomas Touceda@chiiph

Vidalia 0.2.11 release and future workflow

Vidalia is going to have a git repo @tpo.

The workflow will be as follow: There will be two branches, one for stable and one for alpha. The stable branch will be shipped with Tor stable releases, and the alpha branch will be released with Tor alpha.

Besides from that, every new feature or bugfix will get its own branch. Once it's tested, if it's a new feature it'll get merged into alpha, if it's a bugfix it'll get merged into both stable and alpha.

Every new release, the corresponding branch will get tagged with the new version.

Every bugfix or new feature needs Matt's review to get to stable, so I'll open a ticket with a link to the corresponding commit in the git repo.

Matt: are you ok with Vidalia stable being only in the git repo (i.e. removing the svn repo) and with this workflow?

The changelog for both alpha (not finished yet) and stable releases is in: https://trac.torproject.org/projects/tor/wiki/projects/vidalia

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking