You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Peter Kovacs <Pe...@Apache.org> on 2019/08/03 05:47:09 UTC
Re: [resolution] svn migration plan
Hello all,
I have pushed Infra a bit. We are now migrating.
So migration will be finished soon.
I suggest we use the short hash.
I will try to change the Code link.
What else do we need to do?
Sorry if this moves now a bit uncoordinated, but I want to get this done.
On 29.07.19 20:39, Peter Kovacs wrote:
> On 29.07.19 17:18, Matthias Seidel wrote:
>> Hi Peter,
>>
>> Am 29.07.19 um 00:39 schrieb Peter Kovacs:
>>> A different suggestion we use the git commit count. The command is:
>>>
>>> |git rev-list --all --count It will deliver something that looks similar
>>> to the svn number we already use. All the Best Peter |
>> How would such a simple count point to a specific commit/revision?
>>
> I checked this,. In theory it should but there are a lots of option how
> to count in git.
>
> Which makes this not so optimal as on first glance. But it seems a lot
> of people use it to stick to a revision number.
>
> So there seems to be only 2 true options for referencing the commit:
>
> 1) We use the short hash.
>
> 2) We tag releases automatically at checkin.
>
>
> Tbh I would rather use the v
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [resolution] we are now on gitbox and github (was: svn migration
plan)
Posted by Mechtilde <oo...@mechtilde.de>.
Am 03.08.19 um 10:16 schrieb Peter Kovacs:
> I have not managed to find the information to change in our source CMS
> webside.
>
> If you link your github account here with Apache, then you get write
> access on github directly:
>
> https://gitbox.apache.org/setup/
I'm trying to folloe the instructions
>
>
Kind 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
Re: [resolution] we are now on gitbox and github (was: svn migration
plan)
Posted by Peter Kovacs <Pe...@Apache.org>.
I have not managed to find the information to change in our source CMS
webside.
If you link your github account here with Apache, then you get write
access on github directly:
https://gitbox.apache.org/setup/
All the Best
Peter
On 03.08.19 08:25, Peter Kovacs wrote:
> On 03.08.19 08:20, Mechtilde wrote:
>> Hello,
>>
>> Am 03.08.19 um 07:58 schrieb Damjan Jovanovic:
>>> On Sat, Aug 3, 2019 at 7:47 AM Peter Kovacs <Pe...@apache.org> wrote:
>>>> I suggest we use the short hash.
>>>>
>>>>
>>> For what? Why can't we "git tag" relevant commits and use the tag instead?
>> I think we should have an identifier for each build which is done beside
>> tha tag for the "relevant commits"
> Yea focus is more on development. For releases we should use or add the tag.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [resolution] svn migration plan
Posted by Matthias Seidel <ma...@hamburg.de>.
Hi Bidouille,
Am 03.08.19 um 11:47 schrieb Bidouille:
> Do you have published announcement on AOO blog?
We still have to iron out some things, but then I would definitely be
for a Blog post!
Regards,
Matthias
> That will be fine.
>
> ----- Mail original -----
>> De: "Peter Kovacs" <Pe...@Apache.org>
>> À: dev@openoffice.apache.org
>> Envoyé: Samedi 3 Août 2019 08:25:25
>> Objet: Re: [resolution] svn migration plan
>>
>>
>> On 03.08.19 08:20, Mechtilde wrote:
>>> Hello,
>>>
>>> Am 03.08.19 um 07:58 schrieb Damjan Jovanovic:
>>>> On Sat, Aug 3, 2019 at 7:47 AM Peter Kovacs <Pe...@apache.org>
>>>> wrote:
>>>>> I suggest we use the short hash.
>>>>>
>>>>>
>>>> For what? Why can't we "git tag" relevant commits and use the tag
>>>> instead?
>>> I think we should have an identifier for each build which is done
>>> beside
>>> tha tag for the "relevant commits"
>> Yea focus is more on development. For releases we should use or add
>> the tag.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
>> For additional commands, e-mail: dev-help@openoffice.apache.org
>>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>
Re: [resolution] svn migration plan
Posted by Bidouille <oo...@free.fr>.
Do you have published announcement on AOO blog?
That will be fine.
----- Mail original -----
> De: "Peter Kovacs" <Pe...@Apache.org>
> À: dev@openoffice.apache.org
> Envoyé: Samedi 3 Août 2019 08:25:25
> Objet: Re: [resolution] svn migration plan
>
>
> On 03.08.19 08:20, Mechtilde wrote:
> > Hello,
> >
> > Am 03.08.19 um 07:58 schrieb Damjan Jovanovic:
> >> On Sat, Aug 3, 2019 at 7:47 AM Peter Kovacs <Pe...@apache.org>
> >> wrote:
> >>> I suggest we use the short hash.
> >>>
> >>>
> >> For what? Why can't we "git tag" relevant commits and use the tag
> >> instead?
> > I think we should have an identifier for each build which is done
> > beside
> > tha tag for the "relevant commits"
> Yea focus is more on development. For releases we should use or add
> the tag.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [resolution] svn migration plan
Posted by Peter Kovacs <Pe...@Apache.org>.
On 03.08.19 08:20, Mechtilde wrote:
> Hello,
>
> Am 03.08.19 um 07:58 schrieb Damjan Jovanovic:
>> On Sat, Aug 3, 2019 at 7:47 AM Peter Kovacs <Pe...@apache.org> wrote:
>>> I suggest we use the short hash.
>>>
>>>
>> For what? Why can't we "git tag" relevant commits and use the tag instead?
> I think we should have an identifier for each build which is done beside
> tha tag for the "relevant commits"
Yea focus is more on development. For releases we should use or add the tag.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [resolution] svn migration plan
Posted by Mechtilde <oo...@mechtilde.de>.
Hello,
Am 03.08.19 um 07:58 schrieb Damjan Jovanovic:
> On Sat, Aug 3, 2019 at 7:47 AM Peter Kovacs <Pe...@apache.org> wrote:
>
>> Hello all,
>>
>> I have pushed Infra a bit. We are now migrating.
>>
>> So migration will be finished soon.
>>
>>
> Excellent :).
>
>
>>
>> I suggest we use the short hash.
>>
>>
> For what? Why can't we "git tag" relevant commits and use the tag instead?
I think we should have an identifier for each build which is done beside
tha tag for the "relevant commits"
>
> Damjan
>
Kind 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
Re: [resolution] svn migration plan
Posted by Damjan Jovanovic <da...@apache.org>.
On Sat, Aug 3, 2019 at 7:47 AM Peter Kovacs <Pe...@apache.org> wrote:
> Hello all,
>
> I have pushed Infra a bit. We are now migrating.
>
> So migration will be finished soon.
>
>
Excellent :).
>
> I suggest we use the short hash.
>
>
For what? Why can't we "git tag" relevant commits and use the tag instead?
Damjan
Re: [resolution] svn migration plan
Posted by Andrea Pescetti <pe...@apache.org>.
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: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [resolution] svn migration plan
Posted by Mechtilde <oo...@mechtilde.de>.
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
Re: [resolution] svn migration plan
Posted by Peter Kovacs <pe...@apache.org>.
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 <pe...@apache.org>:
>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: dev-unsubscribe@openoffice.apache.org
>For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [resolution] svn migration plan
Posted by Andrea Pescetti <pe...@apache.org>.
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: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: [resolution] svn migration plan
Posted by Mechtilde <oo...@mechtilde.de>.
Hello
Am 03.08.19 um 07:47 schrieb Peter Kovacs:
> Hello all,
>
> I have pushed Infra a bit. We are now migrating.
>
> So migration will be finished soon.
>
After finishing the migration the SVN repository is frozen.
All commits are only visible under
https://github.com/apache/openoffice
and under
https://gitbox.apache.org/repos/asf?p=openoffice.git
Peter wrotes:
If you link your github account here with Apache, then you get write
access on github directly:
https://gitbox.apache.org/setup/
Keind 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