2012/5/29 Markus Knauer <[email protected]> > Hi all, > > today I saw that a number of projects mention a version number in their > project plans that differs from the versions that they were contributing to > Juno RC1 last week, e.g. there are some projects that are still > contributing 0.x artifacts, but they will (hopefully) graduate together > with Juno and release a 1.0. Then there are other projects with a 1.3.x > contribution, but they promise to deliver a 2.0 together with Juno. > > Do we have any advice or best practice here? > > I would expect that projects update to their soon-to-be-released version > as soon as possible because there might be downstream projects that need to > adjust or other dependencies that need to be updated. And I don't think it > is good to wait with those changes until RC4. >
I plan to fix this for JGit/EGit tomorrow (1.3 -> 2.0) -- Matthias
_______________________________________________ cross-project-issues-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
