Skip to content

[Bioc-devel] Final Release Plans (fwd)

2 messages · Jeff Gentry, A.J. Rossini

#
Since several people have now alerted me that they never received Tony's
release timeline that he sent out on Thursday, I'm sending it back out
again.  Note the line that states that packages must pass check by this
Friday.

---------- Forwarded message ----------
Date: Thu, 22 Apr 2004 09:05:16 -0700
From: A.J. Rossini <rossini@blindglobe.net>
Reply-To: rossini@u.washington.edu
To: bioc-devel@stat.math.ethz.ch
Subject: [Bioc-devel] Final Release Plans


I've been having computing disasters related to a too-warm lab room.
Apologies for all delays.  I hate troubleshooting RAID arrays, video
cards, and monitors when it's not really my job :-(.

I've contacted a few of you about reviews, we've gotten a few back
(thanks!) and I need to contact more of you about reviews.   Ideally,
we'd get them from you early next week.   See the important dates for
what I have planned, and what activities need to be done over the next
few weeks.

Yesterday was the last day to check in new packages for release, and
they need to pass R CMD check NEXT FRIDAY.  

Here are the updated timelines.

IMPORTANT DATES AND TIME-LINES:


    * March 15 -- April 26, review packages for: Usage (UI and API)
     and bugs. (open to everyone, with some particular
     assignments). This should focus on usage rather than
     correctness.

    * April 26 -- May 7, last chance for major changes during these 2
     weeks.

    * May 7 -- 12, bug finding and fixing, only changes to code
     required for bug fixes allowed

    * May 14 -- May 21, NO CHANGES TO CODE WITHOUT VERIFYING FROM JEFF
     GENTRY OR TONY ROSSINI (this doesn't mean not to change, but
     don't commit to the repository, send changes to Jeff or Tony)

    * May 21 -- branch the 1.4 version, and back to regularly
     scheduled development and research.

PLEASE NOTE THAT WE HAVE SOME PLANNED POST-RELEASE SLACKTIME FOR POTENTIAL BUGS

The important dates are

    * April 21 -- Last day to check in new packages for the 1.4 release
    * April 26 -- FEATURE FREEZE, bug finding and fixing starts.
    * April 30 -- All Packages should pass R CMD Check or will be
                  taken out
    * May 7    -- CODE FREEZE and validation.
    * May 12   -- Distribution construction.
    * May 15   -- Planned Release.
#
You might get this twice, but please note, we've entered FEATURE
FREEZE.  Which means that you should work hard to make sure that your
packages pass "R CMD check" by Friday.  If you need help, please
contact Jeff or myself.  I'll be in DC for trials meetings next week
(Sun-Thurs) so will both have more time (during meetings) and less
connectivity.

I've got some reviews to pass around, and I have some people who I
need to get reviews from, and I have some people that I need to talk
with to do reviews.  If you've not done one or have not talked with me
about doing one and would prefer some choice, mail me with what you'd
like to do.  Otherwise, I'll be contacting you real soon.

Most of what lies ahead is documentation.

best,
-tony



Jeff Gentry <jgentry@jimmy.harvard.edu> writes: