Reanimate project from wicketstuff sandbox

[Per Newgro]

Hello,

maybe someone has some experiences with the topic and can support me.

I would like to update wicketstuff/sandbox/wicket-contrib-jamon.
I already forked the sandbox and transfered code from 1.3 to 1.4 to 1.5 
to 6 and now to 7.
Almost all problems are solved. There are some strange tests which 
checks that something is NOT running for 1.3
Maybe the founder of that project can give me some hints on this. But 
anyway.


I would like to clearify the next steps to publish my work to the community.

So far i've read the wicketstuff-wiki - contribute a new project - while 
it is not new :-).


I firstly need to adapt the project structure and put it unter 
wicketstuff/core. Do i need to fork wicketstuff-core

or can i request write-access to orginal repo?

My current master contains the wicket-7 version do i need to support 
earlier versions to? It would be no big problem.
Do i need to create a branch for every version then or is it enough to 
manage branch 1.3.x, 1.4.x and so on?


Thanks for your support
Per

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Reanimate project from wicketstuff sandbox

[Martin Grigorov]

Hi,

On Jan 10, 2016 9:42 AM, "Per Newgro"  wrote:
>
> Hello,
>
> maybe someone has some experiences with the topic and can support me.
>
> I would like to update wicketstuff/sandbox/wicket-contrib-jamon.
> I already forked the sandbox and transfered code from 1.3 to 1.4 to 1.5
to 6 and now to 7.
> Almost all problems are solved. There are some strange tests which checks
that something is NOT running for 1.3
> Maybe the founder of that project can give me some hints on this. But
anyway.

I have no idea about that.

>
> I would like to clearify the next steps to publish my work to the
community.
>
> So far i've read the wicketstuff-wiki - contribute a new project - while
it is not new :-).
>
> I firstly need to adapt the project structure and put it unter
wicketstuff/core. Do i need to fork wicketstuff-core
> or can i request write-access to orginal repo?

Whichever way you prefer.

>
> My current master contains the wicket-7 version do i need to support
earlier versions to? It would be no big problem.
> Do i need to create a branch for every version then or is it enough to
manage branch 1.3.x, 1.4.x and so on?

Since no one else needed this library for 1.3/1.4/1.5/6 I would recommend
to maintain it only in master branch, i.e. 7.x

>
> Thanks for your support
> Per
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>