Homepage | Products | OX Knowledge Base | Support | Try Now | Contact | Company
OX Logo
Results 1 to 8 of 8
  1. #1
    neo Guest

    Default Web-CVS acces to the repos

    Hello,

    is it possible to have a web cvs acces to you repositories?

    So it is possible to view the changes online and determine what happened in the past.

    greetings
    Andreas

  2. #2
    Join Date
    Feb 2007
    Location
    Olpe
    Posts
    199

    Default

    This is one of the things we are discussing at the moment.

    Daniel

  3. #3
    neo Guest

    Default

    Quote Originally Posted by Daniel Halbe View Post
    This is one of the things we are discussing at the moment.

    Daniel



    And what about the build versions?

    I'm testing nearly every day and it is still build number 6048 or did I miss somethin?
    So it is a bit hard to explain bugs to a given build number because it does not change but the code does.

  4. #4
    Join Date
    Feb 2007
    Location
    Germany
    Posts
    3,695

    Default

    Uhm, thats a point for sure, lets investigate about this tomorrow

  5. #5
    Join Date
    Feb 2007
    Location
    Germany
    Posts
    3,695

    Default

    I talked about this with the server development team leader. The case that there is a build number in the current community edition itself is a bug, because you check out the source, the build number is set when building the package on your machine. For sure this is not usable for bug reports, please provide the checkout date instead of the build number when reporting bugs. At least until the build number problem has been fixed.

  6. #6
    neo Guest

    Default

    Ok, thanks for the fast answer.

    Another thing to mention is, what about the status of CVS?
    At the moment it does not compile cleanly.

    Could it be possible to remain the CVS in a stable state (or some sort of stable state)?

  7. #7
    Join Date
    Feb 2007
    Location
    Olpe
    Posts
    199

    Default

    Hmm, problem is that a realtime cvs is wanted by many code contributors. On the other side we loose stability with this because we can not guarantee you can build a full functional ox at time x.

    Had a longer talk with Francisco from development team while travelling back from german Cebit, we arrived in office olpe ten minutes ago Perhaps best solution would be to update the CVS every week / two weeks and review the build results via tools like cruisecontrol before updating public cvs.

    R&D has to take a descision - the above is only my opinion as non-developer

    Daniel

  8. #8
    neo Guest

    Default

    Quote Originally Posted by Daniel Halbe View Post
    Hmm, problem is that a realtime cvs is wanted by many code contributors. On the other side we loose stability with this because we can not guarantee you can build a full functional ox at time x.

    Had a longer talk with Francisco from development team while travelling back from german Cebit, we arrived in office olpe ten minutes ago Perhaps best solution would be to update the CVS every week / two weeks and review the build results via tools like cruisecontrol before updating public cvs.

    Hmm, what about the idea to setup two CVS (one public and one for code contributors) or creating a branch with an increased buildnumber and a clean compile would help a bit. Of course the branches are out of scope because they are development snapshots.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •