Release of 6.x-1.0-alpha2
BenK - May 20, 2008 - 15:28
| Project: | Content Construction Kit (CCK) |
| Version: | 6.x-1.0-alpha |
| Component: | General |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
Just a quick question: With the recent release of Views 6.x-2.0-beta3, will there be an alpha2 release of CCK in the not-too-distant future?
Thanks,
Ben
#1
Subscribing...
#2
Me too ...
#3
and me...
#4
I'd add a question to the originally posted in this support request. Are we in a point for CCK in which using the most recent development snapshot is more sensible than using 6.x-1.0-alpha?
I'm in a bit of a rush because we're trying to put into production a website next June 1st and we absolutely need CCK. :-)
TIA
#5
subscribing
#6
Sorry for the absence from this issue queue -- I'm focusing on getting Date and Calendar working right now.
Yes, I think the latest dev version is as good or better than the alpha version -- I'm running on that -- but I'm not sure that there's a lot of difference because no one has had time to work on CCK much since the alpha was released.
#7
What the community can do to speed-up the development of CCK 6.x ?
Is very hard, but Drupal can live without Views, but can NOT live without CCK, so what can we do ? Many people want to help, where can we start ? Would be good to write a post on g.d.o about the status of the migration, next steps, etc... Maybe this post already exists... does it ?
#8
Bounties are good motivators.
#9
[...] because no one has had time to work on CCK much since the alpha was released.i'm sorry, but this is a little bit irritating. i agree with dropcube, CCK is more important than Views.
Coordination between this modules is important and saves resources, but i always thought views has to follow the concepts of CCK.
greetings momper
#10
@momper - I'm sorry but it's a little bit irritating to spend hundreds of unpaid hours working on getting several important modules upgraded only to have someone who doesn't contribute anything demand that I drop everything else and fix the things that matter to him. There are many people who would disagree whether Views or CCK is more important, they're both important.
@dropcube and others - people keep asking the same thing and I keep saying the same thing -- review patches and let us know if they work, review bugs and propose patches. There is one whole page of 'patch needs review' issues against the D6 version but no one is testing them or marking them ready to commit. There are two pages of active bugs for D6 that have no patches that someone could propose fixes for. People keep reporting bugs against the alpha release but no one is testing whether the bug is already fixed. All the alpha 1 issues should go away -- either marked as fixed in -dev or upgraded to -dev to indicate the bug is still there in the latest code.
Some issues are pretty complicated if you're not an expert in CCK, but others are not. If someone worked on these things, those of us who know CCK could focus on the remaining issues.
#11
@KarenS: Thank you for your comments, I agree with you 100% and appreciate your hard work here...
#12
Ok, at least answer this. Although I know that CCK 6 is considered "alpha" right now, is it still considered "safe" to just start using it and putting data in the tables? So when a new alpha or a new beta comes out for cck, we can simply upgrade the module without worrying about a table schema screwing things up? If more people use it, more people can test it, so we can all roll this out sooner.
Also, perhaps we can start applying simpletest to cck? From my experience, unit tests makes things a LOT easier to change. Refactoring becomes a lot easier so people tend to do it more.
#13
@dropcube -- not only do you ask, you respond!! Thanks!! I'll reward that great effort by diverting myself from my other projects to follow up on the issues you've been reviewing :)
@steveeq -- the D6 version has simpletest, but there are only a couple tests. Someone has to write others, but they would be welcomed if you're volunteering. At this point I would say the table schema is not going to change and that if it did there would have to be an upgrade to fix it, so you shouldn't have to worry about that.
#14
I just created a D6.2 branch and a D6.2 beta release. Don't continue to use 6.1 (which is really HEAD) since HEAD is going to be opened up for D7 work.
I forgot to add the release notes into the beta release, but you can see them on the project page under 'View all releases'.
#15
Karen, you're so awesome. Thanks so much.
#16
Automatically closed -- issue fixed for two weeks with no activity.