/
Committers Call 2013-09-23

Samvera Community Wiki

Committers Call 2013-09-23

Jun 16, 2017

Attendees

  • Moderator: Jim Coble (Duke)

  • Notetaker: Carolyn Cole (PSU)

    • Attendees: Jeremy Friesen (ND)
                      Jim Coble (Duke)
                      David Chandek-Stark (Duke)
                      Ben Armintor (Columbia)
                      Michael Klein (NW)
                      Edgar Garcia (NW)
                      Adam Hallett (NW)
                      Justin Coyne (DCE)
                      Lakeisha Robinson (Yale)
                      

 

Agenda

  1. Roll call

  2. Call for agenda items

  3. Deprecation policy (Justin)

    1. Keep deprecation in minor versions remove in next major version

    2. Jeremy suggested keeping for at least one major version

    3. Late version deprecation is an issue.  Deprecated in 6.5  and then they are gone in 7.0

    4. Where is our deprecation policy documented?

    5. How do we walk people from the current version to the next with the deprecations

    6. We should created at least 1 more minor release after deprecations so that users can see the warnings

    7. Helpful to add a script so people can see the warnings

    8. Jeremy will grep the code in 6.6 and post the warnings 6.0 - 6.1 of the hydra gem

    9. If it has not been deprecated yet then any new deprecations will have to wait until version 8

    10. In the upgrade notes for 7 add the step upgrade to 6.6 look for deprecation warnings and then upgrade to 7

    11. Nothing has been removed yet until 7.0 has been created

    12. How do we evolve the code and bring all the partners along.

    13. Need to have a solution for both sets of users active fedora, and users of the hydra gem

    14. Solution bundles depend on new features not available in the current version of the hydra gem

    15. More people might move to using the hydra gem if solution bundles come out

    16. Nobody on the call has a problem with the notion that things could be deprecated in 6.6 and removed in 7

    17. Look for opportunities to give a smooth upgrade path by going to 6.6 first before going to 7

    18. If you are using the hydra gem go to 6.1 before you go to 7.0

    19. You will see the deprecation warnings in your code and more clearly shows up in your test suite

  4. Release ActiveFedora 6.6? (Justin)

    1. We are ready for this release. An email will be sent out on the hydra-tech

    2. Last minor release in the 6 series

  5. Someone review my pull requests. (Justin)

    1. Jeremy reviewed and merged the pull requests

    2. anyone that is a committer can review and merge a pull requests

    3. It is ok to give it a thumbs up on a pull request even if you do not merge it

    4. Get involved.  Merge a pull request!

  6. Dev. Congress review

    1. Mark may be sending an email out on hydra tech asking for feedback on format from those who were at the meeting

    2. Would be good to have a topic list ahead of time to have some more concrete topic

    3. Collaboration was useful

    4. Demo was good, and an email went out on the final status

    5. For a beginner the week was very helpful to getting people started in the community

    6. It was great to have the different levels of developer collaborating

  7. Hydra Gem

    1. Version 6.1

    2. Ned to do some planning.  Jeremy is signed up to do this

    3. Dependent on Active Fedora and minor release of hydra-head with pull requests merged

    4. Anyone using the hydra-6.0?  We need testers

    5. Virginia and/or Hull??  Need an email to see who is using the gem currently: Jeremy

  8. Feedback on Content (Ben)

    1. inline -  xml  

    2. Planning to send out emails to the list serve

    3. Fedora 3.7.0 is out and available

    4. Fedora committers wanted to do a stability path

    5. Mostly bug fixes and Java 7.0 upgrade

    6. 3.7.1 is coming out soon

    7. Library upgrades and performance improvements

    8. Fedora 3 depends on old sun xml serializers for pretty printing

    9. This matters for transactional data for inline xml datastreams in objects

    10. Can be done with pure xerces repositories, with the bug that they fixed but it affects the way and xml comment outside of the document are serialized by the serializer

    11. Ben wants examples of people who use inline xml documents and have comments before the root node

    12. Duke does not have any

  9. Next call: Monday Sept. 30th

    1. Moderator: Adam Wead (Rock Hall)

    2. Notetaker: Jeremy Friesen (ND)