Re: Project future.

----- Messaggio originale -----

> Da: Mauro C. <[email protected]>
> A: [email protected]
> Inviato: Mercoled=EC 3 dicembre 2008, 0:26:27
> Oggetto: [PHPEclipse-devel] Project future.
> =

> 1) Decide how to use subversion, work always on trunk or create branch fo=
r major =

> release.

Atm this problem: backward compatibility to 3.2.x due to GCJ compatibility.
nice how ASF use SVN:
- devel in trunk.
- major and minor releases branched, for example: 1.2.x, 1.3.x and 1.5.x
- tags reflect branches release.

GIT is a nice tool, we should think about it! (trac problem?)

> 2) Create a source copyright template.

Still not try to create ones, but have an idea how should be:
- a standard part with EPL.
- a standard part with PHPEclipse team
- a part with contributors old and active.
- SVN information.

we need also javadoc template for:
- packages
- classes
- members
- methods

Define a standard for methods order:
- implemented interfaces
- public, protected and private

code layout; <imho> many times don't like auto formatting</imho>

> 3) there are alot of nasty code, expecially inside parsers.

hard_work

> 4) Decide if we have to move to 100% AST.

hard_work++ ;-)


Mauro "Incastrix" Casciari



      =


---------------------------------------------------------------------------=
---
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you.  Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/