#41478 File release system issue

Chris Conrad

I've used the Quick Release system to release a big
number of files on the jext-plugins project. Since for
each release I provide both a source and a binary file,
I've submitted for each package with QRS two files with
the same revision, but they resulted being stored as
two separate revisions(i.e. I have package jHierarchy
and two releases 1.0 of it, one with the src and one
with the bin file). Would you like to
a) join the releases of the same package and with the
same name together: it's ugly the download page with
same files together and some in different releases, and
it also makes slower editing releases)
b) fix the bug in the qrs page, so that this doesn't
happen any more.


  • David Burley
    David Burley

    • milestone: --> Second Level Support
    • summary: jext-plugins project releases --> File release system issue
    • assigned_to: nobody --> regs
  • David Burley
    David Burley

    Logged In: YES


    This canned response is used by the SourceForge.net team to
    convey information about how this Support Request will be
    handled. Please read the entirety of this comment before taking
    any further action; information enclosed in this comment will
    help you to ensure that you have an excellent support experience.

    The SourceForge.net team takes all reported issues seriously; we
    will work to provide you a complete, accurate, and timely
    response to your inquiry. Information about our support policies
    and procedures may be found at:

    ABOUT THIS ISSUE: Based on the initial review of this request, we
    have determined that this issue will be considered to have
    Moderate Priority (this is signified by the summary line we use
    on this request, not by the Priority setting on this request).
    Issues within this category typically include service questions,
    usage problems, and specialized requests (such as those requiring
    significant administrative overview, or which require the
    development of a custom solution). A description of this class
    of issues may be found at:

    TRIAGE PROCESS: The initial review of this issue has resulted in
    a member of the SourceForge.net staff determining who should
    process this issue, and a change in the Priority, Summary,
    Assignee, Group and Category settings for this request. We use
    these settings solely for grouping purposes; as the submitter,
    you SHOULD NOT change any of these settings. Since we use all of
    these settings to group issues for faster response, you should
    understand that changing any of these settings (particularly the
    listed Priority setting) will result in significant delays in the
    processing of your request.

    WHAT TO EXPECT: Issues of this nature will typically be reviewed
    again by the assigned member of the SourceForge.net team within 5
    business days (the SourceForge.net team works at least Monday
    through Friday, 9am to 5pm Pacific, excepting holidays). Within
    our next response, we will typically request additional
    information about the problem you have reported, or provide you
    specific troubleshooting instructions. Please wait patiently for
    our next review of, and response to, this request.

    questions or concerns regarding the status of this issue, simply
    add a comment to this support request. All comments you post to
    this support request will be received by the SourceForge.net team
    member who has been assigned this issue. Please do not submit a
    second support request about this issue (add a comment to this
    request instead), and do not attempt to contact the assignee of
    this request via email; all additional information or comments
    about this request should be posted as a comment to this request.

    Thank you,

    SourceForge.net support

  • Jacob Moorman
    Jacob Moorman

    • assigned_to: regs --> rhavyn
  • Jacob Moorman
    Jacob Moorman

    • summary: File release system issue --> File release system issue (PENDING CF 10/2003)
  • Jacob Moorman
    Jacob Moorman

    Logged In: YES


    The SourceForge.net engineer assigned to process this issue
    is currently tied up with other projects. The
    SourceForge.net site code base is currently in a code freeze
    as we are in the process of preparing the site for a major
    upgrade. This comment has been posted to notify you that a
    member of the SourceForge.net team has reviewed this issue
    and we believe it is non-critical (it can wait until after
    the code freeze is thawed, sometime in the early Fall
    months). As such, no further updates will be posted to this
    request in the next couple of months; this update has been
    posted as that you will know the time frame when this issue
    will next be reviewed.

    Should you have questions or concerns regarding this matter,
    please add a comment to this Support Request. Your patience
    is appreciated.

    Thank you,

    Jacob Moorman
    Quality of Service Manager, SourceForge.net

  • David Burley
    David Burley

    • summary: File release system issue (PENDING CF 10/2003) --> File release system issue
  • Jacob Moorman
    Jacob Moorman

    Logged In: YES

    Paolo: Please provide the exact filenames of the files you
    want moved to a single release and the exact text name (or a
    URL) to that release. We will be glad to honor your request
    and adjust the releases for your project accordingly once
    this information has been provided. To respond, add a
    comment to this request.

  • Jacob Moorman
    Jacob Moorman

    • status: open --> closed