On 14 April 2012 10:30, Boudewijn Rempt wrote:
> On Saturday 14 April 2012 Apr, Cyrille Berger Skott wrote:
>
>
>
>> Personnaly, that is how I work with most non-kde projects. But I am unsure
>
>> about enforcing that, unless bugs.kde.org user experience has improved
>
>> drastically.
>
>
>
> Bugz
On Saturday 14 April 2012 Apr, Cyrille Berger Skott wrote:
> Personnaly, that is how I work with most non-kde projects. But I am unsure
> about enforcing that, unless bugs.kde.org user experience has improved
> drastically.
Bugzilla looks nicer... In a low-contrast, stylish but harder to read w
On Saturday 14 April 2012 Apr, C. Boemann wrote:
> On Saturday 14 April 2012 08:37:25 Cyrille Berger Skott wrote:
> > On Thursday 12 Apr 2012, Jaroslaw Staniek wrote:
> > > Isn't that used as: FEATURE: ?
> >
> > I had forgotten about that. What about either:
> >
> > FEATURE/BUG:
> > DESCRIPTION
On Saturday 14 April 2012 08:37:25 Cyrille Berger Skott wrote:
> On Thursday 12 Apr 2012, Jaroslaw Staniek wrote:
> > Isn't that used as: FEATURE: ?
>
> I had forgotten about that. What about either:
>
> FEATURE/BUG:
> DESCRIPTION: optional description that overide the title from bug (usefull
>
On Thursday 12 Apr 2012, Jaroslaw Staniek wrote:
> Isn't that used as: FEATURE: ?
I had forgotten about that. What about either:
FEATURE/BUG:
DESCRIPTION: optional description that overide the title from bug (usefull
when bug report have bad titles like "crash in APPNAME"
Or:
FEATURE/BUG: de
On Thursday, April 12, 2012 14:50:03 Cyrille Berger wrote:
> I have started to put together a draft of a commit policy:
>
> http://community.kde.org/Calligra/Policies/Commits
>
> For now, it is essentially what I said in my emails.
>
> For the git bisect part, maybe we could have some guideline
On 12 April 2012 22:25, Jaroslaw Staniek wrote:
> BTW, is there somewhere documented recommended post-review script and
> recipe specific for calligra development?
>
> I have this:
Updated (don't read if you have your own solution ready):
#!/bin/bash
# post-review-master
# git remote add calligr
BTW, is there somewhere documented recommended post-review script and
recipe specific for calligra development?
I have this:
#!/bin/bash
# first run: git remote add calligra git://anongit.kde.org/calligra
if [ -z "$1" ] ; then echo "enter testing-done"; exit 1; fi
if [ -z "$2" ] ; then echo "ent
On Thursday 12 April 2012 Apr, Friedrich W. H. Kossebau wrote:
> Am Donnerstag, 12. April 2012, 15:03:43 schrieb Jaroslaw Staniek:
> > On 12 April 2012 14:50, Cyrille Berger wrote:
> > > I have started to put together a draft of a commit policy:
> > >
> > > http://community.kde.org/Calligra/Polic
Am Donnerstag, 12. April 2012, 15:03:43 schrieb Jaroslaw Staniek:
> On 12 April 2012 14:50, Cyrille Berger wrote:
> > I have started to put together a draft of a commit policy:
> >
> > http://community.kde.org/Calligra/Policies/Commits
> >
> > For now, it is essentially what I said in my emails.
On 12 April 2012 14:50, Cyrille Berger wrote:
> I have started to put together a draft of a commit policy:
>
> http://community.kde.org/Calligra/Policies/Commits
>
> For now, it is essentially what I said in my emails.
>
> For the git bisect part, maybe we could have some guideline on what to
> co
I have started to put together a draft of a commit policy:
http://community.kde.org/Calligra/Policies/Commits
For now, it is essentially what I said in my emails.
For the git bisect part, maybe we could have some guideline on what to
commit in branch,
could be useful for beginners as well.
As f
On Thursday, April 12, 2012 08:54:22 Boudewijn Rempt wrote:
> On Wednesday 11 April 2012 Apr, Cyrille Berger Skott wrote:
> > Hi,
> >
> > For me this is how it should be: commits in master are restricted to:
> >
> > * single commit bug fixes
> > * merge from feature branches (or single commit fea
On Wednesday 11 April 2012 Apr, Cyrille Berger Skott wrote:
> Hi,
>
> For me this is how it should be: commits in master are restricted to:
>
> * single commit bug fixes
> * merge from feature branches (or single commit feature, note that I
> personnaly don't encourage this practise)
Same here
On Tuesday 10 Apr 2012, Jaroslaw Staniek wrote:
> There are implications of such short release cycle however. I'd like
> to focus on just one today. Work on two or more versions can happen
> concurrently so it's important to have features easily moveable
> between releases since we're going to chan
Hi,
For me this is how it should be: commits in master are restricted to:
* single commit bug fixes
* merge from feature branches (or single commit feature, note that I
personnaly don't encourage this practise)
Then the amount of reviewing for commits or merge is left at the discretion of
the
On 6 April 2012 00:44, C. Boemann wrote:
> In Berlin last year we agreed that we would move to a 4 month release cycle
> and in order to do that we promised ourselves we would keep master in a
> releasable state only merging things when it was ready to be released.
>
> I don't think we have taken
On Saturday 07 April 2012 10:54:05 Boudewijn Rempt wrote:
> On Friday 06 April 2012 Apr, C. Boemann wrote:
> > Hi
> >
> > In Berlin last year we agreed that we would move to a 4 month release
> > cycle and in order to do that we promised ourselves we would keep master
> > in a releasable state onl
On Friday 06 April 2012 Apr, C. Boemann wrote:
> Hi
>
> In Berlin last year we agreed that we would move to a 4 month release cycle
> and in order to do that we promised ourselves we would keep master in a
> releasable state only merging things when it was ready to be released.
>
> I don't thin
Fredag den 6. april 2012 00:44:34 C. Boemann skrev:
> Hi
>
> In Berlin last year we agreed that we would move to a 4 month release cycle
> and in order to do that we promised ourselves we would keep master in a
> releasable state only merging things when it was ready to be released.
>
> I don't t
Hi
In Berlin last year we agreed that we would move to a 4 month release cycle
and in order to do that we promised ourselves we would keep master in a
releasable state only merging things when it was ready to be released.
I don't think we have taken that to heart yet. Master is currently broken
21 matches
Mail list logo
