The dev-tools from wrye-bash

First posts should not ask for milestone

The current release milestone does not exist (milestone is closed) so the scripts should just use latest changelog

Clean Up Repository

This repository was created, with a whole bunch of branches, from the wrye-bash-refactoring repository. Most of these branches are probably identical, so should be pruned.

Fallout 4 Threads and Nexus pages

Once/as we do an official release with Fallout 4 support, we'll need to update the scripts a bit to generate those posts as well. It looks like all that will be needed is getting the information needed to fill out the _Game parameters in scripts\globals.py

Clean Up Repository

This repository was created, with a whole bunch of branches, from the wrye-bash-refactoring repository. Most of these branches are probably identical, so should be pruned.

Ini file for the scripts

In the laudable tradition of Bash I suggest we have a default ini which contains

editor_path=C:\program Files\notepad++\notepad++.exe
skyrim_latest_thread=897896708
skyrim_prev_thread=876876869
oblivion_latest_thread=7777
oblivion_prev_thread=6666
# etc

And other such options for easy editing - those options would be awkward to pass as arguments to the scripts. I would appreciate someone writing (and committing in a branch) a kickoff module for reading this ini. The options would be overridden in a user ini and read from the default ONLY if the user hasn't overridden them.

The more I work with the scripts the more an ini such as this becomes a necessity - that's why I tag this bug.

Offline flag

Most of the scripts should work offline (all apart the changelogs/second posts)

Common changelog for all games

So instead of having special switches to generate changelogs for oblivion, skyrim etc have a common script that prepends [Oblivion], etc in the bug description (if not already there)

Move generate_changelog to main repo?

Since the py3 upgrade, this is now the only remaining script here. It feels weird having this script, which is central to releases, sitting around in some random repo, while everything else a developer needs to build and create a release is in the main repo.
Moving it to the main repo would also go well with our 'clone one repo and you're ready' workflow.

Obviously blocked on wrye-bash/wrye-bash#460, since this repo is now py3

Paging @wrye-bash/bashers for discussion

Autogenerate nexus description pages

Update links to point at git

All the meta-data needs to be updated to point at the GitHub site, rather than the old SourceForge repository

So from what I see we have:

Update links in Forum Starter post for Skyrim
Update links in Forum Starter post for Oblivion
Update links in Second Post templates (will be handled by script to generate second post)
Update links in the Nexus description pages

Standardize the changelog/issues format

We should agree on the changelog and issues display format and automate their creation for the various text formats we use

Nexus, First post, second post (issues open/closed) - bbcode
Version history - html
master changelog - markdown
release changelog - markdown

Discussion in the form of patches to scripts/html.py and scripts/generate_changelog.py

For a variety of formats see the first posts on the forums - in all:

[Bug enhancement ?][issue number ?][Game ?] Title [assignee]

Extend the scripts (changelog, automatic version history, second post etc)

@lojack5 I managed to write a changelog thingy which does not do much but it's a start: https://github.com/wrye-bash/meta/tree/utumno-changelog/SecondPosts. Output (edit 2014.03.28):

<h2>304.4 [2014/03/28] ['Various community members']</h2>
<ul>
    <li>Optimize PNGs [Metallicow]</li>
    <li>Remove the auto-updater [lojack5]</li>
    <li>Skip .bsl files for BAIN [lojack5]</li>
    <li>BOSSv3 support, installer and readme updates [WrinklyNinja]</li>
    <li>Installer Improvements [WrinklyNinja]</li>
    <li>Installer MSVC 2013 Redist Support [WrinklyNinja]</li>
    <li>Missing context menu items [WrinklyNinja]</li>
    <li>Show BSA Conflicts undocumented [WrinklyNinja]</li>
</ul>

I broke your code in modules to reuse it

the github_wrapper module is fine, maybe rethinking skip_labels parameters - ~~could be the labels we are interested in~~ -> we need a builder for issue lists, see code comments in getIssues()
the html module is fine too I think - maybe rename to formatting ?
the globals module has our wrye-bash/wrye-bash specific info and wraps the github for our repo - I marked its functions as _private (so subject to change)
if we go down that road we will need a templates/ subdir (to put stuff like generate_second_posts_lines.txt and .usr)
I am sure I did unpythonisms (and I miss toString())

What you say in all ?

(that's 305+ really)

EDIT:
These steps from the release guide(https://github.com/wrye-bash/wrye-bash/wiki/%5Bgithub%5D-Making-A-Release):

Update Wrye Bash Version History.html with this change log.
Update the same file in the Online Readme
Update the Skyrim/Oblivion/etc first posts with the new change log and version in the meta repository.
~~Update the Skyrim/Oblivion/etc Nexus Description page templates in meta with the new change log and version.~~
master commit message / release changelog --> that's the generate_cahngelog.writeChangelogBBcode() method

need automation.

Also

CLI Parser module

Python interface with git

We need (in order to automate some of the release steps) to interface with git in our scripts. GitPython may be the tool: https://pythonhosted.org/GitPython/0.3.1/tutorial.html (home: https://gitorious.org/git-python, see also http://www.samba.org/~jelmer/dulwich/ for an implementation of git "protocols" in python)

One thread starter

Bethesda forums are going down - so will go down the thread starter script for each subforum - keep the Oblivion one.

Do we need this repo ?

Wanted to push the editor files I am ripping from wrye-Bash somewhere and before I open a branch here (and make dirs like editors/eclipse-pydev, editors/pycharm etc) I want us to discuss a bit what's to be in here - and do we really need this repo ? Or could we just make a dev-tools folder in the meta repo and be done with it ? Not sure, but I'd say merge those two and be done with it - but I might be missing something

Changelogs changes

since we more often than not edit the label titles returned by the github client the changelogs must be rewritten so this edited text is saved then turned to a list (bbcode, mardown etc) - done in https://github.com/wrye-bash/meta/commit/3f527f8e2d6d49ef80bf6269da33512b3228853c
no more changelogs per game - just add the labels as in Bug 669 blah blah [Skyrim] - simplify !

Scripts enhancements

internal API for issues needs revamp - problem is how much will go to github_wrapper and how much to html - but as it is it is bad, bad, bad (try generating master changelog)
cache needs rewrite - I had seen somewhere try except KeyError but lost the page. Anyway (apart from pythonisms I'd like to add) there must be an exhaustive search in existing items to see if we can filter instead of hitting github - but I want to avoid the ifelseheimer - I need some OO trick there
~~nexus pages must be autogenerated too~~ issue wrye-bash/meta#14
get all labels ~~and throw if they are not up to date~~ they won't change this often (edit the main repo Labels wiki too)

Assigning to me but if anyone (Lo ?) wants to lend a patch...

Marking this bug btw just to bump the priority (in this repo makes sense to label bug high priority items and enhancement lower ones)

Repo Readme

Should contain links to the github api we use : https://github.com/jacquev6/PyGithub and a description of the folders.

needs not be long

wrye-bash / dev-tools Goto Github PK

dev-tools's Introduction

Wrye Bash

About

Supported Games

Download

Windows

Linux

Installation

WINE

Questions ? Feedback ?

Latest betas

Contributing

Main Branches

dev-tools's People

Stargazers

Watchers

Forkers

dev-tools's Issues

Recommend Projects

Recommend Topics

Recommend Org