[sip-comm-dev] The 1.0 branch is here!


#1

Hey folks,

Some of you may have already noticed that there's a new branch, called
1.0 available on our svn repository:

https://sip-communicator.dev.java.net:/svn/sip-communicator/branches/1.0

This is the branch that is going to eventually lead to our 1.0 version.
Please make sure that _all_ 1.0 related changes are _only_ committed
there. These may include fixes for recognized bugs and commits
addressing issues from our tracker scheduled for the rc1.0 milestone.

This means that trunk is now open for new features and folks that have
been sitting on things like LDAP support, using proxies, exporting extra
SIP functionalities would now be able to commit them. Both the 1.0 and
trunk branches would be producing nightly builds.

All changes committed in the 1.0 branch would also end up back in trunk.
Now, whether or not this would happen automatically is a different
matter. I am currently looking into the various solutions that allow for
merge tracking with pre-1.5 SVN versions. Hopefully we'd be able to come
up with something.

A few more details on this problem:

Our initial plan here was to wait for a long scheduled java.net upgrade
in order to have our SVN repository upgraded to version 1.6 (currently
1.4). SVN 1.5 and newer have support for merge tracking [1] and this
greatly simplifies branch management. This upgrade was initially
scheduled for February 9th 2009. Unfortunately, for a variety of
technical, administrative and organizational issues the upgrade was
rescheduled a number of times. There's no specific date at this point as
to when it may actually happen.

In the mean time it appears that work has started on re-architecturing
the whole site architecture and that the java.net developers are now
working on replacing the core with a well known open source CMS. Last
time I talked to one of the administrators it seemed that the upgrade
would now have to wait for them to complete. There was no specific date
as to when this would happen but mid to end August was floated as a
reasonable expectation.

I guess that this would be the right time to consider moving to another
forge site like code.google.com, sf.net, or one of the many others that
do canned hosting. In addition to the upgrade delay described here
there's a huge performance issue for most of the European community
members (e.g. no project/SVN/issue tracker or other java.net page would
ever load for less than 10 seconds. Quite often we'd experience delays
that exceed 20). That and the fact that the situation at SUN seems to be
a bit uncertain since the Oracle acquisition have really got me thinking
about the migration option.

I've had a look at code.google.com and it seems that they even have the
option of importing SVN history so that's making the option even more
attractive. Still, I haven't found a complete and easy way of
replicating the issue database, and I believe there's no way at all to
migrate our mailing list archives. This makes the prospect of migration
look quite painful and for the time being this is the only thing that's
giving java.net an advantage (a considerable one at that).

Also, the long awaited upgrade and core shift are supposed to greatly
improve performance, so we might just as well wait a few more months and
see what happens.

However, we couldn't have afforded to wait that long to spin our 1.0
branch off, which is why we are now considering scripts like svnmerge.

Let's hope that we'll be able to come up with something reliable.

Cheers
Emil

···

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#2

Emil,

there's a huge performance issue for most of the European community
members (e.g. no project/SVN/issue tracker or other java.net page would
ever load for less than 10 seconds. Quite often we'd experience delays
that exceed 20).

Just an FYI -- The performance issue exists over here in the US as well,
although it's not quite as bad as what you're describing.

-Alan

···

On Tue, Jun 2, 2009 at 7:22 AM, Emil Ivov <emcho@sip-communicator.org>wrote:

Hey folks,

Some of you may have already noticed that there's a new branch, called
1.0 available on our svn repository:

https://sip-communicator.dev.java.net:/svn/sip-communicator/branches/1.0

This is the branch that is going to eventually lead to our 1.0 version.
Please make sure that _all_ 1.0 related changes are _only_ committed
there. These may include fixes for recognized bugs and commits
addressing issues from our tracker scheduled for the rc1.0 milestone.

This means that trunk is now open for new features and folks that have
been sitting on things like LDAP support, using proxies, exporting extra
SIP functionalities would now be able to commit them. Both the 1.0 and
trunk branches would be producing nightly builds.

All changes committed in the 1.0 branch would also end up back in trunk.
Now, whether or not this would happen automatically is a different
matter. I am currently looking into the various solutions that allow for
merge tracking with pre-1.5 SVN versions. Hopefully we'd be able to come
up with something.

A few more details on this problem:

Our initial plan here was to wait for a long scheduled java.net upgrade
in order to have our SVN repository upgraded to version 1.6 (currently
1.4). SVN 1.5 and newer have support for merge tracking [1] and this
greatly simplifies branch management. This upgrade was initially
scheduled for February 9th 2009. Unfortunately, for a variety of
technical, administrative and organizational issues the upgrade was
rescheduled a number of times. There's no specific date at this point as
to when it may actually happen.

In the mean time it appears that work has started on re-architecturing
the whole site architecture and that the java.net developers are now
working on replacing the core with a well known open source CMS. Last
time I talked to one of the administrators it seemed that the upgrade
would now have to wait for them to complete. There was no specific date
as to when this would happen but mid to end August was floated as a
reasonable expectation.

