Jerome WAGNER wrote:
I beileve that if i simply create 2.1-unstable branch and swithc my
working dir to
it, it will be much simpler for me and less load on your server.
So do you have any opposition to this approach?
Hello Vadim,
As Dave has tried to explain in recent threads, we are in the process
of releasing 2.1 in a few days.
Dave is going to help us work on rethinking the community processes
AFTER the 2.1 final release.
Please hold on to your modifications.
I certainly am opposed to a 2.1-unstable branch in the rush as you are
proposing.
The main focus in the next days should on 2.1 final. Please do not
blur this.
Jérôme
Ok folks,
I'm summarizing
I've spent 14 hours today trying to setup environement where i can do
something
equivalent svn commit without touching your repository, and still be
able to submit
my patches to you after 2.1 release.
I've tried it with bzr2svn which turned out does not support svn:external
and i've tried with svk, which chokes too because some problems with
utf8 conversion.
So basically as of today i can't use svn to continue developpement of
wengophone.
As i'm concetrating work of 2 others developpers and 5 test persons i'm
unable
to work without version control.
Your opposition to create a branch where i can commit without disturbing
your work
leaves me no option but to recommend to my client to create his own
repository on
his servers and to maintain a private fork.
I wanted to prevent this situation because i wanted to share our
developpemnt
(Parger Mode, SMS messages throuh Sip, Chat using conference server,
Server hosted buddy list) with openwengo project, but i can't work
without functioning
version control.
I'll publish link to this fork when i'll setup it, so you'll be able to
pull our
changes if you wish... But if will be up to you.
Thanks
Vadim
P.S.
Actually I'm totally baffled and offended by this situaton.
I understand that you're are under pressure to release 2.1 but i don't
REALLY
see how creation of a branch which I (not you) will maintain can bother
you?
_______________________________________________
Wengophone-devel mailing list
[email protected]
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
