Tim Kelly <hockey@dialectronics.com> writes:

> I read the above to say that 2.0 is a subset of -current; there are
> things in -current that are in 2.0, but all of 2.0 is in -current. Is
> this correct?

2.0 branched off from -current many months ago, but items from
-current were actively moved back into 2.0, on request. The time for
requesting such pullups has pretty much passed. One might say that
"everything in 2.0 was in -current at some point, but might have been
removed or replaced since then".

> What nomenclature is used to denote port specific bug fixes and
> releases?

There are no port-specific releases.

> Is there a set time frame on when those bug fixes will have a
> specific (tag), such as once a month?

There are no set time frames, either. The major releases (2.0) and
point releases (2.1) have rough schedules set when the branch is cut,
but they're pretty rough, and other branches aren't really planned in
advance.

> What about a -bugs branch, which
> contains bug fixes for the last tagged release, but doesn't have
> everything from -current in it?

That will be the 2.0 branch, between 2.0 and 2.1.

The thing to do, now, is to fix things and then make sure they get
into 2.1. 

        - Nathan