Alan Manuel Gloria:
> >> Do we need to implement #{weird symbol}# syntax in the Guile
> >> compatibility layer? I forgot to do it, sorry!
I said:
> > No problem, I just implemented it, if by "guile compatibility layer" you
> > mean process-sharp and friends. It was trivial.
> Err, I mean the part which starts with the comment "; Guile
> Compatibility", actually. Basically the portability API thingy.
> Anyway I'll move it into the Guile compatibility layer, as other
> Scheme's might have a different syntax for weird symbols.
Okay. Bundle applied!
> I checked, and different Guile versions treat control and space
> characters differently
...
> Ah well, I'll see if I can get myself to bother to do it properly or not.
Okay. Since it even varies between guile versions, I suspect that far fewer
programs depend on it. Anybody who wants something even slightly portable will
use string->symbol or similar anyway.
> >> We might then need to fork branches for stable/0.3 bugfix and
> >> unstable/provisional 0.4 after release.
> >
> > Yeah, we can tag and branch at that point. Hmm, we need good names for
> > branches, I'm not sure those are it.
>
> Hmm....
>
> stable - latest stable branch, including bugfixes, so 0.3, 0.3.1 etc.
> unstable - latest development branch
> r0.3 - tag for release 0.3 (or v0.3 if you prefer "version")
I don't know about those names, but I agree that we need those 3 branches. I
started googling, and boy, there are a lot of conventions; it's not obvious
what's a good one. An interesting essay is:
http://nvie.com/posts/a-successful-git-branching-model/
though I find it odd that he considers "master" the "production" branch (I
would have called master the development branch).
I think we need to have *clearly* different names between a released fixed
version ("v0.30") and a branch based on a fixed version (e.g., "r0.3" for
"series based on v0.30" - i.e., for hotfixes of 0.30).
--- David A. Wheeler
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Readable-discuss mailing list
Readable-discuss@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/readable-discuss
