Moving of 3.4 into KDE/3.5/

Hi,

so before everybody forgets about this: We all agreed that
we want to
move 3.4 into KDE/3.5 before the 3.4.1 release so we get
translations
this time. Along the way I guess we should move 3.3 into
branches/kdevelop for people that are stuck on KDE <
3.4.

What was left to do before moving is that we should ask on
kde-i18n
wether its ok for them, primarly because it will make many
strings fuzzy
and introduce quite some new ones. Matt I guess you're
already
subscribed to kde-i18n so, could you do that in the next few
days?

We still have the (relatively large) svn patch from dukju
that we need
to review and decide wether we integrate it (but I guess the
answer to
that will be yes, unless it breaks anything). I'm also not
sure if
Jens, Kris or David have anything hidden on their hdd which
should go
into 3.4.1. I don't have any plans for new features myself,
so I think
feature-wise we're ready for the next release, so all we
need to "fix"
is the translations before releasing.

Andreas

-- 
You have had a long-term stimulation relative to business.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

Please before moving KDevelop/3.4 into KDE/3.5/kdevelop:

- Move KDE/3.5/kdevelop r623698 into kdevelop/3.3 (KDevelop
3.3.6)
- Reapply r630868 to kdevelop/3.3

I'm not a SVN guru :(
-- 
Amilcar Lucas
KDevelop.org webmaster

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On 16.03.07 00:59:49, Amilcar do Carmo Lucas wrote:
> Please before moving KDevelop/3.4 into
KDE/3.5/kdevelop:
> 
> - Move KDE/3.5/kdevelop r623698 into kdevelop/3.3
(KDevelop 3.3.6)
> - Reapply r630868 to kdevelop/3.3

Uhm, and why shouldn't we move KDE/3.5/kdevelop into
kdevelop/3.3? Right
before moving 3.4 into KDE/3.5.

Andreas

-- 
Perfect day for scrubbing the floor and other exciting
things.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On Friday 16 March 2007 02:21, Andreas Pakulat wrote:
> Uhm, and why shouldn't we move KDE/3.5/kdevelop into
kdevelop/3.3? Right
> before moving 3.4 into KDE/3.5.

We can do either smth like:
svn cp $kde_svn/branches/KDE/3.5/kdevelop
$kde_svn/branches/kdevelop/3.3
svn co $kde_svn/branches/KDE/3.5/kdevelop $kdev_src
svn merge -r 472524:HEAD $kde_svn/branches/kdevelop/3.4
$kdev_src
svn commit

or like Andreas suggested
svn mv $kde_svn/branches/KDE/3.5/kdevelop
$kde_svn/branches/kdevelop/3.3
svn mv $kde_svn/branches/kdevelop/3.4
$kde_svn/branches/KDE/3.5/kdevelop

I don't know which is better honestly.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On Mar 16, 2007, at 10:47 AM, Kris Wong wrote:

>> I'm also not sure if Jens, Kris or David have
anything
>> hidden on their hdd which should go into 3.4.1.
>
> I do (see attached patch if you are curious).  I
believe it is  
> ready to
> be committed at this point, but I am awaiting approval
from David  
> first.
> I don't know if or how that would affect the move.
>
> Kris Wong
> <switch_header_impl.patch>
>

What does your patch do?
--
Matt



_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

> What does your patch do?

It is an update to a previous patch I submitted that allows
the switch
header/implementation code to find matching
definitions/declarations in
files that have different names (i.e.,
myheader.h/somesource.cpp).  The
current implementation iterates through the project files in
the code
model rather than searching from the global namespace node,
as was
suggested by David.  This patch corrects this implementation
and is both
more correct and more efficient.  It also handles some
scenarios that
the current implementation does not, such as:

multiple matching symbols in the same project (think
Driver:river
in
languages/java/ and lib/cppparser)
using statements (to import namespaces)

Kris Wong

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

Just in case anyone concerned with this isn't aware, I heard
back from
David and have committed my changes.  That's it from me on
the 3.4
front.

Kris Wong

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

Am Donnerstag, 15. März 2007 22:42 schrieb Andreas Pakulat:
> Hi,
> I'm also not sure if
> Jens, Kris or David have anything hidden on their hdd
which should go
> into 3.4.1.

Nothing hidden on my disk. 

Kris Wong's new switch-header patch should be tested a
little for regressions 
before releasing 3.4.1.

greetings, David

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

Am Samstag, 17. März 2007 00:49:45 schrieb David Nolden:
> Am Donnerstag, 15. März 2007 22:42 schrieb Andreas
Pakulat:
> > Jens, Kris or David have anything hidden on their
hdd which should go
> > into 3.4.1.

Now, after a few fixes, I think that at least the
code-completion is ready for 
3.4.1. 

greetings, David

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel