Merge with Intland codebase and migrate of devsite to javaforge

[zingo]

Hello
As stated in a previous info update (before Christmast) there have
bean discussions with Intland on how to handle the dev hosting and
main dev repo. Intland did offered to take care of and host the
releases and devsite . They already have a project site up at
http://javaforge.com/project/HGE and in the near future they will
manage the 1.5 release. Currently they have named the project HgEclipe
to distinguish it from the mercurialeclipse from the bitbucket site
but the name will change back to mercurialeclipse and the bitbucket
site will migrated over to javaforge. I don't know if http://javaforge.com/project/HGE
will still be used or if a new project workplace will be created for
mercurialeclipse but we will probably know that soon.

During the coming days there will be a merge between the code of the
projects. After the initial merge the Issuetracker and wiki
documentation on bitbucket will be moved or locked and the bitbucket
site will not be the official devsite anymore.

The wiki documentation and Issues need migrating so if anyone is
interested in helping to get the documentation organized and better
structured on the new dev site please let me know.

Sorry for the inconvenience this might create.
/Zingo Andersen

[Duvel]

On 19 jan, 20:34, zingo <spamfil...@zingo.org> wrote:
> Hello
> As stated in a previous info update (before Christmast) there have
> bean discussions with Intland on how to handle the dev hosting and
> main dev repo. Intland did offered to take care of and host the

> releases and devsite . They already have a project site up athttp://javaforge.com/project/HGEand in the near future they will

> manage the 1.5 release. Currently they have named the project HgEclipe
> to distinguish it from the mercurialeclipse from the bitbucket site
> but the name will change back to mercurialeclipse and the bitbucket

> site will migrated over to javaforge. I don't know ifhttp://javaforge.com/project/HGE

> will still be used or if a new project workplace will be created for
> mercurialeclipse but we will probably know that soon.
>
> During the coming days there will be a merge between the code of the
> projects. After the initial merge the Issuetracker and wiki
> documentation on bitbucket will be moved or locked and the bitbucket
> site will not be the official devsite anymore.
>
> The wiki documentation and Issues need migrating so if anyone is
> interested in helping to get the documentation organized and better
> structured on the new dev site please let me know.

Is there already any news regarding a new repository and Issue
Tracker?

I'm now a little bit confused, where to create new issues and so.

I could for instance already check if my issues are still there and
move them to a new Issue Tracker.

With kind regards,

Remco Schoen (aka Duvel)

[Zingo Andersen]

Hello
As stated before the the project sites will be merged to the HgEclipse project site on javaforge.
The Idea is that Intland will release the MercurialEclipse 1.6 soon. issuetracking and main devsite
will be hosted on the javaforge site.

--
Zingo Andersen (zingo.org and vectrace.com)

> --
> You received this message because you are subscribed to the Google Groups "MercurialEclipse" group.
> To post to this group, send email to mercuria...@googlegroups.com.
> To unsubscribe from this group, send email to mercurialeclip...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/mercurialeclipse?hl=en.
>
>
>