Hello,

Things were very quiet from my side these past months, but I intend to progressively come back to a more intensive participation.

Among the first steps I'd like to take would be to work towards a 1.0beta1 release (as it's going to be 1.0 and not 0.13, remember? see [1] if not ;-) )

We have a pretty good state on trunk, and though it feels a bit unfinished here and there, I think it's at least as good as 0.12-stable stability wise, so why not get more exposure for the new features and APIs? We can always make things a bit better and more polished in a later 1.0.x maintenance release.

One big reorganization that I think would still be important to do even before the beta1 is the move of the svn support to tracopt. Now that we have Git support there, there's no reason to keep svn directly in trac/versioncontrol (see [2]). I think we can leave around a few imports for backward compatibility. I created #10712 for that.

Besides that, I'll go through some of the pending patches that can finished soon, then upgrade the version numbers, prepare the beta release and get some feedback from the field.

And then, what I'd really like to finish before the final 1.0 are the other tickets listed in TracDev/ToDo#Trac1.0.

That's the plan so far ;-)

-- Christian


[1] - https://groups.google.com/forum/#!msg/trac-dev/17DO_N1MM-A/nbhupXw0NAIJ
 [2] - https://groups.google.com/d/msg/trac-dev/hCwTylvQ_FU/QNNWsHgZtGgJ

--
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To post to this group, send email to trac-dev@googlegroups.com.
To unsubscribe from this group, send email to 
trac-dev+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/trac-dev?hl=en.

Reply via email to