My view on this is that we, as committers have the responsabilities of:
1- Clear up your commit queue asap. The transaction period should
not last much longer. If you're depending on the q4e package
structure, it can change anytime.
2- Help in cleaning up after the move and make IAM conform to
eclipse standards and conventions
3- Make trunk compile successfully (and keep it that way)
Please don't be afraid of fixing errors, no matter what/who caused them.
So, Allan:
- You can commit (you are a committer :-) )
- If you have patches based on the q4e layout, commit them as soon
as possible (before someone else renames the packages).
- If you need to start new work on something that has not been
renamed, rename it first.
- If the code is not building, help in fixing the problems
- and... once everything is stable again, do not introduce code that
breaks the builds.
I think this has been said a couple of times, but I want to stress it
once again:
Q4E has been moved to Eclipse IAM. There are no restrictions to
committers anymore.
Yours,
On Tue, Nov 4, 2008 at 12:21 PM, Allan G. Ramirez <agramirez@xxxxxxxxx
<mailto:agramirez@xxxxxxxxx>> wrote:
Currently some packages are not yet renamed to iam like the
packages in pomeditor causing compile errors. Can we still commit
even if there are still compile errors?
Currently, i'm working on revision that does compile and it has
still devzuz packages on it so that i can still work on issues on
queue and I want to commit these changes to iam trunk.
I'll change the packages of these classes that i'm working on to
iam that is if it's ok to commit to trunk.
Carlos Sanchez wrote:
Added to http://wiki.eclipse.org/IAM_Moving_from_Google_Code
2008/11/1 Abel Muiño Vizcaino <amuino@xxxxxxxxx
<mailto:amuino@xxxxxxxxx>>:
We would need a list of things to change to get an idea of
how much work we
will need. That can take the form of documenting a
(manual) migration path
in the wiki.
After that, we might think in automating it.
El 01/11/2008, a las 4:40, Carlos Sanchez escribió:
all the plugins in the core feature have been renamed, now
we need to
consider where we need to support legacy naming.
ie recognize the old classpath container and change it to
the new name
2008/10/31 Joakim Erdfelt <joakim.erdfelt@xxxxxxxxx
<mailto:joakim.erdfelt@xxxxxxxxx>>
One niggle - "dependency.analisys"
The correct (American) spelling is analysis <347.gif>
- Joakim
On Wed, Oct 29, 2008 at 9:34 AM, Carlos Sanchez
<carlos@xxxxxxxxxxxxxxxx>
wrote:
IAM repo for anything already there
Google will be just for the embedder from now on
On Wed, Oct 29, 2008 at 12:51 AM, Allan G. Ramirez
<agramirez@xxxxxxxxx <mailto:agramirez@xxxxxxxxx>>
wrote:
By the way, where do we commit the changes is
it in iam repo
(https://dev.eclipse.org/svnroot/technology/org.eclipse.iam)
or still
in
google code?
Carlos Sanchez wrote:
yep, you should, you can comment it out if
needed
On Tue, Oct 28, 2008 at 6:32 PM, Korina
Cordero <kcordero@xxxxxxxxx
<mailto:kcordero@xxxxxxxxx>>
wrote:
I'm currently working on the Profiles
section. It's still in the
beginning
stage. It will compile but it's not
even coming close to running.
Do I
commit it now?
Carlos Sanchez wrote:
+1 to all
I've already made some changes
if anyone has patches, apply them
now or suffer later ;)
On Tue, Oct 28, 2008 at 1:41 PM,
Abel Muiño Vizcaino
<amuino@xxxxxxxxx
<mailto:amuino@xxxxxxxxx>>
wrote:
I'm proposing the following
changes on the q4e code
contributed to
IAM:
1) Rename the packages
"org.devzuz.q.maven.*" to
"org.eclipse.iam.*"(that
is, remove up to the "maven"
segment).
This is because what comes
after the project name (iam)
should be a
component (core, ui,
dependency, wtp...)
2) With the previous change,
update the package dependencies
declared
by
the
plug-ins.
Now the codebase should build
again
3) Make uniform use of the
maven conventions (some
projects have
source
code
on src, some on src/main/java)
4) Rename the plug-in
"org.eclipse.iam.maven.dependencyviewer"
to
"org.eclipse.iam.maven.dependency.viewer"
(i.e. split that last
segment
in
two)
This is to match the
dependency.analisys plug-in.
It makes sense to
have
them sharing the same naming
scheme.
5) Related to the previous
one, move the
org.devzuz.q.maven.dependency.*
in
the dependency viewer to
org.eclipse.iam.dependency.viewer
(insert
the
"viewer" segment that is
currently missing).
Sounds ok?
BTW: Does anybody know how to
get the commit messages emailed to
the
list,
like we had in google code?
--
Abel Muiño Vizcaino -
http://ramblingabout.wordpress.com
--~--~---------~--~----~------------~-------~--~----~
You received this message
because you are subscribed to
the Google
Groups
"Q
for Eclipse developers list"
group.
To post to this group, send
email to
q4e-dev@xxxxxxxxxxxxxxxx
<mailto:q4e-dev@xxxxxxxxxxxxxxxx>
To unsubscribe from this
group, send email to
q4e-dev+unsubscribe@xxxxxxxxxxxxxxxx
<mailto:q4e-dev%2Bunsubscribe@xxxxxxxxxxxxxxxx>
For more options, visit this
group at
http://groups.google.com/group/q4e-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
_______________________________________________
iam-dev mailing list
iam-dev@xxxxxxxxxxx
<mailto:iam-dev@xxxxxxxxxxx>
https://dev.eclipse.org/mailman/listinfo/iam-dev
_______________________________________________
iam-dev mailing list
iam-dev@xxxxxxxxxxx
<mailto:iam-dev@xxxxxxxxxxx>
https://dev.eclipse.org/mailman/listinfo/iam-dev
_______________________________________________
iam-dev mailing list
iam-dev@xxxxxxxxxxx
<mailto:iam-dev@xxxxxxxxxxx>
https://dev.eclipse.org/mailman/listinfo/iam-dev
_______________________________________________
iam-dev mailing list
iam-dev@xxxxxxxxxxx <mailto:iam-dev@xxxxxxxxxxx>
https://dev.eclipse.org/mailman/listinfo/iam-dev
_______________________________________________
iam-dev mailing list
iam-dev@xxxxxxxxxxx <mailto:iam-dev@xxxxxxxxxxx>
https://dev.eclipse.org/mailman/listinfo/iam-dev
_______________________________________________
iam-dev mailing list
iam-dev@xxxxxxxxxxx <mailto:iam-dev@xxxxxxxxxxx>
https://dev.eclipse.org/mailman/listinfo/iam-dev
_______________________________________________
iam-dev mailing list
iam-dev@xxxxxxxxxxx <mailto:iam-dev@xxxxxxxxxxx>
https://dev.eclipse.org/mailman/listinfo/iam-dev
_______________________________________________
iam-dev mailing list
iam-dev@xxxxxxxxxxx <mailto:iam-dev@xxxxxxxxxxx>
https://dev.eclipse.org/mailman/listinfo/iam-dev
_______________________________________________
iam-dev mailing list
iam-dev@xxxxxxxxxxx <mailto:iam-dev@xxxxxxxxxxx>
https://dev.eclipse.org/mailman/listinfo/iam-dev
_______________________________________________
iam-dev mailing list
iam-dev@xxxxxxxxxxx <mailto:iam-dev@xxxxxxxxxxx>
https://dev.eclipse.org/mailman/listinfo/iam-dev
--
Abel Muiño - http://ramblingabout.wordpress.com/
------------------------------------------------------------------------
_______________________________________________
iam-dev mailing list
iam-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/iam-dev
