Re: [jamboost] Sourceforge file release system

From: David Abrahams (dave_at_[hidden])
Date: 2003-04-24 09:30:28

Vladimir Prus <ghost_at_[hidden]> writes:

> Hi Steven,
>
>> > 1. I though that a new "package" must be created, called
>> > "boost-build". Yet I failed to do so. Docs say there should be a
>> > button for creating new package, but I can't find it.
>>
>> Hmm, it looks like they've changed the admin pages since the last time I
>> released SCons...
>>
>> Go to your project's "Admin" page, then to "File Releases." Down at the
>> bottom of the page, there's a "New Package Name" box and a "Create This
>> Package" button.
>
> I certainly don't see this box/button, even though I'm told by admin page I 
> can manage files releases. Dave, probably the "boost-build" package must 
> be created by you...

Done.

>> I don't believe you can replace a released file. Even if you could,
>> IMHO you *really* don't want to do this. Releasing a same-named file
>> with different contents is a configuration management nightmare:
>>
>> "I found bug X, I'm using version 2.0-m3."
>>
>> "Is this version 2.0-m3 from before or after I updated the
>> file to fix packaging problem Y?"
>>
>> "Umm... I'm not sure...."
>>
>> You avoid all of those sorts of issues if you just start with the
>> assumption you'll increment a version number or release number or file
>> number each time you put a new file out there.
>
> Optimally, release should have two states: "open" and "closed". In the open 
> state you can download the packages, try them on other platforms and fix 
> errors. Once you "close" release and announce it, you can only make new 
> release. But probably SF can't handle this.

You just change the release name from "alpha" to "final", I think

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com