Is there any chance of tagging the repository with version information any
time soon? It would make it a lot easier for those of us outside the inner
circle to help out. Also, is there a dev mailinglist?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Tags are meant to be immutable, Branches are meant to be worked on. I any
case, I too am glad to see that they are now (to some extent) using branches.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yeah - we were kind of wild-west subversioning there for a bit. We'll try to
get things more in line with standard operating procedures to help people jump
in to the project, but that's going to require some reading and some free time
on my behalf, which is getting hard to come by at the new job.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi guys,
Is there any chance of tagging the repository with version information any
time soon? It would make it a lot easier for those of us outside the inner
circle to help out. Also, is there a dev mailinglist?
Versions @ branches/ insufficient? It looks like a recent development on the
devs part (which I am thankful for!).
-nick
Nick (fill3r),
Tags are meant to be immutable, Branches are meant to be worked on. I any
case, I too am glad to see that they are now (to some extent) using branches.
Agreed ... even if svn inherently exposes tags as writable (!) ...
Yeah - we were kind of wild-west subversioning there for a bit. We'll try to
get things more in line with standard operating procedures to help people jump
in to the project, but that's going to require some reading and some free time
on my behalf, which is getting hard to come by at the new job.
After the 2.6 release, we're thinking of migrating the project to Github in order to help develop a community of contributors.