On Monday 15 Jul 2013 09:46:49 Aaron J. Seigo wrote:
> On Friday, July 12, 2013 17:48:50 David Jarvie wrote:
> > best of intentions) for old habits to take over and to accidentally use
> > master again. This happened to me more than once.
>
> So how can we make that clearer for people and hard fo
On Freitag, 12. Juli 2013 17:47:53 CEST, Aaron J. Seigo wrote:
On Wednesday, July 10, 2013 22:39:29 Thomas Lübking wrote:
There'll have to be (minor) patches to kde-workspace (you cannot keep
shipping known and fixable crashes), thus new tarballs and
shipping kdelibs
4.13.2, workspace 4.11.12
Aaron J. Seigo wrote:
> "we should try to recruit more people from the user community of
> downstream distributions who have the skills necessary to merge patches
> and test. some distributions do this already.”
The reason I mentioned "issues" with this approach originally originate from
(perha
On Monday, July 15, 2013 02:48:01 PM Albert Astals Cid wrote:
> El Diumenge, 14 de juliol de 2013, a les 04:19:52, Inge Wallin va escriure:
> > I think keeping 6 months is a good
> > figure to ensure both reasonable turn-around *and* actual bugfixes of
> > versions being used in the real world.
>
El Dilluns, 15 de juliol de 2013, a les 09:58:01, Cristian Tibirna va
escriure:
> Although Inge supposedly bases his analysis on extrapolation and (very) wise
> guessing, and despite the obvious lack of hard data (1), I will put my
> support behind Inge's view.
>
> (1) (sadly including here our b
On Mon, July 15, 2013 10:46:49 Aaron J. Seigo wrote:
> On Friday, July 12, 2013 17:48:50 David Jarvie wrote:
> > best of intentions) for old habits to take over and to accidentally use
> > master again. This happened to me more than once.
>
> So how can we make that clearer for people and hard fo
On Mon, July 15, 2013 12:27:53 Aaron J. Seigo wrote:
> On Saturday, July 13, 2013 23:36:24 David Faure wrote:
> > * let master be the branch that will become 4.12, even if you (= the
> > workspace developers) don't intend to do more than bugfixing on 4.x, there
> > will always be a need to separate
Although Inge supposedly bases his analysis on extrapolation and (very) wise
guessing, and despite the obvious lack of hard data (1), I will put my support
behind Inge's view.
(1) (sadly including here our blatant dissing of, e.g., 527 severe bug reports
on nepomuk... that ask for stability an
El Diumenge, 14 de juliol de 2013, a les 04:19:52, Inge Wallin va escriure:
> I think keeping 6 months is a good
> figure to ensure both reasonable turn-around *and* actual bugfixes of
> versions being used in the real world.
It may be a reasonable turn-around for some users, but it is also not
d
Hey,
On Tuesday, July 09, 2013 18:57:41 Albert Astals Cid wrote:
> So the kde-workspace dudes decided they don't want a 4.12 release and that
> they'll do a LTS 4.11, fine, how do we fix that branch wise?
After carefully reading everybody's opinion, I would like to make kde-
workspace master our
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/111480/#review35959
---
Ship it!
i think that technically this is a bug in the applica
On Saturday, July 13, 2013 23:36:24 David Faure wrote:
> I feel strongly about what kde-workspace should do in the current situation,
> actually, after having gone through multiple solutions with kdelibs:
Welcome to my world.
I feel strongly about what kdelibs should have done. I am not the maint
On Sunday, July 14, 2013 04:19:52 Inge Wallin wrote:
> Without having any scientific proof, I believe that there are 2 main
> categories of users:
> 1. Those generally satisfied who want stability
> 2. Those who long for new updates all the time.
Regardless of whether someone is a Category 1 or
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/111480/
---
(Updated July 15, 2013, 9:18 a.m.)
Review request for kde-workspace and Ma
On Saturday, July 13, 2013 09:50:21 Luca Beltrame wrote:
> Aaron J. Seigo wrote:
> > 1. packagers seem to feel that if upstream doesn’t do the actual commit to
> > the upstream repository, then upstream is not maintaining their software
>
> To be honest, that's not always true.
Good :)
> At leas
On 2013-07-14, Inge Wallin wrote:
> Here are some assumptions. Correct me if they are wrong:
> - KDE developers support the last relesed and *maybe* the second to last
> release with bugfixes.
> - Distributions have a release cycle of 6 months or longer.
> - Distributions pick their contents 2
On Saturday, July 13, 2013 14:05:13 Jaime Torres Amate wrote:
> How would the release schedule (
> http://techbase.kde.org/Schedules/KDE4/4.11_Release_Schedule) be in a 3 or
> 4 mounths release? 1 month for new features, 2 or 3 for bugfixing,
> translating, language bindings? Or like linux kernel,
On Friday, July 12, 2013 17:48:50 David Jarvie wrote:
> On Fri, July 12, 2013 4:42 pm, Aaron J. Seigo wrote:
> > * there were 2 main reasons the branched-kdelibs shifted back to master-
> >
> > kdelibis:
> > * people were too stubborn and too (willfully) uninformed to understand
> >
> > why t
On Sunday, July 14, 2013 15:23:46 David Faure wrote:
> On Friday 12 July 2013 17:07:13 Aaron J. Seigo wrote:
> > we ought to think of ways to make master more stable.
>
> Exactly. And porting master to qt5/frameworks definitely doesn't make it
> more stable, so let's not do that.
>
> (Yes, I'm m
On 07/13/2013 10:19 PM, Inge Wallin wrote:
Without having any scientific proof, I believe that there are 2 main categories
of users:
1. Those generally satisfied who want stability
2. Those who long for new updates all the time.
My feeling is that the first category is the silent majority an
20 matches
Mail list logo
