[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-edu
Subject:    Re: [kde-edu]: 4.7 branch in kde edu projects
From:       "Anne-Marie Mahfouf" <annemarie.mahfouf () free ! fr>
Date:       2011-05-24 19:06:09
Message-ID: 201105242106.09683.annemarie.mahfouf () free ! fr
[Download RAW message or body]

On Monday 23 May 2011 02:53:04 Tomaz Canabrava wrote:
> God question,
> I'm using a 4.8 branch that will become master on rocs, but local,
> don't know if I can push up right now, actually.
> 
> Tomaz

Hi Tomaz,

No please do not push right now as master is 4.7 and will stay as such until 
the RC1 if I understand correctly.
If some people were to create 4.7 branches in the repo, the release manager 
would not be able to package the next betas, they will be packaged from 
master.
Either keep your local branchuntil the RC1 or create a feature branch that 
you'll merge after master becomes 4.8.

Additionally, is the GHNS script fixed so I could do a nice screenshot for Rocs 
for the website?

Best regards,

Anne-Marie

> On Sun, May 22, 2011 at 6:24 PM, Aleix Pol <aleixpol@kde.org> wrote:
> > Hi!
> > I was wondering about how we're going to proceed to properly maintain
> > consistency across kde edu (and KDE in general too, I guess) when it
> > comes to creating and naming the KDE 4.7 branch.
> > 
> > What's the usual thing to do here? Should I create my 4.7 branch myself,
> > right now?
> > 
> > Aleix
> > _______________________________________________
> > kde-edu mailing list
> > kde-edu@mail.kde.org
> > https://mail.kde.org/mailman/listinfo/kde-edu
> 
> _______________________________________________
> kde-edu mailing list
> kde-edu@mail.kde.org
> https://mail.kde.org/mailman/listinfo/kde-edu
_______________________________________________
kde-edu mailing list
kde-edu@mail.kde.org
https://mail.kde.org/mailman/listinfo/kde-edu
[prev in list] [next in list] [prev in thread] [next in thread]