From: Markos Chandras <hwoarang@gentoo.org>
To: "Tomáš Chvátal" <scarabeus@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in app-office/libreoffice: ChangeLog libreoffice-3.4.99.1.ebuild libreoffice-3.5.0.0.ebuild
Date: Sat, 17 Dec 2011 09:56:01 +0000 [thread overview]
Message-ID: <4EEC6731.30107@gentoo.org> (raw)
In-Reply-To: <CA+NrkpcuKrmKV3ySvc3_TwWVvD6Y6D78O1K6hBXCcx65s1SVTw@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 12/17/2011 09:34 AM, Tomáš Chvátal wrote:
> 2011/12/16 Markos Chandras <hwoarang@gentoo.org>:
>> On 12/12/2011 05:44 PM, Tomas Chvatal (scarabeus) wrote:
>>> scarabeus 11/12/12 17:44:48
>>>
>>> Modified: ChangeLog Added:
>>> libreoffice-3.4.99.1.ebuild Removed: libreoffice-3.5.0.0.ebuild
>>> Log: Remove miss-named beta0. Add beta1 with better name
>>> (presented as downgrade).
>>>
>>> (Portage version: 2.2.0_alpha80/cvs/Linux x86_64, RepoMan
>>> options: --force)
>>>
>>> Revision Changes Path 1.216
>>> app-office/libreoffice/ChangeLog
>>>
>> I know it is a bit late but do you think that commit made sense
>> at that time? It is not the best user experience we can provide
>> when beta releases appear as downgrades. FWIW beta releases
>> should remain masked to avoid useless compilations to slow
>> machines instead of digging through Changelogs to see what
>> happened. Are the beta releases of libreoffice so critical that
>> force you to keep them in the ~testing tree?
>>
> They should be stable enough plus it helps a lot to catch all the
> bugs. Most of those Gentooers reported are being fixed and I think
> it is better to test it during the beta cycle rather than start
> messing with it after final release.
>
> So if you don't want those ebuild in main tree just tell me so and
> I can add only the releases (but then I won't care about the bugs
> much as I do this fixes as part of the upstream QA and don't use
> Gentoo [no worries I compile/runtime test it in the dev tinderbox
> that has gentoo], so at the point of release I should be focusing
> on master branch again).
>
> Tom
>
You misunderstood me. I don't object to beta ebuilds but I wonder if
testing users want to have them by default. Maybe they should be
masked by default and whoever wants the shiny stuff can always unmask
them. Anyway not a big deal. I guess I belong to the minority of
people who do own a single core PC in 2011 :)
- --
Regards,
Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (GNU/Linux)
iQIcBAEBCgAGBQJO7GcxAAoJEPqDWhW0r/LCd3oQAMR8gUxPPu+tnPWkOmU5ZedK
B7aCy09P2ecV/BvxDBf1wQOWDb19tpfXT15Rm486+pxkDovP0lhr8hbNklfHXbjE
fB+2JYvEb5qf/zNePCNRc6LC/KaDurIx+z4RzFBOquoZbJM5Z6c8ya+w2q98YmtD
DsB5y1jpq5Fs2eVNjDvmuzDjR0MoMPP1oE9Y0kU4D5ahpH03IdPbyCv/AjR/M3lb
MRezGuRI7EQmrnBNdqZIJpUPHaCioxsyvIeVpw9gkprdQPC4olX8ASd90En41kA6
pnxK1+u1WYJKWJyCZrGROIlws8dBa/mKHn+E+SU10j4kLGIi6dYQGOghPC8g+yop
3E4kgDlJZnXTIpnCszrdkgoqWlDNzmToV6c0D6hvc9itG2aE8vwiSKXHQMp1Lxf7
RGF1/gxyojB9ExUhCwWK7jFBPqhrYb88CpU5fvLRGR8VQ5zq1pM3F5yNoPg4qYdD
U7tUdwm6UPNc9p3QfLSW93FSV4MAEzXhOuj0Kmt9AMr0n+boKyzycm44wm1R31NM
hXoX7bhxP4r2UPRXUJBO+3FGdcxrH4YkcZ3A5yXEV/LwkgtSKsJRzyA5/VQFZCkw
Tt5wvXqRrjW51fVfeY3SU8q/Y0W1pu46Dd1C3Vc3jR1xW8uUegVVJNizmOdOC70y
O7p/tIdyadV9aOjsSKUs
=oIMb
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2011-12-17 9:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20111212174448.F09FC2004B@flycatcher.gentoo.org>
2011-12-16 20:33 ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in app-office/libreoffice: ChangeLog libreoffice-3.4.99.1.ebuild libreoffice-3.5.0.0.ebuild Markos Chandras
2011-12-17 8:32 ` Ciaran McCreesh
2011-12-17 10:47 ` Markos Chandras
2011-12-17 12:02 ` Ciaran McCreesh
2011-12-17 16:58 ` Zac Medico
[not found] ` <CA+NrkpcuKrmKV3ySvc3_TwWVvD6Y6D78O1K6hBXCcx65s1SVTw@mail.gmail.com>
2011-12-17 9:56 ` Markos Chandras [this message]
2011-12-17 10:27 ` Pacho Ramos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EEC6731.30107@gentoo.org \
--to=hwoarang@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=scarabeus@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox