[discussion] svn migration plan

classic Classic list List threaded Threaded
63 messages Options
1234
Reply | Threaded
Open this post in threaded view
|

Re: [resolution] svn migration plan

Mechtilde Stehmann-2
Hello Andrea,
hello  *

Am 14.08.19 um 11:21 schrieb Andrea Pescetti:

> On 03/08/2019 Peter Kovacs wrote:
>> I have pushed Infra a bit. We are now migrating. ...
>> Sorry if this moves now a bit uncoordinated, but I want to get this done.
>
> It's now clear that this was indeed quite rushed, but I'm prepared to
> working with git too and I'm sure we can fix the missing bits with time.
>
> For example, there is still a lot of documentation to be updated and
> adding a quick git clone command here and there in the wiki is enough
> for us, but confusing for the general public.
The entries I found, I added the git clone command
>
> Anyway, good to see this done! I'm remarking about the speed just
> because the CMS (which shouldn't have been part of this discussion at
> all) will require a much more detailed plan, as it is already very clear
> from the discussion on list.>
> Regards,
>   Andrea.

Regards

--
Mechtilde Stehmann
## Apache OpenOffice
## Freie Office Suite für Linux, MacOSX, Windows
## Debian Developer
## PGP encryption welcome
## F0E3 7F3D C87A 4998 2899  39E7 F287 7BBA 141A AD7F


signature.asc (849 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [resolution] svn migration plan

Peter Kovacs-3
In reply to this post by Andrea Pescetti-2
Agreed. Cms is another beast. I think it would be a good idea to sum up the current discussion on a cwiki page.


Am 14. August 2019 11:21:10 MESZ schrieb Andrea Pescetti <[hidden email]>:

>On 03/08/2019 Peter Kovacs wrote:
>> I have pushed Infra a bit. We are now migrating. ...
>> Sorry if this moves now a bit uncoordinated, but I want to get this
>done.
>
>It's now clear that this was indeed quite rushed, but I'm prepared to
>working with git too and I'm sure we can fix the missing bits with
>time.
>
>For example, there is still a lot of documentation to be updated and
>adding a quick git clone command here and there in the wiki is enough
>for us, but confusing for the general public.
>
>Anyway, good to see this done! I'm remarking about the speed just
>because the CMS (which shouldn't have been part of this discussion at
>all) will require a much more detailed plan, as it is already very
>clear
>from the discussion on list.
>
>Regards,
>   Andrea.
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [hidden email]
>For additional commands, e-mail: [hidden email]
Reply | Threaded
Open this post in threaded view
|

Re: [resolution] svn migration plan

Andrea Pescetti-2
In reply to this post by Mechtilde Stehmann-2
Mechtilde wrote:
> Am 14.08.19 um 11:21 schrieb Andrea Pescetti:
>> adding a quick git clone command here and there in the wiki is enough
>> for us, but confusing for the general public.
> The entries I found, I added the git clone command

This is a good example of something that is enough for us but confusing
for the general public. See

https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO

where we still have the SVN commands (which WILL work and give you the
frozen SVN trunk, with no indications that this is frozen; it is now
easy to say that we should have added a last SVN commit mentioning git),
then the new git command, then notes like "You can use git as well.
There exists no guide for this, therefore ask on dev@, if you want to
use git".

I would be for only listing the git commands, re-reading the entire page
and re-writing the sections that mention SVN.

Old versions of the page are easily visible to everybody, so we can use

https://wiki.openoffice.org/w/index.php?title=Documentation/Building_Guide_AOO&oldid=245569

as "the latest version before the switch to git" in case.

For sure, once one has properly ported

1. https://openoffice.apache.org/source.html

2. https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO

things will be much clearer to the public, but also to us (the fact that
I see patches sent by mail, and not link to pull requests, makes me
think we are still unclear about our own processes).

I will start with updating page 1 above; I think this will leave me with
some questions about what conventions we are using for git, so it will
be a useful exercise.

Regards,
   Andrea.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

1234