1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
|
Hi Olav<br><span id="result_box" class="" lang="en"><span class="hps">Thanks</span><span class="">, I'll talk</span> <span class="hps">to you</span> <span class="hps">when working</span> <span class="hps">in</span> <span class="hps">gnome</span> <span class="hps">packages.<br>
Send me gnome junior job anytime, I'am a mageia gnome soldier :-P<br><br>Saludos. <br><br>Bersuit<br><br><br></span></span><br><div class="gmail_quote">2013/1/15 Olav Vitters <span dir="ltr"><<a href="mailto:olav@vitters.nl" target="_blank">olav@vitters.nl</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Tue, Jan 15, 2013 at 08:33:18AM +0100, Bersuit Vera wrote:<br>
> I ask excuse, just I saw the update on<br>
> <a href="http://check.mageia.org/cauldron/updates.html" target="_blank">http://check.mageia.org/cauldron/updates.html</a>,<br>
> I trush the updates are to stable. I'am just a Padawan.<br>
<br>
</div>No problem at all, this is how anyone learns.<br>
<br>
I was hoping you wanted to become the vino or vinagre maintainer though :P<br>
<br>
FYI, almost all software on <a href="http://ftp.gnome.org" target="_blank">ftp.gnome.org</a> follows<br>
a.b.c and optionally .d<br>
<br>
where<br>
a = major<br>
b = minor (even=stable, uneven=unstable)<br>
c = micro (generally ok to update)<br>
d = pico (only used in case previous version did not build, highly<br>
recommended to update if a.b.c is still the same)<br>
<br>
so<br>
3.6.0 => 3.6.1 is just a stable update<br>
3.6.0 => 3.6.0.2 likely fixed some build issues which you might or not<br>
not have experienced on Mageia<br>
3.6.2 => 3.7.2 means the it goes from stable to unstable<br>
3.7.91 => 3.8.0 means a new stable release<br>
<br>
Note that on GNOME, the software is QA tested from git. However, the<br>
tarballs are released individually by maintainers. Then after tarball<br>
releases it is checked by the release team. Could happen that you first<br>
have 3.6.x, quickly followed by 3.6.x.1 or even a 3.6.x.2. Generally<br>
this only happens for the first few micro releases in a new development<br>
cycle (e.g. 3.7.0 to 3.7.4).<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Regards,<br>
Olav<br>
</font></span></blockquote></div><br>
|
