[discussion] svn migration plan

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

Re: [discussion] CMS migration

Matthias Seidel
Hi Jörg,

Am 30.07.19 um 23:32 schrieb Jörg Schmidt:
> Hello,
>
> A fundamental question first:
> The "CMS migration" won't touch the wiki content? Right?
>
> (i mean: wiki.openoffice.org)
No, Wiki is a different server.

>
>
>> From: Peter Kovacs [mailto:[hidden email]]
>> Sent: Tuesday, July 30, 2019 7:58 AM
>> To: [hidden email]; Gavin McDonald
>> Subject: Re: [discussion] CMS migration
>> I had a quick look at the content. I think we do not need to migrate
>> everything. We should think about reducing the content.
>>
>> So we could try to identify the most important Pages, that are still
>> useful and then make a switch, taking offline everything
>> else, but keep
>> the SVN as archive. If there is interest in the material that
>> we did not
>> migrate we could add a migration request page.
> Sorry, but:
> What you are proposing here is an extremely large amount of work, _work that needs to be done carefully_.
>
> If we make mistakes, the loss of information will be a disaster. Not necessarily for the project, but for millions of users.
> For example, there are (probably) tens of thousands of websites that link to pages from openoffice.org. Our goal must be to maintain or redirect these link targets.
That is exactly why I tried to start this process years ago.

But you know what happened...

>
>
> I don't understand:
> Why is migration necessary at all?
I already told you on users-de@. ASF Infra can not support the old (self
baked) CMS anymore.
> I don't like the fact that programmers here spend time with this discussion (and possibly later with the migration), because the (unfortunately) few programmers we have should concentrate fully on the further development of the program.

Then it would be the perfect time to help those few people that already
spend so much time on this project? ;-)

Regards,

   Matthias

>
>
>> @all
>>
>> Maybe it would be nice to make a openoffice.org memorial. publishing a
>> freezed version of what is online today. It is maybe a stupid
>> Idea, but
>> looking through all the stuff, it feels like moving through old times.
> No, that's not a stupid idea. I explicitly support this idea, less as a memorial but rather as an archive and backup.
>
>
>
> greetings,
> Jörg
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


