I've come to realise that people using the proton-c Go binding via 'go
get' can be making direct use of the content from the "go1" branch of
the proton repository. Some updates were just pushed to the branch
bringing it up to date with master, effectively 0.18.0 rc1 from
yesterday plus some cosmetic changes like comments and clarified
parameter names. Since 0.18.0 is still under vote this shouldnt be the
case if the go1 branch contents are so directly related to what a
regular Go user ends up using (i.e not someone following development
and deliberately aiming to use development content). If thats the
case, then the branch needs to hold the content of a release and only
be updated after an associated release vote has passed.

Robbie

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org

Reply via email to