It's not stable enough to do point release systems. No formal system for stable
branch vs dev branch. No central design control. No branch or release
maintainers. Need to get people and time and responsibilities set before you
can do that. Best to focus on migration to github first. At least the
[I sent this yesterday already to the list but it looks like it didn't go
through, sorry if this is now the second mail...]
Every previous committer got back to me and agreed to be included in the git
history with name and email, thanks to everyone!
I now have an experimental git repo at
https://
Hi everyone,
if we do migrate to git, we should have a branching scheme for the project.
I would suggest we just go with git flow
(http://nvie.com/posts/a-successful-git-branching-model/). It is widely
used, well documented, lots of people are familiar with it and we don't have
to come up with our
Every previous committer got back to me and agreed to be included in the git
history with name and email, thanks to everyone!
I now have an experimental git repo at
https://github.com/pythonnet/pythonnet. PLEASE don't use that for anything
real yet, I expect more rebases before the migration is
Hi everyone,
I'm trying to understand what the "official" release history is right now.
PythonNet 2.0 was never officially released, correct? Was the last release
2.0 beta?
In any case, I think it would be great if we released an official 2.0
version, provided binaries for download etc.
My gut s
