After making a new release, the text in the link for the default download on the project page was missing the release number. I had to edit the project page and save it with the new release number. Other than that, it looks fine.
<br><br><div><span class="gmail_quote">On 10/16/06, <b class="gmail_sendername">Derek Wright</b> <<a href="mailto:drupal@dwwright.net">drupal@dwwright.net</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
i'm pleased to announce that v0.1 of the new release system is Done<br>Enough(tm). of course, the system isn't completely done, in the<br>sense that no further improvements could be made. ;) i just think<br>it's at a point of functionality and usability that we could install
<br>it, start using it, and make incremental improvements going forward.<br>therefore, the 2 main issues now need review:<br><br>"make releases real nodes"<br><a href="http://drupal.org/node/83339#comment-145779">
http://drupal.org/node/83339#comment-145779</a><br><a href="http://drupal.org/files/issues/release_as_node.patch_27.txt">http://drupal.org/files/issues/release_as_node.patch_27.txt</a><br><br>"port cvs.module to releases-as-nodes"
<br><a href="http://drupal.org/node/84706#comment-146000">http://drupal.org/node/84706#comment-146000</a><br><a href="http://drupal.org/files/issues/cvs_release_node.patch_17.txt">http://drupal.org/files/issues/cvs_release_node.patch_17.txt
</a><br><br>these apply against DRUPAL-4-7 of project, project_issue and cvslog. [1]<br><br>i don't expect everyone to review every line of code (or even<br>understand all of it -- i had to do some fairly nasty FAPI tricks to
<br>make the UI as smooth as i could for adding new releases). however,<br>all of this is going to run on d.o and so we need to make sure it's<br>all secure, the performance isn't going to be a problem, and that it<br>all works how we want. so, any reviews would be most appreciated
<br>(and obviously essential before the whole system can go to go live).<br><br>if you're not a heavy-weight drupal coder and don't feel up to the<br>task of reviewing this stuff, you can still help by playing with the<br>
new system on a test site i've setup:<br><br><a href="http://drupal-release.dwwright.net/">http://drupal-release.dwwright.net/</a><br><br>this is running a modified copy of a DB snapshot from <a href="http://drupal.org">drupal.org
</a> as<br>of about 2 months ago. all the email addresses have been stripped<br>out (so trying to reset your password won't work!), and a few of the<br>modules have been disabled (namely all the forums and aggregator/blog
<br>stuff). new account creation is disabled, but everyone with accounts<br>on d.o can log in with their d.o username/password circa 2 months<br>ago. projects and issues are of course still enabled. there's a<br>scratch copy of the contrib cvs repository, too. this is just a
<br>shared hosting box, so the performance is pretty terrible. ;) don't<br>let that scare you (and please be gentle on the site). ;)<br><br>the main thing i need are people who maintain projects (modules,<br>themes or translations) to login to the site, go to your project
<br>page, and try adding some new release nodes. i haven't yet written<br>the handbook pages, so i'll just briefly document the process for<br>adding a release here:<br><br>1) create a cvs tag for your release<br>2) navigate to your project node
<br>3) click on the "add new release" link<br>4) fill out the N-page form (which involves specifying the tag you<br>want to use)<br>5) wait for the cron job to package your release based on the tag [2]<br><br>since it's going to be too much of a pain in the ass to give y'all
<br>access to this test site's cvs repository, i just created some tags<br>across the entire contrib repo for your testing enjoyment. there are<br>a few release tags and a few branches for each project. if anyone<br>wants additional tags created you can let me know (preferably when
<br>i'm on IRC, or else via email).<br><br>if you add a release node and point it to a branch, that means you<br>want nightly development snapshots created from that branch. the<br>conversion script that i ran (and which will run on
d.o)<br>automatically creates these release nodes for you for any existing<br>releases (which are all snapshot releases from branches). however,<br>to give y'all a sense of how things will work in the long term, i<br>removed all the HEAD-specific releases for all the projects, so folks
<br>can see what's it's like to add a release node for both the HEAD<br>(which is a special case for various reasons you'll see when you fill<br>out the form) and for a regular branch (DRUPAL-5).<br><br>my goal is that the UI makes enough sense that i don't have to say
<br>anything else. however, i'm sure some of you will be confused in the<br>absence of any documentation, since i admit that some of it is pretty<br>complicated. ;)<br><br>in addition to adding releases, you can poke around with how releases
<br>interact with the issue queue, the project browsing pages, and the<br>project nodes themselves. the last 2 in particular are areas of<br>future work, but you can help verify that what's there isn't any<br>worse than what we already have. ;)
<br><br>thanks for any testing, feedback, and most importantly, code reviews!<br>i can't wait to get this all committed and installed on d.o!!!<br><br>-derek<br><br><br>p.s.: there are a *ton* of ideas i have about new features we can
<br>build on top of this. at this point, i'm not very interested in that<br>-- i just want to get the basic system commited to cvs and install it<br>on d.o. please file other feature requests and ideas as separate<br>issues, instead of posting replies here, or following up to the 2
<br>issues i linked to above.<br><br><br>notes:<br><br>[1] for convenience, a tarball of the latest code from those 3<br>directories, with the 2 patches already applied: <a href="http://drupal-">http://drupal-</a><br><a href="http://release.dwwright.net/files/new-release-2005-10-15.tar.gz">
release.dwwright.net/files/new-release-2005-10-15.tar.gz</a><br><br>[2] the cron job packages releases from tags every 5 minutes, and<br>does the snapshots from branches every 8 hours. for the interested<br>reader, the packaging script itself is a separate issue: http://
<br><a href="http://drupal.org/node/88056">drupal.org/node/88056</a><br><br></blockquote></div><br>