lso fail to
see any credible reason that Subversion cannot handle the development
here at Apache.
Before I comment on the SCM aspect, please let me introduce myself, as
I've just subscribed to this list. My name is Jens-Heiner Rechtien
(h...@openoffice.org). I've been with SO/OOo for mo
en-US)
bundled_extensions
This way someone can check out PREFIX/trunk/app and build a working OOo
without additional languages and save some time.
Heiner
--
Jens-Heiner Rechtien
.
Right, but don't underestimate the effort in doing the conversion
especially without having Ause, Michael or Björn around. Won't be
complete for many months to come.
Heiner
--
Jens-Heiner Rechtien
ludes all the "work in progress" in the CWSs we can
easily use OOO340m1 as staring point, as it just contains a few more
recent CWS integrations. It's almost equivalent as to using DEV300 m103
and redoing the latest integrations.
Regards,
Heiner
--
Jens-Heiner Rechtien
better now :-)
People are working on that, but we obviously have to wait. Let's use the
time to go through all files where the copyright situation is unclear or
where we already know that the copyright holder is someone else (I have
posted a first list already).
Heiner
--
Jens-Heiner Rechtien
h...@openoffice.org
jhrecht...@web.de
lists/discuss/archive/2011-03/message/14
Heiner
--
Jens-Heiner Rechtien
Hi Christian,
On 06/17/2011 04:42 PM, Christian Lohmaier wrote:
Hi Heiner, *,
On Fri, Jun 17, 2011 at 4:25 PM, Jens-Heiner Rechtien wrote:
On 06/17/2011 03:57 PM, Christian Lohmaier wrote:
On Fri, Jun 17, 2011 at 3:46 PM, Daniel Shahaf
wrote:
Christian Lohmaier wrote on Fri, Jun 17, 2011
On 06/17/2011 10:12 PM, Greg Stein wrote:
On Fri, Jun 17, 2011 at 08:55, Jens-Heiner Rechtien wrote:
...
The OOO340 codeline contains the DEV300_m106 tag so OOO340 is definitely
branched of DEV300_m106, which is incidentally also the very last milestone
we did on DEV300. Using m103 does not
ercurial repository, add all the patches and then convert this into an
svn repository.
What do the experts say?
Heiner
--
Jens-Heiner Rechtien
e patch approach Mathias suggested.
Never thought that we would ever have to go back to Subversion :-)
Heiner
--
Jens-Heiner Rechtien
size of the resulting SVN repository from
~90GB to ~7GB if I remember this right. Historical milestone information
has been dropped.
2009: import of SVN trunk in HG. No CWS branch in SVN has been migrated
as Herbert remarked correctly.
Heiner
--
Jens-Heiner Rechtien
On 06/27/2011 10:08 AM, Mathias Bauer wrote:
On 25.06.2011 14:05, Jens-Heiner Rechtien wrote:
Hi Mathias,
On 06/23/2011 07:15 PM, Mathias Bauer wrote:
Hi,
I'm no svn expert, but I hope to find some here.
We still have a lot of work in so called child workspaces (in Mercurial
they are
On 06/27/2011 01:08 AM, Greg Stein wrote:
On Sat, Jun 25, 2011 at 08:21, Jens-Heiner Rechtien wrote:
On 06/23/2011 09:17 PM, Greg Stein wrote:
On Thu, Jun 23, 2011 at 14:02, Pedro F. Giffuni
wrote:
Disclaimer: I am no SVN expert but I play a lot with
FreeBSD's SVN repository.
--- O
wnstream project complains about upstream being unresponsive
:-). But I know that we've updated neon support regularly over the last
years.
Heiner
--
Jens-Heiner Rechtien
Hi Greg,
On 06/29/2011 05:27 AM, Greg Stein wrote:
On Mon, Jun 27, 2011 at 05:42, Jens-Heiner Rechtien wrote:
On 06/27/2011 01:08 AM, Greg Stein wrote:
...
Merging them in hg is easy, just pull/merge. But ... we are talking about
a
hundred or so CWSs here. In all kinds of readiness states
Hi Greg,
On 06/29/2011 07:14 AM, Greg Stein wrote:
On Sat, Jun 25, 2011 at 08:48, Jens-Heiner Rechtien wrote:
On 06/24/2011 09:07 AM, Stephan Bergmann wrote:
...
Which gets me thinking of the next topic, how exactly to import the
current OOo Hg repository into SVN. While Hg has the concept
rking with 4G files (oh, wait! Hg can't deal with
files that size!) then sending a delta is very important.
Of course, anyone who actually commits 4G files to a *source* code
repository should be tarred and feathered.
[... snip ...]
Heiner
--
Jens-Heiner Rechtien
ally OOO340 was branched of DEV300 m106, thus there is no new
stuff in the main development code line DEV300 which is not also in
OOO340. Lucky timing, for once. There was just one milestone m1 on
OOO340 with the integration of about a handful of bug fixes and a few
late features.
Heiner
--
Jens-Heiner Rechtien
n get OOO340 by using the DEV300.hg bundle,
then pulling from that repository?
Exactly.
You could also wait until tomorrow and directly download a OOO340.hg
bundle via http://hg.services.openoffice.org/bundle/OOO340.hg
The bundle should be available around 3:00 GMT tonight.
Regards,
Heiner
1) Will AOOo maintain the Solaris port?
2) Will AOOo release Solaris binaries?
I'd certainly encourage us to do #1, provided that we have volunteers
with Solaris expertise on the project to test, fix errors, etc.,
related to that port. Are you able to help with this? Or can you help
by intro
e to write
the conversion tools first we'll loose way to much time which could be
spent better on getting AOOo 3.4 (or whatever the first AOOo release
will be called) out of the door. A pity that Apache git support is not
ready for prime time ... would make things so much easier.
Hei
nches) in google
code sounds like a good approach.
Pedro.
Heiner
--
Jens-Heiner Rechtien
one
which is a bit surprising. Probably an artifact of the conversion tool.
Heiner
--
Jens-Heiner Rechtien
better handled with other mechanism, like Maven or so.
With SVN all this is less of a concern, naturally.
Heiner
--
Jens-Heiner Rechtien
it with CVSup, make a tarball and upload that somewhere...
probably nobody really wants to actually look at it, it's more of an
"insurance" thing, right?
Regards,
Heiner
--
Jens-Heiner Rechtien
25 matches
Mail list logo
