As a user, who is familiar with both CE/YE editions, the release numbers
suggested below allows me to easily know when there is little
difference, or when there are big changes coming where I have to make
sure I'm getting the "right" version.
For example, with:
Quagga-CE-1.1-0.1
Quagga-YE-1.1
I might say, the CE version seems to be a little a head of the YE
version, maybe a few little features with bugs fixes, I'll take it. But:
Quagga-CE-1.1-1.6
Quagga-YE-1.1
I might say, too much change for me for now, I will just use the YE for
now. I don't need to look elsewhere, the numbers told me everything I
need to know.
--Jafar
On 6/2/2016 4:16 PM, Jafar Al-Gharaibeh wrote:
On 6/2/2016 11:43 AM, Donald Sharp wrote:
How do the releases relate to each other? Not sure if it is a
problem. Keep numbering disconnected since we don't currently have
CE and YE connected?
This boils down to the question of how much different YE from CE is.
Different numbering schemes will give the impression that we have
completely different versions of Quagga. That is going to be
confusing. I don't think that is the case, and I don't think that is
the direction we want to take. This is the reason I suggested the
comment (CE is a superset of YE...) in the document. The vast majority
of patches (if not all) should make their way into both releases. With
CE having a shorter release cycle, such updates will show up there
first typically. We shouldn't allow code/features divergence to keep
things simple for both maintainers and users. Some
new/adventurous/controversial features that only get a simple majority
vote are good examples of features that will be in CE but not in YE
for an "extended" period of time. They either stay there until they
are deemed to be worthy of inclusion of YE, or continued to be
experimental for more time. In some cases we might even get to the
point where a feature should be dropped altogether if it proves to be
problematic or un-useful.
The point is: we shouldn't allow bug fixes, "small" patches, or any
agreed upon (super majority) patches to make it to CE and slip away
cycle after cycle without including them in YE. YE should be brought
up to speed with CE every YE release. Some new features might be
carried over a few cycles before they get included in YE but that
doesn't mean CE and YE should have release numbers completely
independent of each other. They should have something in common. Here
is one idea I have regarding numbering releases:
Quagga-CE-Major.Minor-CEMajor.CEMinor
Quagga-YE-Major.Minor
Identical releases:
Quagga-CE-1.0-0.0
Quagga-YE-1.0
Add minor feature X to CE
Quagga-CE-1.0-0.1
Quagga-YE-1.0
Add minor feature Y to CE
Quagga-CE-1.0-0.2
Quagga-YE-1.0
Move feature Y to YE
Quagga-CE-1.1-0.1
Quagga-YE-1.1
As you can see, CE major and CE minor moves on their own. But whenever
a patch is integrated with YE, the associated numbers are carried over
to the main Major/Minor numbers.
Cheers,
Jafar
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev
