Changes between Version 20 and Version 21 of GitObjections
- Timestamp:
- 09/21/09 17:04:12 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GitObjections
v20 v21 28 28 * Answer 5.4: Every single git work tree of Parrot is a backup of the entire source code history. Currently, if the svn repo on parrot.org were to be hit by a meteor, we would be in a bad way. Our code is safer in git. 29 29 30 6. Objection: Upstream projects depend on getting Parrot from svn.30 6. Objection: ~~Upstream projects depend on getting Parrot from svn.~~ (cotto) 31 31 * Claim 6.1: Ensure that those projects are given sufficient advance notice of any VCS switch. This includes HLLs and derivative projects such as mod_parrot. A list of such projects should be maintained. 32 32 * Counter-claim 6.1.1: According to Parrot policies, HLLs and other projects should not be dependent on the VCS but should restrict their work to released versions of Parrot. Projects that choose to have a dependency on the master Parrot VCS do so at their own risk. 33 * This counterclaim is true. HLLs officially shouldn't be depending on Parrot's VCS. If they want to, they can figure something out or copy whatever Rakudo ends up doing. - cotto 33 34 34 35 As an HLL author, I can't track parrot releases exclusively by release. However, even when I do, I do not track it via svn, but by requiring the user to get their own copy and install it (So my issue is #7, below) --coke