smime.p7s (5K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [discussion] CMS migration

Peter Kovacs-3

On 31.07.19 00:18, Matthias Seidel wrote
>> I don't understand:
>> Why is migration necessary at all?
> I already told you on users-de@. ASF Infra can not support the old (self
> baked) CMS anymore.

they replace it with another self baked solution... :/

With less overhead maybe.


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

Reply | Threaded
Open this post in threaded view
|

RE: [discussion] CMS migration

Jörg Schmidt-2
In reply to this post by Peter Kovacs-3
Hello Peter,

> From: Peter Kovacs [mailto:[hidden email]]
> Sent: Wednesday, July 31, 2019 12:07 AM
> To: [hidden email]
> Subject: Re: [discussion] CMS migration

> >> Maybe it would be nice to make a openoffice.org memorial.
> publishing a
> >> freezed version of what is online today. It is maybe a stupid
> >> Idea, but
> >> looking through all the stuff, it feels like moving
> through old times.
> > No, that's not a stupid idea. I explicitly support this
> idea, less as a memorial but rather as an archive and backup.
> thanks Jörg. Archieve or memorial are both fine for me. And useing
> openoffice.org might be also good for this.

How can we technically copy the web pages (and file attachments)?
Can this be done directly via the CMS, or do we have to use an offline reader?

I myself made a copy of www.openoffice.org with HTTrack Website Copier several years ago, but the result was not so good.



greetings,
Jörg


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

Reply | Threaded
Open this post in threaded view
|

RE: [discussion] CMS migration

Jörg Schmidt-2
In reply to this post by Matthias Seidel
Hello Mathias,

> From: Matthias Seidel [mailto:[hidden email]]
> Sent: Wednesday, July 31, 2019 12:19 AM
> To: [hidden email]
> Subject: Re: [discussion] CMS migration

> > If we make mistakes, the loss of information will be a
> disaster. Not necessarily for the project, but for millions of users.
> > For example, there are (probably) tens of thousands of
> websites that link to pages from openoffice.org. Our goal
> must be to maintain or redirect these link targets.
>
> That is exactly why I tried to start this process years ago.
>
> But you know what happened...

I know what you mean. I thought I was doing the right thing, but maybe I shouldn't have interfered.

> Then it would be the perfect time to help those few people
> that already
> spend so much time on this project? J

I'm sorry, but I don't have time. I understand the importance of the work, but I will not make a promise here that will raise hope, but which I will not be able to keep later.



greetings,
Jörg


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

Reply | Threaded
Open this post in threaded view
|

Re: [discussion] CMS migration

Dave Fisher-2
In reply to this post by Jörg Schmidt-2


> On Jul 30, 2019, at 3:56 PM, Jörg Schmidt <[hidden email]> wrote:
>
> Hello Peter,
>
>> From: Peter Kovacs [mailto:[hidden email]]
>> Sent: Wednesday, July 31, 2019 12:07 AM
>> To: [hidden email]
>> Subject: Re: [discussion] CMS migration
>
>>>> Maybe it would be nice to make a openoffice.org memorial.
>> publishing a
>>>> freezed version of what is online today. It is maybe a stupid
>>>> Idea, but
>>>> looking through all the stuff, it feels like moving
>> through old times.
>>> No, that's not a stupid idea. I explicitly support this
>> idea, less as a memorial but rather as an archive and backup.
>> thanks Jörg. Archieve or memorial are both fine for me. And useing
>> openoffice.org might be also good for this.
>
> How can we technically copy the web pages (and file attachments)?
> Can this be done directly via the CMS, or do we have to use an offline reader?
>
> I myself made a copy of www.openoffice.org with HTTrack Website Copier several years ago, but the result was not so good.

You can build the OpenOffice.org site on your computer by following the instructions here: https://openoffice.apache.org/website-local.html#setup

These instructions were written initially in December 2011 when I did the initial build locally. Note this is using python 2.

Regards,
Dave

>
>
>
> greetings,
> Jörg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


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

Reply | Threaded
Open this post in threaded view
|

Re: [discussion] CMS migration

Dave Fisher-2
In reply to this post by Peter Kovacs-3


> On Jul 30, 2019, at 3:29 PM, Peter Kovacs <[hidden email]> wrote:
>
>
> On 31.07.19 00:18, Matthias Seidel wrote
>>> I don't understand:
>>> Why is migration necessary at all?
>> I already told you on users-de@. ASF Infra can not support the old (self
>> baked) CMS anymore.
>
> they replace it with another self baked solution... :/

No, they prefer Pelican: https://github.com/getpelican/pelican it will support Github’s markdown and allow the preview of content within GitHub.

"the pelican setup sees the commit to master, builds the site, pushes to the asf-site branch, which the gitpubsub sees, and pulls that change to the active website"

There will be two major challenges.

(1) Creating our theme so that we continue to handle the NL translated elements in the header. An example page theme template is quite similar to what the CMS uses: https://github.com/getpelican/pelican/blob/master/pelican/themes/notmyidea/templates/page.html
(2) How to adapt the legacy html into the new template.

I plan to help, but only after ApacheCon NA. If someone else starts the process then I would gladly review and discuss.

Regards,
Dave

>
> With less overhead maybe.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>


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

Reply | Threaded
Open this post in threaded view
|

Re: [discussion] CMS migration

Peter Kovacs-3

On 31.07.19 01:29, Dave Fisher wrote:
>> they replace it with another self baked solution... :/
> No, they prefer Pelican: https://github.com/getpelican/pelican it will support Github’s markdown and allow the preview of content within GitHub.
>
Hmm sorry,  I thought for some reason that they are still in development
of the tool, But then we can start! So no waiting. :)

Dave, Raphael do you have may be time to Mentor George? - Would be cool
if we can make him a new committer.

 @ Raphael: Would be very nice to see you more active again.


All the best

Peter



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

Reply | Threaded
Open this post in threaded view
|

Re: [discussion] CMS migration

Kay Schenk-2
In reply to this post by Dave Fisher-2
Hi all.
A few questions --
* what's the status of the current OO website repositories -- both
https://openoffice.apache.org/ and https://www.openoffice.org/
in terms of updates? Are they both, as of today, still svn checkout?

* and since the CMS is broken (?), do updates to through svn go live
instantly or ????

* where are the instructions for the new "tool"?

Thanks.

On Tue, Jul 30, 2019 at 4:29 PM Dave Fisher <[hidden email]> wrote:

