Manuzhai wrote:
...
I just always get confused when there's a notice about a merge
(whether it is about merging the branch up to latest trunk or merging
the branch *to* the trunk).
A notice on the mailing list or in changesets?
When we mention a merge here, it's always about merging the feature in
trunk, as the other way round is just technical to keep a branch
current, it's never mentioned here.
The latter changesets are always labelled "<branch name>: merged trunk"
or trunk replaced with the appropriate log:[EMAIL PROTECTED]:to TracLinks.
It seems to me, though, that the workflow part, while nice, will take
to long to finish before 0.11.
Probably, yes.
I have no clue how hard your number 4
is, but it seems like it's not that essential.
Ok, but we'll see if the mimeview fixes will eventually trigger
something to happen there ...
... I think it would be a good time to start moving
most of those over to 0.12, except for the ones that are actually
viable for 0.11.
I see this to happen next month maybe, not now.
I also think 0.11 is in a pretty good state right
now, and while it may be a little low on user-facing features (Genshi
and Pygments are interesting to developers, but not so much for users
of the system;
Not true for Pygments; 1) it's easy to install compared with the other
highlighters 2) it's much more powerful. 3) the user can select the
rendering style she likes most...
WebAdmin was already there, setting your timezone is
not that big of a deal for most people, I presume
A related change I'd like to see would be the ability to select the way
date and time are displayed.
-- but the blame support is pretty cool), I think it would make for a
good incremental
release kind of thing.
Exactly, I think that with this we have a good incentive for people to
upgrade, even if the workflow is _still_ not there. The features in the
other pending branches will also provide a few nice user-visible features:
- timeline-link-resolver adds links back to the timeline from most
displayed dates and ages
- property-renderers adds the ability to implement custom property
renderers, with some useful default implementations (wiki renderer, svn
renderer for svn:externals and svn:needs-lock)
- last but not least, the security branch will also bring/enable a lot
of enhancements
-- Christian
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac
Development" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/trac-dev?hl=en
-~----------~----~----~----~------~----~------~--~---