PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 14 Jun 2011 12:00 AM by  SuperUser Account
HICDEP release process
 3 Replies
Sort:
You are not authorized to post a reply.
Author Messages


Basic Member


Posts:289
Basic Member


--
30 May 2011 10:50 AM

    Hello everyone,

    As Charlotte and Jesper pointed out at the last TC, the release process for new HICDEP versions is currently undocumented. I'm about to change that, here's what I came up so far:


    roughly every year, the following happens:

    • 4 weeks before a WP4 TC, I post a message to the discussion board stating that the version currently visible in the wiki is now considered a candidate for release as-is
    • WP4 members forward the message to any data managers or researches they know who might have valuable feedback
    • Within the first 3 weeks, everybody (including external parties) may comment and changes are still possible
    • A week before the TC, the wiki pages are frozen
    • at the TC, we discuss any issues and in the decide to release the current version or not
    • If accepted, I perform a version bump, mark the version as stable, produce a downloadable PDF and create a new set of wiki pages for the next draft version. The changes from the last stable version to the current stable are outlined in the ChangeLog

    Are you all fine with this? I think the extra look by external parties is quite a critical step... Do you think 3 weeks is too long/too short to get actual feedback? If noone objects, I will document this process on the HICDEP homepage a bit more formally in a week or so.

    Kind regards,

    Simon



    Basic Member


    Posts:289
    Basic Member


    --
    01 Jun 2011 12:00 AM


    Hi Simon

    Thanks for your email. I like what you have suggested, and think that 3 weeks is a reasonable timeframe for feedback. If we made it any longer we might risk people forgetting to comment.

    Just one suggestion though - is it possible for you to create a downloadable PDF for the draft version, which we can send to external parties for comment? I guess it would be easier for you if everyone viewed the tables on the wiki pages, but some of our EPPICC collaborators might find this a bit beyond their IT skills and may be more likely to comment if given an pdf attachment.

    Thanks and best wishes Ali


    Basic Member


    Posts:289
    Basic Member


    --
    06 Jun 2011 12:00 AM


    Just one suggestion though - is it possible for you to create a downloadable PDF for the draft version, which we can send to external parties for comment?

    That's a very good point, I will make sure to provide one. It's probably still worth pointing these collaborators to the website in case they are curious, but handing them a PDF is surely the right thing to do.

    Kind regards,

    Simon


    Basic Member


    Posts:289
    Basic Member


    --
    14 Jun 2011 12:00 AM
    The process is now also described in ReleaseProcess which is accessible via the homepage.
    You are not authorized to post a reply.