Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update form_us.xml #542

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update form_us.xml #542

wants to merge 1 commit into from

Conversation

Caulley
Copy link

@Caulley Caulley commented Jun 16, 2022

No description provided.

Copy link
Author

@Caulley Caulley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added <_longname> and formatted.

@prculley prculley changed the base branch from master to maintenance/gramps51 June 24, 2023 16:37
@prculley prculley changed the base branch from maintenance/gramps51 to master June 24, 2023 16:38
@prculley prculley mentioned this pull request Jun 24, 2023
@prculley
Copy link
Contributor

Are you sure you want this in master branch? It may be a long time (years) before another major release of gramps from master branch occurs. Usually it makes more sense to apply addons changes to the current maintenance branch, as these eventually get merged into master branch anyway.

@jralls
Copy link
Member

jralls commented Jun 24, 2023

@prculley the roadmap says we're releasing 5.2.0 at the end of next month, and since it's a new major-ish release commits are still going to master.

Do you mean to announce a many-years schedule slip?

@Caulley
Copy link
Author

Caulley commented Jun 26, 2023

Hi Paul
I am sending this on behalf of my father. He was in an accident and is unable to respond himself. About the form_us.xml changes. He said that the Would War 2 form had been completed and checked to ensure that the changes would not effect any data that had already been input and should be released. The other form was a census and should not be released and disregarded completely. He hopes this is useful.

@Nick-Hall
Copy link
Member

the roadmap says we're releasing 5.2.0 at the end of next month

Hopefully, I should be able to manage a release by the end of next month. This one is going to require quite a bit of work though. I'll post to the mailing list with more details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants