Re: [Slashcode-general] Will there be a new slashcode releaseat sourceforge ?

[Shane Z. <sh...@lo...>]

On Feb 13, 2008, at 2:52 PM, Larson, Timothy E. wrote:

> William Scott Lockwood III <> wrote:
>> Ever?
>
> I think the idea for a long time now has been that you can always pull
> the most recent stable tag from public CVS, so why do you need a
> tarball?
>
> A quarterly(?) notice (on this list and the site) as to what that  
> tag is
> would be nice, though.

Well, it's not that difficult to find out what the latest tag is:

Macintosh-2:~ shane$ cd /tmp
Macintosh-2:tmp shane$ cvs -d:pserver:ano...@sl... 
:/cvsroot/slashcode login
Logging in to :pserver:ano...@sl...:2401/ 
cvsroot/slashcode
CVS password:
Macintosh-2:tmp shane$ cvs -z3 -d:pserver:ano...@sl... 
:/cvsroot/slashcode co slash
Macintosh-2:tmp shane$ tail -50 /tmp/slash/sql/mysql/upgrades | grep  
cvs_tag_currentcode
UPDATE vars SET value = 'T_2_5_0_190' WHERE name =  
'cvs_tag_currentcode';
UPDATE vars SET value = 'T_2_5_0_191' WHERE name =  
'cvs_tag_currentcode';
UPDATE vars SET value = 'T_2_5_0_192' WHERE name =  
'cvs_tag_currentcode';
UPDATE vars SET value = 'T_2_5_0_193' WHERE name =  
'cvs_tag_currentcode';
UPDATE vars SET value = 'T_2_5_0_194' WHERE name =  
'cvs_tag_currentcode';


Or just goto http://slashdot.org and view the page's sourcecode.  
You'll see links w/ the tag that they are using, which is normally  
pretty close to current:

<link rel="stylesheet" type="text/css" media="screen, projection"  
href="//images.slashdot.org/core-tidied.css?T_2_5_0_194a">
Or http://use.perl.org is another site that's kept relatively close to  
current I believe.
I think the reason why you see people asking for a point-release is  
because the point-release would typically have included in it a  
scripted-method to upgrade from prior version(s). So, while people  
want the additional functionality of the current version (css, media  
in stories, audio stories, tags, firehose, discussion2, etc) they are  
not willing to go through the upgrade process as it currently is.  
Which is "follow these directions - which is basically apply these  
changes by hand in the order they are in in this file" and that's  
about it. The process does work (Lord knows I've done it enough times)  
but it's time consuming, and with a site/server that's well-modded or  
not well-kept-up it can be rather difficult to upgrade. (Though, let  
me be clear, that's _not_ any fault of the upgrade process, as it is,  
nor if it were automated).
Also, the point release would have to have some serious testing and  
what-not done to it before it could be released. This takes time, and  
manpower. It also means someone's goto to go back through the bugs  
that are on slash's sourceforge page and http://sourceforge.net/projects/slashcode/ 
  and make sure the ones that were accepted were fixed and the code's  
in, others may not have been accepted but should've, or maybe not, and  
those pesky feature requests too, should any of those try to be taken  
care of before the point release and if so who's gonna be tasked with  
each one?
All of that takes time, energy and person-power.
So who's volunteering do some of the work needed for a point release  
and what part are you going to volunteer to do? :)
  Shane