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

Prepare RichWidgets for release #78

Closed
bleathem opened this issue Oct 30, 2013 · 15 comments
Closed

Prepare RichWidgets for release #78

bleathem opened this issue Oct 30, 2013 · 15 comments
Assignees
Milestone

Comments

@bleathem
Copy link
Member

@bleathem bleathem commented Oct 30, 2013

We have worked out a reasonable dist structure for our upcoming release, however there are a few release-related issues that have as yet to be addressed.

@ghost ghost assigned lfryc Nov 6, 2013
@lfryc
Copy link
Member

@lfryc lfryc commented Nov 7, 2013

I will investigate more what are our options.

@lfryc
Copy link
Member

@lfryc lfryc commented Nov 12, 2013

+1 Zip distribution - release notes can be added as a description (or even they might are available automatically on Milestones page)

@bleathem
Copy link
Member Author

@bleathem bleathem commented Nov 12, 2013

The git releases article describes how to manage release notes

@lfryc
Copy link
Member

@lfryc lfryc commented Nov 12, 2013

Ad Bower

We have agreed on team meeting that we will use CI to build a dist branch which one can use in Bower.

  • The dist branch will contain release tags.
  • The dist branch will be updated as a post-commit hook (Web Hook) using continuous integration.
@lfryc
Copy link
Member

@lfryc lfryc commented Nov 12, 2013

I will prototype it on a custom RichWidgets fork.

@lfryc
Copy link
Member

@lfryc lfryc commented Nov 18, 2013

Distribution generated automatically to https://github.com/richwidgets/richwidgets/commits/dist branch.

@bleathem can we register richwidgets package in bower repository now?

@bleathem
Copy link
Member Author

@bleathem bleathem commented Nov 18, 2013

@lfryc +1

Let's also change the RichFaces build to use this dist build, rather than the convoluted (and time consuming) process of building the bower dependency.

@bleathem
Copy link
Member Author

@bleathem bleathem commented Nov 18, 2013

I made the change to RichFaces with this commit:
richfaces/richfaces@4745212

We can update it to use the bower dependency directly once RichWidgets is present in the bower registry.

@ghost ghost assigned bleathem Nov 19, 2013
@lfryc
Copy link
Member

@lfryc lfryc commented Nov 22, 2013

@bleathem anything else needed to resolve this issue?

@bleathem
Copy link
Member Author

@bleathem bleathem commented Nov 22, 2013

There is the final outstanding task in the issue description:

Draft a release-process asciidoc file

@ghost ghost assigned lfryc Nov 24, 2013
@lfryc
Copy link
Member

@lfryc lfryc commented Nov 24, 2013

@bleathem , I have drafted a release process - would you mind to review it and review my comments?

https://gist.github.com/lfryc/7625055

@ghost ghost assigned bleathem Nov 24, 2013
@lfryc
Copy link
Member

@lfryc lfryc commented Nov 27, 2013

@bleathem : I have incorporated your suggestions, would you mind to give it final shot?

@lfryc
Copy link
Member

@lfryc lfryc commented Nov 28, 2013

The gist was updated according to the comments. @bleathem note that I don't get notifications for gist changes.

@lfryc lfryc closed this Nov 28, 2013
@lfryc lfryc reopened this Nov 28, 2013
@lfryc
Copy link
Member

@lfryc lfryc commented Nov 28, 2013

Ouch, closed accidentaly.

@ghost ghost assigned lfryc Nov 28, 2013
lfryc added a commit that referenced this issue Dec 2, 2013
@lfryc lfryc closed this Dec 2, 2013
@lfryc
Copy link
Member

@lfryc lfryc commented Dec 2, 2013

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

Successfully merging a pull request may close this issue.

None yet
2 participants