*Situation*

Although I try to keep changes small (and thus easily
discussable/verifiable), I have some difficulties to get patches into
trunk.

An example is this tiny patch, which adds 2 missing fields (essentially
a defect) into the ticket/api.py:

http://trac.edgewall.org/attachment/ticket/3990/TicketQueryMacroAddTimestampFields.diff

and which was finally moved to an dedicated ticket for simplification
reasons:

http://trac.edgewall.org/attachment/ticket/4019

Of course I understand that changes (patches) have to be verified prior
to going into trunk, and that commiters have other subsystems and tasks
in their mind, making it difficult to verify the patches with full
attention.

So, It seems that synchronizing a development effort based on patches
is not that easy (technically, organizational - this is _not_ a
criticism to the trac team).

-

*possibility*

Possibly a more effective way would be to create a branch, which could
be used for further tasks (like Query Module Refactoring), too.

Following the naming-scheme of the project, the location would be here:

http://trac.edgewall.org/browser/sandbox/query

*request*

So, my question to the team is:

Can I have a "query" branch, on which I continue the current task, thus
changes can be verified more easily and merged to trunk in one chunk?

Within this branch, I would initially continue this task:

http://dev.lazaridis.com/base/wiki/PlanTicketQueryMacro

and later some more work on the query system.

This way, patches that I provide could get applied by committers (no
need for immediate verification, as it's a sandbox).

Commit access for me (to this sandbox location) could simplify things
even more.

.


--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to