>
>
> > On Jul 30, 2019, at 3:29 PM, Peter Kovacs <[hidden email]> wrote:
> >
> >
> > On 31.07.19 00:18, Matthias Seidel wrote
> >>> I don't understand:
> >>> Why is migration necessary at all?
> >> I already told you on users-de@. ASF Infra can not support the old
> (self
> >> baked) CMS anymore.
> >
> > they replace it with another self baked solution... :/
>
> No, they prefer Pelican: https://github.com/getpelican/pelican it will
> support Github’s markdown and allow the preview of content within GitHub.
>
> "the pelican setup sees the commit to master, builds the site, pushes to
> the asf-site branch, which the gitpubsub sees, and pulls that change to the
> active website"
>
> There will be two major challenges.
>
> (1) Creating our theme so that we continue to handle the NL translated
> elements in the header. An example page theme template is quite similar to
> what the CMS uses:
> https://github.com/getpelican/pelican/blob/master/pelican/themes/notmyidea/templates/page.html
> (2) How to adapt the legacy html into the new template.
>
> I plan to help, but only after ApacheCon NA. If someone else starts the
> process then I would gladly review and discuss.
>
> Regards,
> Dave
>
> >
> > With less overhead maybe.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

--
"And in the end, only kindness matters."
   -- Jewel, "Hands"
________________________________________
MzK
Reply | Threaded
Open this post in threaded view
|

Re: [discussion] CMS migration

Matthias Seidel
Hi Kay,

Am 31.07.19 um 23:49 schrieb Kay Schenk:
> Hi all.
> A few questions --
> * what's the status of the current OO website repositories -- both
> https://openoffice.apache.org/ and https://www.openoffice.org/
> in terms of updates? Are they both, as of today, still svn checkout?

It is still functional for both sites...

However the staging does not work on https://openoffice.apache.org/ due
to the permanent https redirection.
But I can live with that... ;-)

>
> * and since the CMS is broken (?), do updates to through svn go live
> instantly or ????
I did a commit yesterday, all went fine (but did not publish yet).
>
> * where are the instructions for the new "tool"?

We are still discussing about a new system at the moment.

Regards,

   Matthias

>
> Thanks.
>
> On Tue, Jul 30, 2019 at 4:29 PM Dave Fisher <[hidden email]> wrote:
>
>>
>>> On Jul 30, 2019, at 3:29 PM, Peter Kovacs <[hidden email]> wrote:
>>>
>>>
>>> On 31.07.19 00:18, Matthias Seidel wrote
>>>>> I don't understand:
>>>>> Why is migration necessary at all?
>>>> I already told you on users-de@. ASF Infra can not support the old
>> (self
>>>> baked) CMS anymore.
>>> they replace it with another self baked solution... :/
>> No, they prefer Pelican: https://github.com/getpelican/pelican it will
>> support Github’s markdown and allow the preview of content within GitHub.
>>
>> "the pelican setup sees the commit to master, builds the site, pushes to
>> the asf-site branch, which the gitpubsub sees, and pulls that change to the
>> active website"
>>
>> There will be two major challenges.
>>
>> (1) Creating our theme so that we continue to handle the NL translated
>> elements in the header. An example page theme template is quite similar to
>> what the CMS uses:
>> https://github.com/getpelican/pelican/blob/master/pelican/themes/notmyidea/templates/page.html
>> (2) How to adapt the legacy html into the new template.
>>
>> I plan to help, but only after ApacheCon NA. If someone else starts the
>> process then I would gladly review and discuss.
>>
>> Regards,
>> Dave
>>
>>> With less overhead maybe.
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [hidden email]
>>> For additional commands, e-mail: [hidden email]
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>


