Re: git BoF
On Sat, Jun 25, 2011 at 11:35, Raphael Kubo da Costa wrote: > On Thursday 23 June 2011 14:13:01 Ian Monroe wrote: > > I'm thinking we should have a KDE Git transition BoF. One thought is that > > the Git BoF happen after the release team BoF so that they can be given > the > > opportunity to add stuff to our agenda. > > Do you have anything in mind for this BoF which wouldn't fit in the > release- > team BoF itself? > Yea, a lot of git techie talk. Ian ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: [Kde-scm-interest] Re: git BoF
On Saturday, June 25, 2011 21:40:31 Ingo Klöcker wrote: > On Saturday 25 June 2011, Raphael Kubo da Costa wrote: > > On Thursday 23 June 2011 14:13:01 Ian Monroe wrote: > > > I'm thinking we should have a KDE Git transition BoF. One thought > > > is that the Git BoF happen after the release team BoF so that they > > > can be given the opportunity to add stuff to our agenda. > > > > Do you have anything in mind for this BoF which wouldn't fit in the > > release- team BoF itself? > > I think the audience for both BoFs is very different. The Git transition > BoF appears to address projects which did not yet do the transition to > Git while the release team BoF appears to address people interested in > doing release work. (Or maybe I'm reading too much from the BoFs' > titles.) I quite agree with Ingo, and I think we need to think about our release management in a focused way, not mix it with issues around the Git migration. As I see it, Git or not should be completely transparant for how our releases look like. Cheers, -- sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9 ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
Re: [Kde-scm-interest] Re: git BoF
On Saturday 25 June 2011, Raphael Kubo da Costa wrote: > On Thursday 23 June 2011 14:13:01 Ian Monroe wrote: > > I'm thinking we should have a KDE Git transition BoF. One thought > > is that the Git BoF happen after the release team BoF so that they > > can be given the opportunity to add stuff to our agenda. > > Do you have anything in mind for this BoF which wouldn't fit in the > release- team BoF itself? I think the audience for both BoFs is very different. The Git transition BoF appears to address projects which did not yet do the transition to Git while the release team BoF appears to address people interested in doing release work. (Or maybe I'm reading too much from the BoFs' titles.) Regards, Ingo signature.asc Description: This is a digitally signed message part. ___ release-team mailing list release-team@kde.org https://mail.kde.org/mailman/listinfo/release-team