I guess that this would be the right time to consider moving to another
forge site like code.google.com, sf.net, or one of the many others that
do canned hosting. In addition to the upgrade delay described here
there's a huge performance issue for most of the European community
members (e.g. no project/SVN/issue tracker or other java.net page would
ever load for less than 10 seconds. Quite often we'd experience delays
that exceed 20). That and the fact that the situation at SUN seems to be
a bit uncertain since the Oracle acquisition have really got me thinking
about the migration option.

I've had a look at code.google.com and it seems that they even have the
option of importing SVN history so that's making the option even more
attractive. Still, I haven't found a complete and easy way of
replicating the issue database, and I believe there's no way at all to
migrate our mailing list archives. This makes the prospect of migration
look quite painful and for the time being this is the only thing that's
giving java.net an advantage (a considerable one at that).

Also, the long awaited upgrade and core shift are supposed to greatly
improve performance, so we might just as well wait a few more months and
see what happens.

However, we couldn't have afforded to wait that long to spin our 1.0
branch off, which is why we are now considering scripts like svnmerge.

Let's hope that we'll be able to come up with something reliable.

Cheers
Emil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#3

Hi Emil,

Thank you for the information! Not only because it answers questions
we've been facing for a few months now but also because it touches on
alternatives I didn't dare mention.

For the abysmally slow performance alone, I'd personally ditch
java.net now and go with code.google.com (or any other project hosting
which is better than java.net) while trunk is still virgin after you
created branches/1.0. The endless delay of the updates only make that
decision sound right. At the end of the day, code.google.com has
Subversion 1.5 now, I don't remember past experience of slow access to
its issue tracker and groups.google.com seems to be OK with respect to
mailing lists for various projects already while java.net isn't there
yet and may or may not be there in the foreseeable future.

Anyway, I understand the migration isn't trivial and I can see why
we'd want to wait a few more months for java.net to get their act
together. I hope they actually will before long.

Best regards,
Lubo

···

2009/6/2 Alan Kelly <akoriolesfan@gmail.com>:

Emil,

there's a huge performance issue for most of the European community
members (e.g. no project/SVN/issue tracker or other java.net page would
ever load for less than 10 seconds. Quite often we'd experience delays
that exceed 20).

Just an FYI -- The performance issue exists over here in the US as well,
although it's not quite as bad as what you're describing.

-Alan

On Tue, Jun 2, 2009 at 7:22 AM, Emil Ivov <emcho@sip-communicator.org> > wrote:

Hey folks,

Some of you may have already noticed that there's a new branch, called
1.0 available on our svn repository:

https://sip-communicator.dev.java.net:/svn/sip-communicator/branches/1.0

This is the branch that is going to eventually lead to our 1.0 version.
Please make sure that _all_ 1.0 related changes are _only_ committed
there. These may include fixes for recognized bugs and commits
addressing issues from our tracker scheduled for the rc1.0 milestone.

This means that trunk is now open for new features and folks that have
been sitting on things like LDAP support, using proxies, exporting extra
SIP functionalities would now be able to commit them. Both the 1.0 and
trunk branches would be producing nightly builds.

All changes committed in the 1.0 branch would also end up back in trunk.
Now, whether or not this would happen automatically is a different
matter. I am currently looking into the various solutions that allow for
merge tracking with pre-1.5 SVN versions. Hopefully we'd be able to come
up with something.

A few more details on this problem:

Our initial plan here was to wait for a long scheduled java.net upgrade
in order to have our SVN repository upgraded to version 1.6 (currently
1.4). SVN 1.5 and newer have support for merge tracking [1] and this
greatly simplifies branch management. This upgrade was initially
scheduled for February 9th 2009. Unfortunately, for a variety of
technical, administrative and organizational issues the upgrade was
rescheduled a number of times. There's no specific date at this point as
to when it may actually happen.

In the mean time it appears that work has started on re-architecturing
the whole site architecture and that the java.net developers are now
working on replacing the core with a well known open source CMS. Last
time I talked to one of the administrators it seemed that the upgrade
would now have to wait for them to complete. There was no specific date
as to when this would happen but mid to end August was floated as a
reasonable expectation.

I guess that this would be the right time to consider moving to another
forge site like code.google.com, sf.net, or one of the many others that
do canned hosting. In addition to the upgrade delay described here
there's a huge performance issue for most of the European community
members (e.g. no project/SVN/issue tracker or other java.net page would
ever load for less than 10 seconds. Quite often we'd experience delays
that exceed 20). That and the fact that the situation at SUN seems to be
a bit uncertain since the Oracle acquisition have really got me thinking
about the migration option.

I've had a look at code.google.com and it seems that they even have the
option of importing SVN history so that's making the option even more
attractive. Still, I haven't found a complete and easy way of
replicating the issue database, and I believe there's no way at all to
migrate our mailing list archives. This makes the prospect of migration
look quite painful and for the time being this is the only thing that's
giving java.net an advantage (a considerable one at that).

Also, the long awaited upgrade and core shift are supposed to greatly
improve performance, so we might just as well wait a few more months and
see what happens.

However, we couldn't have afforded to wait that long to spin our 1.0
branch off, which is why we are now considering scripts like svnmerge.

Let's hope that we'll be able to come up with something reliable.

Cheers
Emil

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net