Menu

#77 Document things release technician can't do (i.e. upload to Stoa)

previous
done
5(medium)
2015-05-01
2014-07-31
No

The Release Process document (https://sourceforge.net/p/epidoc/wiki/ReleaseProc/) needs to specify which steps can only be carried out by someone with upload rights to Stoa.org (i.e. Gabby, Tom, Hugh, Ryan).

Discussion

  • BODARD Gabriel

    BODARD Gabriel - 2014-08-28
    • assigned_to: Simona Stoyanova
     
  • Simona Stoyanova

    • status: unread --> accepted
     
  • Simona Stoyanova

    • create a new directory in stoa with the value of the new release
    • copy files into it (ODD, RelaxNG, README)
    • update stoa.org/epidoc/schema/dev
    • copy new guidelines to stoa.org/epidoc/gl/dev
    • copy the new schema and other stuff from the release directory to the /latest directory
    • upload the zip archive of the example-p5-xslt directory to the Example Stylesheets folder in SourceForge

    Anything else?

     
  • BODARD Gabriel

    BODARD Gabriel - 2014-09-18

    Thanks, Simona. Yes, that sounds like more or less everything: all the Stoa.org related things, basically.

    (I think you should be able to do the last bit though, no? I think Charlotte was able to upload to the Sourceforge release area. Confirm with her when she's back next week...)

     
  • Simona Stoyanova

    I remember I couldn't do the last bit. I'll check with Charlotte, yes. Thank you!

     
  • Simona Stoyanova

    • status: accepted --> needs-feedback
     
  • BODARD Gabriel

    BODARD Gabriel - 2014-12-18

    Pietro has added a few final notes arising from the last release.

     
  • BODARD Gabriel

    BODARD Gabriel - 2014-12-18
    • assigned_to: Simona Stoyanova --> Pietro Maria Liuzzo
     
  • Pietro Maria Liuzzo

    • status: needs-feedback --> done
     
  • Tom Elliott

    Tom Elliott - 2015-05-01
    • Group: future --> previous
     

Log in to post a comment.