On 03 Jul 2001 10:16:20 +0200, Dominik Vogt wrote:
>
> On Tue, Jul 03, 2001 at 07:59:02AM +0000, Mikhael Goikhman wrote:
> > On 03 Jul 2001 09:16:43 +0200, Dominik Vogt wrote:
> > >
> > > On Tue, Jul 03, 2001 at 12:03:14AM -0500, Jason L Tibbitts III wrote:
> > > > >>>>> "MG" == Mikhael Goikhman <[EMAIL PROTECTED]> writes:
> > > >
> > > > MG> Jason please move fvwm-2.4.0-pre3.tar.{gz,bz2} to the testing
> > > > MG> directory.
> > > >
> > > > It's there.
> > > >
> > > > MG> In any case, the instructions posted by Dominik are valid with one
> > > > MG> minor correction. The release time is immediately after July, 03
> > > > 20:00
> > > > MG> GMT.
> > > >
> > > > It's nearly 2001.07.03 05:00 UTC now, which means I'll do the release at
> > > > 15:00 CDT (my local time). Unless UTC and GMT aren't currently
> > > > coincident. (This stuff makes my brain hurt.)
> > > >
> > > > I will mail out the announcement (docs/ANNOUNCE) at that time,
> > >
> > > ... or unless the package is screwed up - which is the case. It
> > > bears the release number 2.4.0.1 since I already changed the
> > > ChangeLog, configure.in and NEWS.
> >
> > Did you download 2.4.0-pre3? :)
> >
> > It has no 2.4.0.1 anywhere, because as I said I did it from
> > "cvs update -r version-2_4_0". The files that you mention have version
> > after symbolic version-2_4_0, so this is not included in the package.
> >
> > > Also, the fvwm-web patch does
> > > not have the correct date anymore. Forthermore, the dates in the
> > > module man pages do not match the intended release date anymore.
> > > I have to redo everything from scratch (*groan*). Can somebody
> > > tell me the cvs command to move the 2.4.0 tag to the current file
> > > versions?
> >
> > % cvs tag -F version-2_4_0 [files]
> >
> > I think that pre3 is just good to be a release. Trust me. But if you want
> > to have an additional headache, which I really wanted not to cut from you,
> > you may decide differently. :)
>
> I'd really prefer if you didn't take that this lightly. It's no
> fun to double and triple check each step I make and I don't think
> it's a good idea to change the set of distributed files 6 hours
> before the release (see "todo-2.4" and "todo-3.0").
The list of distributed files is defined in Makefile.am, I didn't change
it. This change didn't actually add todo-2.4 and todo-3.0 to rpm
because they are not distributed with dist, it was harmless.
> > Web patch may be redone. It is ok by me that the date is July 1, since we
> > didn't have a single code change since then, so pre-2 is not different.
> >
> > As I wrote this, I got an email about pre4. But the tag is not moved,
> > so "cvs update -r version-2_4_0" is still pre3. So either pre4 is not
> > synchronized with cvs tag version-2_4_0 or pre4 is the same as pre3.
>
> The tag has been move for all files that were changed.
Ok, I see that you tagged a new tag "version_2_4_0"; tag "version-2_4_0"
is not moved.
Here is that may be done to synchronize these tags:
% cvs tag -r version_2_4_0 -F version-2_4_0
Regards,
Mikhael.
--
Visit the official FVWM web page at <URL:http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm-workers" in the
body of a message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]
