Re: package naming and release numbering

[Kai.Grossjohann@CS.Uni-Dortmund.DE (K. )]

Tom Roche <Tom...@nc...> writes:

> Kai.Grossjohann@CS.Uni-Dortmund.DE Fri, 28 Sep 2001 14:04:28 +0200
> 
>> What happens if the two versions are not in sync and a bad problem
>> is reported? Then the fix needs to be applied to both versions,
>> which is more work than just applying it to one version.
> 
> Umm ... it's hard for me to say, without actually having exercised
> SF's packaging functionality, but I suspect this wouldn't actually be
> a problem:
> 
> * I would hope that there would be some "proof period" for the stable
>   code. I.e. the rule should be that nothing goes into a stable
>   package that's less than n days old. (Any candidates for n? Just
>   offhand I'd say n = 14.) 
> 
> * SF packages are essentially just tar- or zipballs (see 
> 
> https://sourceforge.net/docman/display_doc.php?docid=6445&group_id=1
> 
>   ) so releasing a package involves essentially just snapshotting
>   (identifying versions of files suitable for the package) and
>   twiddling.
> 
>   In case of the "worst-case scenario" above, just rollback to
>   pre-bad-problem versions. This can be done outside of CVS:

So your suggestion is to proceed as follows:

When we think that it's a good time, we make a snapshot from CVS and
call it a tentative release.  Then people try that for a while, and if
they find it works, we call it a real release.

Yeah, that would be easy, and we could add tags to CVS to keep track
of what has been released.  And stuff.

Good idea!

> 
>> So, the status of tramp2*.el is unclear.  Maybe Daniel wants to chime
>> in here?
> 
> Indeed: is he on the new list?

Yep.

> Perhaps tramp2 would make a good subproject for SF's Task Manager? See
> 
> http://sourceforge.net/pm/?group_id=34545

This gives me an empty list of subprojects.  I skimmed the list of
documentation but didn't find anything which looked promising to
explain what is a subproject.

What is it?

kai
-- 
Abort this operation?   [OK]  [Cancel]