Release tag & "Re: HEADS UP! Upcoming work in HEAD and other events!"

Raphael Marmier raphael at
Tue Apr 26 09:42:20 PDT 2005

Appart from security/important fixes, nothing will ever go to RELEASE.

The work done in HEAD will go to PREVIEW, then with time will become a 
_NEW_ release.

Each release has its own branch of code in cvs.


Jurij Kovacic wrote:

It is my understanding that work currently being done in HEAD will 
eventually be commited to the RELEASE tag.

Since we are tracking DragonFly RELEASE on one of our production servers 
I am concerned that at some time in the future I would need to recompile 
all the installed ports after a system upgrade - is this really the 
case? And if so, when can we expect this?

Even though I KNOW this probably is a BAD idea - would a sym-link ->

fix the problem? This temporary measure would give us enough time to 
rebuild the ports in all jails as we cannot afford any downtime.

Keep up the bood work!

Jurij Kovacic

Matthew Dillon wrote:

:On Wed, Apr 20, 2005 at 11:12:09AM -0700, Matthew Dillon wrote:
:Will DragonFly_Stable stay in sync with DragonFly_Preview, or is it
:going to be removed sometime later?
    It will be removed sometime later.  At the moment it *is* in sync.

:>     Joerg is going to start bringing in the citrus framework and 
:>     on libc revision bump issues.  LIBC MAY BREAK!  LIBC MAY BREAK 
:>     TIMES OVER THE NEXT FEW WEEKS, IN FACT!  There could also be 
:>     buildworld/installworld issues and other things.
:I noticed that you need to rebuild perl port(if you have that) after
:the citrus import, otherwise it complains failing to set the locale.
        It's likely that just about everything would need to be rebuilt,
    including ports.   Multiple times.   Everyone should be aware that
    the work on HEAD is creating a moving target for libc and system

                    Matthew Dillon                     
<dillon at xxxxxxxxxxxxx>

More information about the Users mailing list