#tyndur · 2010-12-13

28 Nachrichten · Seite 1 von 1 · Original-CSV herunterladen

  1. pcmattmankevin: also, ping here :)
  2. kevinAlso pong here ;-)
  3. pcmattman(for a different thing)
  4. pcmattmanBeen working on a git workflow for Pedigree - would you mind perusing it and criticising it as necessary? :)
  5. pcmattmanhttp://pedigree-project.org/projects/pedigree/wiki/Workflow
  6. kevinYay, processes! :-)
  7. pcmattmanI decided to finally get around to it :)
  8. kevinHm, not sure if I completely understand why you merge release branches with master and delete them and so on...
  9. kevinWouldn't it be easier to use the normal development model?
  10. pcmattmanIt could well be
  11. kevinThat is, master is for development, and for each release you have a branch like stable-0.2.x
  12. kevinIf you have any fixes to backport, you just cherry-pick it from master into the stable branch
  13. kevinAnd tags again for the individual releases
  14. pcmattmanI mostly agree - except I want stable to be the default, and development branches to be non-default
  15. pcmattmanI've had far too much time with non-building master to be happy with having that as the default every clone gets is all
  16. pcmattmanEssentially... protecting myself and the tree from the developers :P
  17. kevinNot sure about that
  18. kevinIf I want to have a stable version, I get a tarball
  19. pcmattmanFair enough
  20. kevinWhen I clone a git repository, I want to have the latest and greatest
  21. kevinAnd most broken, of course ;-)
  22. pcmattmanIs there a way to offer a clone URL for a specific branch? :)
  23. kevinDon't think so
  24. pcmattmanProbably a good thing
  25. kevingit clone has a -b parameter, so if you provide the whole command line, it might do the trick
  26. pcmattmanI'm still unsure about the semantics of release and hotfix branches
  27. pcmattmanThey've both had the least thought out of all of the other processes
  28. pcmattman(as you can probably tell... :P)