Hi Jesse, think you are wrong with the assumption that dojo does not necesserily needs to be updated in tacos 4.0. dojo is moving way to fast in the moment (think about their pane refactoring) as it could be "frozen". At least not till 4.1 is out of the door which might take quite a time.
Otherwise it would mean for users who want to use tacos and some more recent dojo to have two dojo versions installed which sounds tricky. Yeah but this looks like a manpower issue. I see your point with breaking the current code with a new dojo snapshot. They don't care much about backward compability ;-) my 2cents, Markus On 1/13/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote: > You're right Felix, maybe it's about time that we start a tacos4.1 roadmap > wiki page as well. > > It doesn't seem unreasonable at all to relabel the tacos4-alpha-7-pretap4-1 > branch to just tacos4.0 at all. I'd still prefer to keep the branch on > whatever the latest and greatest is, but maybe even there it is better to > branch when you're guaranteed to have everything broken (as in my maven2 > move sitting there now) . > > I will save most of this for the roadmap, but to answer your questions: > > -) I'm hoping that tacos4.0 will move from alpha to beta relatively soon > with us focusing on bugfixes and tiny tweaks here and there for now with the > eventual goal of releasing a final tacos4.0. > > We can try upgrading dojo if we want, but I already had to change some > things in trunk to get it working again (mostly with floating panes), so if > someone wants to do it they'll have to take responsibility for any and all > changes that need to be made to keep things stable.(we are trying to get > more stable, not less) > > -) Besides bugfixes and tiny tweaks I don't see myself doing a whole lot of > active development in tacos for the next two months or so, though I'm sure > there will be plenty of spilloff sitting in branch of me playing around with > new features in tapestry4.1 to see if the api feels right from a client/user > perspective. (Maybe I should start creating another demo app in tapestry, > haven't figured that one out yet) > > -) The naming conventions of tacos4.0 and tacos4.1 mimicking tapestry seem > like the easiest path for me. I'm pretty lazy anyways so if it's already > inuitive for people to know that we're doing this then all the better. Of > course everything is up for debate, I don't have the last say in any of > this. > > That's basically it. The testng patch work is done for the most part now, > there'll probably be some bug fixes and such once in a while that I work on > but the majority of my time will be in tapestry4.1 for a while, with the > disclaimer that everything I'll be doing will be directly beneficial to > tacos ;) > > How does everyone else feel about this? Do you think tacos is going in the > wrong direction, am I leaving other considerations out? > > On 1/13/06, Felix Sun <[EMAIL PROTECTED]> wrote: > > I feel a bit confuse about the current development status. and lost my way > on the next step development. > > Here is what I am trying to understand: > > > > * The tacos4-alpha-7-pretap4-1 is the further development branch of > tacos4-alpha-7 > > which would be based on Tapestry 4.0 + latest dojo?(or not? ) > > > > As Leonardo said we should not forget that for Tapestry 4.0 developers > > only bugfix should be made to this branch, if there are bugs caused by > dojo, then we may update dojo, right? > > and in the future, we may release tacos4-beta-1, tacos4-beta-2, .. tacos4 > final? and this branch is built by Ant. > > If so , I think we should call this branch *tacos4* which following the > Tapestry 4.0 > > and I am not sure whether we can do that further to release tacos4 final, > > maybe far before that time the main focus should be on HEAD branch. > > > > * The HEAD branch is based on latest Tapestry(4.1) + latest dojo? > > We may do a lot of big refactorings and even change the whole structure of > the project. and is built by Maven2 > > Is that we are going to call it *tacos4.1* which following the Tapestry > 4.1? > > > > Which branch we should emphasize on now? > > > > > > > > ------------------------------------------------------- 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_idv37&alloc_id865&op=click _______________________________________________ Tacos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tacos-devel
