| Time |
Nick |
Message |
| 09:13 |
|
beardicus joined #evergreen |
| 09:22 |
|
Dyrcona joined #evergreen |
| 10:54 |
abneiman |
docs build Q: has the recent server upgrade changed anything about how release notes are built? does the symlink still need to be manually updated, or will committed changes to release notes show up automagically? |
| 11:01 |
|
Christineb joined #evergreen |
| 11:24 |
Dyrcona |
abneiman: The only thing that has changed is where the final release notes files go. |
| 11:25 |
Dyrcona |
The directory is now: /var/www/wordpress/documentation/release/ |
| 11:26 |
Dyrcona |
I see, you're asking about the automatic documentation build process? I don't know about that off the top of my head. |
| 11:35 |
abneiman |
Dyrcona++ |
| 11:35 |
abneiman |
Bmagic, do you know? |
| 11:37 |
Bmagic |
The docs server isn't the same server. Lupin is what was migrated. The docs server is called eg-docs |
| 11:39 |
abneiman |
so the link will still need to be updated if I push a release notes change? |
| 11:40 |
Bmagic |
So, nothing changes as far as Evergreen's official documentation (docs.evergreen-ils.org) - But the release notes and the README are part of what is published on the newly migrated server. As far as Evergreen's git repository is concerned, no changes. When the release notes change or a new branch is cut or a new release is published, the routine is basically the same as it was before with a slight difference in folder path on the |
| 11:40 |
Bmagic |
server |
| 11:41 |
abneiman |
ok. But if I push a change to extant release notes, does anything else need to happen after I push that for the change to be visible in the release notes? I thought there was an extra step |
| 12:00 |
|
jihpringle joined #evergreen |
| 12:00 |
|
smayo joined #evergreen |
| 12:01 |
smayo |
How does computers work? Asking for a friend. |
| 12:06 |
Dyrcona |
smayo: So, we taught rocks to think if we push electricity through them.... |
| 12:11 |
eby |
https://i.imgflip.com/atj6o5.jpg |
| 12:11 |
Dyrcona |
:) |
| 12:26 |
smayo |
:) |
| 12:45 |
|
collum joined #evergreen |
| 14:13 |
|
smayo joined #evergreen |
| 15:25 |
|
Dyrcona joined #evergreen |
| 15:42 |
* Dyrcona |
checks code to see if setting active = 'f' on staff accounts prevents them from logging in. |
| 15:46 |
Dyrcona |
Looks that will work, and so would setting barred = 't'. |
| 17:27 |
Bmagic |
abneiman: sorry for the delay. Changing the release notes in the repository does not* update the webstie. It doesn't work like the docs. Whereas the docs are regenerated nightly, we don't have any automation around generating new release notes docs for the wordpress site. It's part of the manual process for the release manager/build master teams. https://wiki.evergreen-ils.org/doku.php?id=dev:release_process:evergreen:how_to_build |
| 17:43 |
|
smayo joined #evergreen |
| 18:37 |
|
jihpringle joined #evergreen |
