Changes between Version 25 and Version 26 of GitObjections

Show
Ignore:
Timestamp:
05/04/10 18:58:19 (5 years ago)
Author:
coke
Comment:

update point 7 based on experience in recent months.

Legend:

Unmodified
Added
Removed
Modified
  • GitObjections

    v25 v26  
    4141   * Answer 7.1 : HLL's should be tied to a released version of Parrot. 
    4242 
    43 This may be reasonable for HLL '''releases''', but not for HLL '''development'''. That said, a harder time figuring out which versions are OK is fine, as long as it's not impossible. I can even remove the programmatic check and simply warn the user. If we do develop a programmatic solution, this cost can be shared among those HLL implementors that need it. --coke 
     43This may be reasonable for HLL '''releases''', but there is a concern for HLL '''development'''. Given parrot's monthly releases, I have found that any work I'm doing is either OK against the last monthly release, or that I just need to track svn HEAD and fix any potential backward incompatibilities that arise; Practically, this hasn't been a real pain point for me at all - Coke. 
    4444 
    45458. Objection: ~~Windows support for git is not first-class.~~