I would rather not mavenize the alpha-7 branch if at all possible, but instead only focus on bug fixes and other things like that. We can merge in any major fixes into the trunk where appropriate.

That's my general plan.

On 1/10/06, Leonardo Quijano Vincenzi <[EMAIL PROTECTED]> wrote:
Lots of these bugs should go to tacos-alpha-7 --> soon to be
tacos-beta-1. Let's not forget that for Tapestry 4.0 developers!

(How are we handling these ports?? Delayed merge of CVS branches is
tricky, since the directory structure changed and we might not want to
Mavenize tacos4-alpha7-pretap-4-1, right?)

Or do we want to do that?

Anyway, there's a bug on the Palette component I might want to check
out, and there's the MaskEdit issue I mentioned before, so I'd like to
set the guidelines before proceeding. We can:

1) Mavenize tacos4-alpha7-pretap-4-1 and do all fixes on that branch,
then merge to trunk.
2) Merge fixes manually between the two branches.

--
Ing. Leonardo Quijano Vincenzi
DTQ Software


Jesse Kuhnert wrote:
> Has this been logged into the bug reporter? I'm much more likely to do
> bug fixing in large chunks right now, so if you get it in there in
> time I'll be able to fix it. It does seem like a high priority-ish
> item though.




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Tacos-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tacos-devel

Reply via email to