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

Add changelog and release #180

Closed
izqui opened this issue Jan 10, 2018 · 8 comments
Closed

Add changelog and release #180

izqui opened this issue Jan 10, 2018 · 8 comments

Comments

@izqui
Copy link
Contributor

izqui commented Jan 10, 2018

No description provided.

@izqui izqui added the meta label Jan 14, 2018
@izqui izqui added this to the 0.5 code freeze milestone Jan 14, 2018
@izqui izqui changed the title Add changelog Add changelog and release Jan 25, 2018
@sohkai sohkai removed this from the aragonOS 3.0 milestone May 8, 2018
@0x-r4bbit
Copy link

0x-r4bbit commented Aug 10, 2018

As discussed in aragon/aragon-cli#164 (comment) this can be easily achieved by sticking to a commit message convention that can be parsed to generate changelogs out from that automatically.

One convention that can be used is described here: aragon/aragon-cli#164 (comment)

On that note, would this be a valid case for creating an AGP to collectively decide whether such a convention should be used across all Aragon projects (for consistency)?

If yes, I could take a stab on that.

@sohkai
Copy link
Contributor

sohkai commented Aug 10, 2018

@PascalPrecht I'd love to start adopting something like conventional-changelog to make this more automated! Difficult part is to start agreeing, so an AGP would be a good start :).

We can also start deploying commit hooks, CI hooks, etc. to make sure we adhere to these standards, but as you can imagine, that's been on the backburner ;).

@0x-r4bbit
Copy link

Difficult part is to start agreeing, so an AGP would be a good start :)

Okay, I'll give this a spin then.

We can also start deploying commit hooks, CI hooks, etc. to make sure we adhere to these standards, but as you can imagine, that's been on the backburner ;)

Yes. I'd suggest we take it one step at a time. I'll go ahead and try to create my first AGP and then we take it from there. Once the community came to consensus, really the bread and butter is to stay disciplined and use those conventions everybody agreed on.

Adding the tooling is then the smallest problem I guess. We should also make sure to introduce dedicated contribution guideline (in case they don't exist yet).

Lemme give the AGP a try. I'll update this thread once done.

@izqui
Copy link
Contributor Author

izqui commented Aug 10, 2018

Completely support this, thanks @PascalPrecht for leading the initiative! looking fwd to the AGP

@0x-r4bbit
Copy link

Here's a first attempt: aragon/governance#31

@luisivan
Copy link
Contributor

Stale issue, closing now

@luisivan
Copy link
Contributor

(BTW thanks @PascalPrecht, seems like we are using a commit message convention now, plus we will be automating changelogs soon)

@0x-r4bbit
Copy link

That's awesome, happy to see conventions being applied! 👏

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

No branches or pull requests

4 participants