smime.p7s (5K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [discussion] CMS migration

Kay Schenk-2
Thanks Matthias...

I didn't know if the control over publishing with --
https://cms.apache.org/
still worked or not.

I will investigate on my own soon.


On Thu, Aug 1, 2019 at 11:38 AM Matthias Seidel <[hidden email]>
wrote:

> Hi Kay,
>
> Am 31.07.19 um 23:49 schrieb Kay Schenk:
> > Hi all.
> > A few questions --
> > * what's the status of the current OO website repositories -- both
> > https://openoffice.apache.org/ and https://www.openoffice.org/
> > in terms of updates? Are they both, as of today, still svn checkout?
>
> It is still functional for both sites...
>
> However the staging does not work on https://openoffice.apache.org/ due
> to the permanent https redirection.
> But I can live with that... ;-)
>
> >
> > * and since the CMS is broken (?), do updates to through svn go live
> > instantly or ????
> I did a commit yesterday, all went fine (but did not publish yet).
> >
> > * where are the instructions for the new "tool"?
>
> We are still discussing about a new system at the moment.
>
> Regards,
>
>    Matthias
>
> >
> > Thanks.
> >
> > On Tue, Jul 30, 2019 at 4:29 PM Dave Fisher <[hidden email]> wrote:
> >
> >>
> >>> On Jul 30, 2019, at 3:29 PM, Peter Kovacs <[hidden email]> wrote:
> >>>
> >>>
> >>> On 31.07.19 00:18, Matthias Seidel wrote
> >>>>> I don't understand:
> >>>>> Why is migration necessary at all?
> >>>> I already told you on users-de@. ASF Infra can not support the old
> >> (self
> >>>> baked) CMS anymore.
> >>> they replace it with another self baked solution... :/
> >> No, they prefer Pelican: https://github.com/getpelican/pelican it will
> >> support Github’s markdown and allow the preview of content within
> GitHub.
> >>
> >> "the pelican setup sees the commit to master, builds the site, pushes to
> >> the asf-site branch, which the gitpubsub sees, and pulls that change to
> the
> >> active website"
> >>
> >> There will be two major challenges.
> >>
> >> (1) Creating our theme so that we continue to handle the NL translated
> >> elements in the header. An example page theme template is quite similar
> to
> >> what the CMS uses:
> >>
> https://github.com/getpelican/pelican/blob/master/pelican/themes/notmyidea/templates/page.html
> >> (2) How to adapt the legacy html into the new template.
> >>
> >> I plan to help, but only after ApacheCon NA. If someone else starts the
> >> process then I would gladly review and discuss.
> >>
> >> Regards,
> >> Dave
> >>
> >>> With less overhead maybe.
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: [hidden email]
> >>> For additional commands, e-mail: [hidden email]
> >>>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [hidden email]
> >> For additional commands, e-mail: [hidden email]
> >>
> >>
>
>

--
"And in the end, only kindness matters."
   -- Jewel, "Hands"
________________________________________
MzK
Reply | Threaded
Open this post in threaded view
|

Re: [resolution] svn migration plan

Peter Kovacs-3
In reply to this post by Peter Kovacs-3
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: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
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

Damjan Jovanovic
On Sat, Aug 3, 2019 at 7:47 AM Peter Kovacs <[hidden email]> 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
Reply | Threaded
Open this post in threaded view
|

Re: [resolution] svn migration plan

Mechtilde Stehmann-2
Hello,

Am 03.08.19 um 07:58 schrieb Damjan Jovanovic:

> On Sat, Aug 3, 2019 at 7:47 AM Peter Kovacs <[hidden email]> 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


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

Re: [resolution] svn migration plan

Peter Kovacs-3

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 <[hidden email]> 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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [resolution] we are now on gitbox and github (was: svn migration plan)

Peter Kovacs-3
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 <[hidden email]> 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: [hidden email]
> For additional commands, e-mail: [hidden email]
>

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

Reply | Threaded
Open this post in threaded view
|

Re: [resolution] we are now on gitbox and github (was: svn migration plan)

Mechtilde Stehmann-2


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


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

Re: [resolution] svn migration plan

FR web forum
In reply to this post by Peter Kovacs-3
Do you have published announcement on AOO blog?
That will be fine.

----- Mail original -----

> De: "Peter Kovacs" <[hidden email]>
> À: [hidden email]
> 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 <[hidden email]>
> >> 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: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

---------------------------------------------------------------------
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

Mechtilde Stehmann-2
In reply to this post by Peter Kovacs-3
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


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

Re: [resolution] svn migration plan

Matthias Seidel
In reply to this post by FR web forum
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" <[hidden email]>
>> À: [hidden email]
>> 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 <[hidden email]>
>>>> 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: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>


smime.p7s (5K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: [resolution] svn migration plan

Andrea Pescetti-2
In reply to this post by Peter Kovacs-3
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]

1234