Dirk wrote:
Hi Toby

Sounds good. Actually I was thinking about just going full-bore and issuing a 1.0 release. I think that most of the major issues that most users would encounter when converting their repo have been solved, and I don't really see us adding any major new features unless someone else decides to take over. I first need to go through the ticket list again and see if there are any major issues that still need resolved. What do you think?

I have a few more pending local changes that are new features, but which are very interesting:

* fine grained label mapping support
* better detection of UNPIN/PIN activities
* detection of comments in UNPIN/PIN activities
* omit commits if PIN/UNPIN does not change update the state of the file
* Handle PIN/UNPIN as commits and not as copy from activities.
* don't break recursive SHARE/PIN activities into multiple revisions.

All these changes will give a much better history of the converted archive. In my opinion this should go into a 1.0 version.

I will do my very best to go through my issues this week. Beginning at the end of this week, I will be very busy again with other task, so I don't expect to have any more time to contribute to this project again for some amount of time.

Hi Dirk,

I saw that you have just made numerous commits; I am out of town for the
rest of the week and am just now checking my email but it looks like you
have cleaned up many hanging issues and enhancements! Thanks very much
for continuing to contribute to this project.

Hopefully I too can work on going through the issues soon to figure out
the ones that can reasonably be completed in order to get a 1.0 out the
door.

toby

_______________________________________________
vss2svn-users mailing list
Project homepage:
http://www.pumacode.org/projects/vss2svn/
Subscribe/Unsubscribe/Admin:
http://lists.pumacode.org/mailman/listinfo/vss2svn-users-lists.pumacode.org
Mailing list web interface (with searchable archives):
http://dir.gmane.org/gmane.comp.version-control.subversion.vss2svn.user

Reply via email to