diff options
Diffstat (limited to 'zarb-ml/mageia-dev/attachments/20101007/138c9beb/attachment.html')
| -rw-r--r-- | zarb-ml/mageia-dev/attachments/20101007/138c9beb/attachment.html | 24 |
1 files changed, 24 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/attachments/20101007/138c9beb/attachment.html b/zarb-ml/mageia-dev/attachments/20101007/138c9beb/attachment.html new file mode 100644 index 000000000..325123a62 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20101007/138c9beb/attachment.html @@ -0,0 +1,24 @@ +<br><br><div class="gmail_quote">2010/10/6 Olivier Thauvin <span dir="ltr"><<a href="mailto:nanardon@nanardon.zarb.org">nanardon@nanardon.zarb.org</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> +<div class="im">* Buchan Milne (<a href="mailto:bgmilne@multilinks.com">bgmilne@multilinks.com</a>) wrote:<br> +</div><div class="im">> On Tuesday, 5 October 2010 23:39:09 Tux99 wrote:<br> +> > On Wed, 6 Oct 2010, nicolas vigier wrote:<br> +><br> +</div><div class="im">> > 3) I mentioned earlier that the packager would need to use good<br> +> > judgement and not include major incompatible version changes<br> +><br> +> You are aware that this is significantly more work than 'mdvsys submit -t<br> +> 2010.1 --define section=main/backports $package' (after some minimal testing of<br> +> course)?<br> +<br> +</div>This part of the discuss let me think something.<br> +<br> +We have both some people wanting huge set of backport and other wanting<br> +long life release w/o change except security/bug fix.<br> +<br> +So, why not alternate both, 1 release with backports denied but long<br> +life, and the 2nd with backports and update but during a shorter period.<br> +(X.0 would be the new distro with backports, X.1 the one more servers<br> +oriented or enterprise).<br> +<br> +What do you think ?<br> +<font color="#888888"></font><br></blockquote><div><font color="#888888"><br>i am not pro this, i think this is better to have the same policy for all the releases.</font> </div></div> |