Skip to content

Correct PirateBoxScripts_Webserver branch #9

Open

Description

@MaStr

It came just in my mind, that we need to do an adjustment about the checked out branch on the repository PirateBoxScripts_Webserver

As we have on the auto-scripts the following list:

  • stable -> openwrt-piratebox-feed:master

  • beta -> openwrt-piratebox-feed:development

  • dev. -> local-feeds : master

    PirateBoxScripts_Webserver

  • stable -> master

    • beta ---> we need a special tag for this, that is applied to the corresponding branch/commit
  • dev ---> development

y.x.z

The version-number raises in y & x requires a change of the piratebox_image file. This is one of the dependencies between those two worlds

That is my idea about that problem

Activity

  1. stylesuxx commented on Sep 11, 2014

    @stylesuxx
    Contributor

    OK, will implement this.
    Can you explain the version number raises a bit more, I do not understand that right now,..

  2. MaStr commented on Sep 12, 2014

    @MaStr
    MemberAuthor

    Does this answers some of the questions: http://piratebox.cc/docs:version_numbers ?

  3. stylesuxx commented on Sep 12, 2014

    @stylesuxx
    Contributor

    OK, so so far I implemented the checkout of the dev branch when building a snapshot release => https://github.com/stylesuxx/openwrt-dev-environment/tree/feature/webserver-scripts-versions

    For beta we can pass a variable to the build indicating what exactly we want, maybe even as granular as a specific commit?

  4. MaStr commented on Sep 15, 2014

    @MaStr
    MemberAuthor

    I would use a specific tag on the Repository, that will be drawn as beta build.

    it will be called beta_snapshot and will be changed to the specific commit

  5. added a commit that references this issue on Sep 15, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions