What is “Giant commit” all about?

  • I try to keep up with the new changes and try to understand them. In the case of the ‘giant commit’ I can’t find any simple explanation what this is all about? Is it something important. I mean, important enough to do an upgrade?

Viewing 4 replies - 1 through 4 (of 4 total)

  • think i will first upgrade to 1.2 and stick with it for sometime ??

    Thread Starter Jack

    (@moxie)

    Perhaps I misunderstand you here, but I look on the CVS site now and then to see if files are modified which are of interest to me (like including the excludefunction in the dropdown_cat), and I suddenly saw a lot of files were modified for the same reason. But I don’t see the reason? Or is it better to just leave those things where they are and wait for a regular new release?
    In short I find it difficult to keep an overview of what is going on. Are reported bugs handled? And if they have, how will I know? Like in the case of that exclude-thing. I’m not so good at php, so do I really have to look each evening in the cvs to see if something has been changed?
    I’m very thankfull for software like this, but sometimes it eludes me to see that some minor tweaking has been done to files, but some major issues here and there on the forum are left out. Like the loginproblem which is mentioned quit often.
    I know. It’s all done by people. And people have more than one life…
    I’ll be patient… ??

    Don’t use CVS HEAD, it is undergoing major changes. Bug fixes for 1.2 are happening on the WordPress-Ver-1_2_1-Branch branch.

    That big update looks to be a change in some naming conventions in WordPress. A good step to standardization in the project.
    Thats what i gathered anyhow.
    Most people should do as rboren pointed out, stick to WordPress-ver-1_2_1-Branch.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘What is “Giant commit” all about?’ is closed to new replies.