Re: [Sugar-devel] Sugar 0.101.3 (unstable)
Because of some issue we had with git, the sugar tarball included a few less commits than intended. Here is a new tarball http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.101.5.tar.xz * Fix #4733 remove warning on username change * Fix issue with activity updater breaking on server errors On 8 March 2014 15:32, Daniel Narvaez dwnarv...@gmail.com wrote: Hello, this release marks our feature freeze for 0.102. Now let's focus on bug fixing! Sources: http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.101.4.tar.xz http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.101.3.tar.xz http://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/sugar-artwork-0.101.3.tar.xz Thanks to everyone involved! -- Daniel Narvaez -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar 0.101.3 (unstable)
We recently added a Release Notes section in developer.sugarlabs.org :-) http://developer.sugarlabs.org/release-notes/102.md.html We agreed to add the deprecations notes there. 2014-03-09 21:10 GMT-03:00 Walter Bender walter.ben...@gmail.com: It didn't take me too long to pull together http://wiki.sugarlabs.org/go/0.102/Notes and I am happy to do the same again for the other unstable releases. We need to do some more work for the stable release as per Gonzalo's comments. -walter On Sun, Mar 9, 2014 at 8:04 PM, Daniel Narvaez dwnarv...@gmail.com wrote: The discussion started because Peter would like to have release notes for unstable releases. (Though he might be content with those being just the git logs). On 10 March 2014 01:01, Gonzalo Odiard godi...@sugarlabs.org wrote: I am not thinking in doing it for every unstable release, just for 0.102. I already did it for 0.100, I can volunteer to do it again in 0.102 Gonzalo On Sun, Mar 9, 2014 at 8:58 PM, Daniel Narvaez dwnarv...@gmail.com wrote: The thing is, I don't have time to do that manually for each unstable release. We either need a volunteer to do it or a way to generate it automatically from the log (which was the goal of my suggestion). On 10 March 2014 00:56, Gonzalo Odiard godi...@sugarlabs.org wrote: In the end, we need a summary to the end public, we can prepare it like in the past, based in the commit messages. Gonzalo On Sun, Mar 9, 2014 at 8:41 PM, Daniel Narvaez dwnarv...@gmail.com wrote: On 9 March 2014 22:31, Gaurav Parida gparid...@gmail.com wrote: Keeping the commit messages, will help in knowing the changes done in a release. The documentation aspect of a new release will be easily handled. +1 for the idea. On Mon, Mar 10, 2014 at 2:35 AM, Walter Bender walter.ben...@gmail.com wrote: Just as a rough sketch of what pulling the commit messages would look like, I've set up http://wiki.sugarlabs.org/go/0.102/Notes -walter The mockups look good. It would be great if each one them also has the link to the merge request. In my opinion, the commit messages will be more understandable, if we put some guidelines for them. like preappend the commit messages with with [Feature] / [Bug Fix #] / [Defect] / [Upgrade] from now on... We could include in the release notes only the subject of commits tagged like that. That would avoid to have too many irrelevant implementation details in the notes and also to simply omit commits that are not relevant (like refactorings etc). ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Gonzalo Odiard SugarLabs - Learning Software for children -- Daniel Narvaez -- Gonzalo Odiard SugarLabs - Learning Software for children -- Daniel Narvaez -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar 0.101.3 (unstable)
On Mon, Mar 10, 2014 at 10:42 AM, Manuel Quiñones ma...@laptop.org wrote: We recently added a Release Notes section in developer.sugarlabs.org :-) http://developer.sugarlabs.org/release-notes/102.md.html This will be very nice for developers. Maybe less nice for our end users. Seems we will probably need both. I'll point to this page from the wiki page. We agreed to add the deprecations notes there. 2014-03-09 21:10 GMT-03:00 Walter Bender walter.ben...@gmail.com: It didn't take me too long to pull together http://wiki.sugarlabs.org/go/0.102/Notes and I am happy to do the same again for the other unstable releases. We need to do some more work for the stable release as per Gonzalo's comments. -walter On Sun, Mar 9, 2014 at 8:04 PM, Daniel Narvaez dwnarv...@gmail.com wrote: The discussion started because Peter would like to have release notes for unstable releases. (Though he might be content with those being just the git logs). On 10 March 2014 01:01, Gonzalo Odiard godi...@sugarlabs.org wrote: I am not thinking in doing it for every unstable release, just for 0.102. I already did it for 0.100, I can volunteer to do it again in 0.102 Gonzalo On Sun, Mar 9, 2014 at 8:58 PM, Daniel Narvaez dwnarv...@gmail.com wrote: The thing is, I don't have time to do that manually for each unstable release. We either need a volunteer to do it or a way to generate it automatically from the log (which was the goal of my suggestion). On 10 March 2014 00:56, Gonzalo Odiard godi...@sugarlabs.org wrote: In the end, we need a summary to the end public, we can prepare it like in the past, based in the commit messages. Gonzalo On Sun, Mar 9, 2014 at 8:41 PM, Daniel Narvaez dwnarv...@gmail.com wrote: On 9 March 2014 22:31, Gaurav Parida gparid...@gmail.com wrote: Keeping the commit messages, will help in knowing the changes done in a release. The documentation aspect of a new release will be easily handled. +1 for the idea. On Mon, Mar 10, 2014 at 2:35 AM, Walter Bender walter.ben...@gmail.com wrote: Just as a rough sketch of what pulling the commit messages would look like, I've set up http://wiki.sugarlabs.org/go/0.102/Notes -walter The mockups look good. It would be great if each one them also has the link to the merge request. In my opinion, the commit messages will be more understandable, if we put some guidelines for them. like preappend the commit messages with with [Feature] / [Bug Fix #] / [Defect] / [Upgrade] from now on... We could include in the release notes only the subject of commits tagged like that. That would avoid to have too many irrelevant implementation details in the notes and also to simply omit commits that are not relevant (like refactorings etc). ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Gonzalo Odiard SugarLabs - Learning Software for children -- Daniel Narvaez -- Gonzalo Odiard SugarLabs - Learning Software for children -- Daniel Narvaez -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- .. manuq .. -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar 0.101.3 (unstable)
this release marks our feature freeze for 0.102. Now let's focus on bug fixing! It would be useful to see release notes for each release so as to know what's changed, added and needs to be tested rather than a tarball list dumped to the list. Sources: http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.101.4.tar.xz http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.101.3.tar.xz http://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/sugar-artwork-0.101.3.tar.xz Will be in tomorrow's F-21/rawhide compose. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar 0.101.3 (unstable)
On 9 March 2014 11:02, Peter Robinson pbrobin...@gmail.com wrote: this release marks our feature freeze for 0.102. Now let's focus on bug fixing! It would be useful to see release notes for each release so as to know what's changed, added and needs to be tested rather than a tarball list dumped to the list. I agree, but at the moment I have no time to do that myself. We could have a page in sugar-docs and reviewers would fill in items that are release note worthy when pushing pull requests. Sort of worried about raising the review barrier though. What do people think about that? ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar 0.101.3 (unstable)
this release marks our feature freeze for 0.102. Now let's focus on bug fixing! It would be useful to see release notes for each release so as to know what's changed, added and needs to be tested rather than a tarball list dumped to the list. I agree, but at the moment I have no time to do that myself. We could have a page in sugar-docs and reviewers would fill in items that are release note worthy when pushing pull requests. Sort of worried about raising the review barrier though. What do people think about that? Why can't it be auto generated using git and then you just have to make sure there's decent commit messages. Ultimately I think good commit messages should be compulsory because it tells you why changes were made. Peter ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar 0.101.3 (unstable)
The commit messages for our changes to Sugar core tend to be pretty decent. If we grab those and put them into a wiki page, then we could manually edit them into something more friendly to read once per release cycle. I volunteer to do the editing. Catching changes to the core activities is a bit more haphazard. But once the page is set up, we can put a call out to the maintainers in Fructose (a relatively small group). -walter On Sun, Mar 9, 2014 at 3:33 PM, Peter Robinson pbrobin...@gmail.com wrote: this release marks our feature freeze for 0.102. Now let's focus on bug fixing! It would be useful to see release notes for each release so as to know what's changed, added and needs to be tested rather than a tarball list dumped to the list. I agree, but at the moment I have no time to do that myself. We could have a page in sugar-docs and reviewers would fill in items that are release note worthy when pushing pull requests. Sort of worried about raising the review barrier though. What do people think about that? Why can't it be auto generated using git and then you just have to make sure there's decent commit messages. Ultimately I think good commit messages should be compulsory because it tells you why changes were made. Peter ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar 0.101.3 (unstable)
Just as a rough sketch of what pulling the commit messages would look like, I've set up http://wiki.sugarlabs.org/go/0.102/Notes -walter On Sun, Mar 9, 2014 at 4:37 PM, Walter Bender walter.ben...@gmail.com wrote: The commit messages for our changes to Sugar core tend to be pretty decent. If we grab those and put them into a wiki page, then we could manually edit them into something more friendly to read once per release cycle. I volunteer to do the editing. Catching changes to the core activities is a bit more haphazard. But once the page is set up, we can put a call out to the maintainers in Fructose (a relatively small group). -walter On Sun, Mar 9, 2014 at 3:33 PM, Peter Robinson pbrobin...@gmail.com wrote: this release marks our feature freeze for 0.102. Now let's focus on bug fixing! It would be useful to see release notes for each release so as to know what's changed, added and needs to be tested rather than a tarball list dumped to the list. I agree, but at the moment I have no time to do that myself. We could have a page in sugar-docs and reviewers would fill in items that are release note worthy when pushing pull requests. Sort of worried about raising the review barrier though. What do people think about that? Why can't it be auto generated using git and then you just have to make sure there's decent commit messages. Ultimately I think good commit messages should be compulsory because it tells you why changes were made. Peter ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Walter Bender Sugar Labs http://www.sugarlabs.org -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar 0.101.3 (unstable)
On 9 March 2014 20:33, Peter Robinson pbrobin...@gmail.com wrote: this release marks our feature freeze for 0.102. Now let's focus on bug fixing! It would be useful to see release notes for each release so as to know what's changed, added and needs to be tested rather than a tarball list dumped to the list. I agree, but at the moment I have no time to do that myself. We could have a page in sugar-docs and reviewers would fill in items that are release note worthy when pushing pull requests. Sort of worried about raising the review barrier though. What do people think about that? Why can't it be auto generated using git and then you just have to make sure there's decent commit messages. Ultimately I think good commit messages should be compulsory because it tells you why changes were made. In my experience good commits message and good commits split doesn't necessarily make a good list of changes for release notes. They target different audiences. That said it's certainly better than nothing and it might not be too bad given how usually the sugar log looks. I suppose we could just link to github compare (I wonder if there is a way to hide the code diff, it seems to be hidden automatically when there are a lot of commits) https://github.com/sugarlabs/sugar/compare/v0.101.3...v0.101.4 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar 0.101.3 (unstable)
On 9 March 2014 21:37, Walter Bender walter.ben...@gmail.com wrote: The commit messages for our changes to Sugar core tend to be pretty decent. If we grab those and put them into a wiki page, then we could manually edit them into something more friendly to read once per release cycle. I volunteer to do the editing. You mean editing when releasing a stable version or also for each unstable version? ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar 0.101.3 (unstable)
In the end, we need a summary to the end public, we can prepare it like in the past, based in the commit messages. Gonzalo On Sun, Mar 9, 2014 at 8:41 PM, Daniel Narvaez dwnarv...@gmail.com wrote: On 9 March 2014 22:31, Gaurav Parida gparid...@gmail.com wrote: Keeping the commit messages, will help in knowing the changes done in a release. The documentation aspect of a new release will be easily handled. +1 for the idea. On Mon, Mar 10, 2014 at 2:35 AM, Walter Bender walter.ben...@gmail.comwrote: Just as a rough sketch of what pulling the commit messages would look like, I've set up http://wiki.sugarlabs.org/go/0.102/Notes -walter The mockups look good. It would be great if each one them also has the link to the merge request. In my opinion, the commit messages will be more understandable, if we put some guidelines for them. like preappend the commit messages with with [Feature] / [Bug Fix #] / [Defect] / [Upgrade] from now on... We could include in the release notes only the subject of commits tagged like that. That would avoid to have too many irrelevant implementation details in the notes and also to simply omit commits that are not relevant (like refactorings etc). ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Gonzalo Odiard SugarLabs - Learning Software for children ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar 0.101.3 (unstable)
The thing is, I don't have time to do that manually for each unstable release. We either need a volunteer to do it or a way to generate it automatically from the log (which was the goal of my suggestion). On 10 March 2014 00:56, Gonzalo Odiard godi...@sugarlabs.org wrote: In the end, we need a summary to the end public, we can prepare it like in the past, based in the commit messages. Gonzalo On Sun, Mar 9, 2014 at 8:41 PM, Daniel Narvaez dwnarv...@gmail.comwrote: On 9 March 2014 22:31, Gaurav Parida gparid...@gmail.com wrote: Keeping the commit messages, will help in knowing the changes done in a release. The documentation aspect of a new release will be easily handled. +1 for the idea. On Mon, Mar 10, 2014 at 2:35 AM, Walter Bender walter.ben...@gmail.comwrote: Just as a rough sketch of what pulling the commit messages would look like, I've set up http://wiki.sugarlabs.org/go/0.102/Notes -walter The mockups look good. It would be great if each one them also has the link to the merge request. In my opinion, the commit messages will be more understandable, if we put some guidelines for them. like preappend the commit messages with with [Feature] / [Bug Fix #] / [Defect] / [Upgrade] from now on... We could include in the release notes only the subject of commits tagged like that. That would avoid to have too many irrelevant implementation details in the notes and also to simply omit commits that are not relevant (like refactorings etc). ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Gonzalo Odiard SugarLabs - Learning Software for children -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar 0.101.3 (unstable)
I am not thinking in doing it for every unstable release, just for 0.102. I already did it for 0.100, I can volunteer to do it again in 0.102 Gonzalo On Sun, Mar 9, 2014 at 8:58 PM, Daniel Narvaez dwnarv...@gmail.com wrote: The thing is, I don't have time to do that manually for each unstable release. We either need a volunteer to do it or a way to generate it automatically from the log (which was the goal of my suggestion). On 10 March 2014 00:56, Gonzalo Odiard godi...@sugarlabs.org wrote: In the end, we need a summary to the end public, we can prepare it like in the past, based in the commit messages. Gonzalo On Sun, Mar 9, 2014 at 8:41 PM, Daniel Narvaez dwnarv...@gmail.comwrote: On 9 March 2014 22:31, Gaurav Parida gparid...@gmail.com wrote: Keeping the commit messages, will help in knowing the changes done in a release. The documentation aspect of a new release will be easily handled. +1 for the idea. On Mon, Mar 10, 2014 at 2:35 AM, Walter Bender walter.ben...@gmail.com wrote: Just as a rough sketch of what pulling the commit messages would look like, I've set up http://wiki.sugarlabs.org/go/0.102/Notes -walter The mockups look good. It would be great if each one them also has the link to the merge request. In my opinion, the commit messages will be more understandable, if we put some guidelines for them. like preappend the commit messages with with [Feature] / [Bug Fix #] / [Defect] / [Upgrade] from now on... We could include in the release notes only the subject of commits tagged like that. That would avoid to have too many irrelevant implementation details in the notes and also to simply omit commits that are not relevant (like refactorings etc). ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Gonzalo Odiard SugarLabs - Learning Software for children -- Daniel Narvaez -- Gonzalo Odiard SugarLabs - Learning Software for children ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar 0.101.3 (unstable)
The discussion started because Peter would like to have release notes for unstable releases. (Though he might be content with those being just the git logs). On 10 March 2014 01:01, Gonzalo Odiard godi...@sugarlabs.org wrote: I am not thinking in doing it for every unstable release, just for 0.102. I already did it for 0.100, I can volunteer to do it again in 0.102 Gonzalo On Sun, Mar 9, 2014 at 8:58 PM, Daniel Narvaez dwnarv...@gmail.comwrote: The thing is, I don't have time to do that manually for each unstable release. We either need a volunteer to do it or a way to generate it automatically from the log (which was the goal of my suggestion). On 10 March 2014 00:56, Gonzalo Odiard godi...@sugarlabs.org wrote: In the end, we need a summary to the end public, we can prepare it like in the past, based in the commit messages. Gonzalo On Sun, Mar 9, 2014 at 8:41 PM, Daniel Narvaez dwnarv...@gmail.comwrote: On 9 March 2014 22:31, Gaurav Parida gparid...@gmail.com wrote: Keeping the commit messages, will help in knowing the changes done in a release. The documentation aspect of a new release will be easily handled. +1 for the idea. On Mon, Mar 10, 2014 at 2:35 AM, Walter Bender walter.ben...@gmail.com wrote: Just as a rough sketch of what pulling the commit messages would look like, I've set up http://wiki.sugarlabs.org/go/0.102/Notes -walter The mockups look good. It would be great if each one them also has the link to the merge request. In my opinion, the commit messages will be more understandable, if we put some guidelines for them. like preappend the commit messages with with [Feature] / [Bug Fix #] / [Defect] / [Upgrade] from now on... We could include in the release notes only the subject of commits tagged like that. That would avoid to have too many irrelevant implementation details in the notes and also to simply omit commits that are not relevant (like refactorings etc). ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Gonzalo Odiard SugarLabs - Learning Software for children -- Daniel Narvaez -- Gonzalo Odiard SugarLabs - Learning Software for children -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar 0.101.3 (unstable)
It didn't take me too long to pull together http://wiki.sugarlabs.org/go/0.102/Notes and I am happy to do the same again for the other unstable releases. We need to do some more work for the stable release as per Gonzalo's comments. -walter On Sun, Mar 9, 2014 at 8:04 PM, Daniel Narvaez dwnarv...@gmail.com wrote: The discussion started because Peter would like to have release notes for unstable releases. (Though he might be content with those being just the git logs). On 10 March 2014 01:01, Gonzalo Odiard godi...@sugarlabs.org wrote: I am not thinking in doing it for every unstable release, just for 0.102. I already did it for 0.100, I can volunteer to do it again in 0.102 Gonzalo On Sun, Mar 9, 2014 at 8:58 PM, Daniel Narvaez dwnarv...@gmail.com wrote: The thing is, I don't have time to do that manually for each unstable release. We either need a volunteer to do it or a way to generate it automatically from the log (which was the goal of my suggestion). On 10 March 2014 00:56, Gonzalo Odiard godi...@sugarlabs.org wrote: In the end, we need a summary to the end public, we can prepare it like in the past, based in the commit messages. Gonzalo On Sun, Mar 9, 2014 at 8:41 PM, Daniel Narvaez dwnarv...@gmail.com wrote: On 9 March 2014 22:31, Gaurav Parida gparid...@gmail.com wrote: Keeping the commit messages, will help in knowing the changes done in a release. The documentation aspect of a new release will be easily handled. +1 for the idea. On Mon, Mar 10, 2014 at 2:35 AM, Walter Bender walter.ben...@gmail.com wrote: Just as a rough sketch of what pulling the commit messages would look like, I've set up http://wiki.sugarlabs.org/go/0.102/Notes -walter The mockups look good. It would be great if each one them also has the link to the merge request. In my opinion, the commit messages will be more understandable, if we put some guidelines for them. like preappend the commit messages with with [Feature] / [Bug Fix #] / [Defect] / [Upgrade] from now on... We could include in the release notes only the subject of commits tagged like that. That would avoid to have too many irrelevant implementation details in the notes and also to simply omit commits that are not relevant (like refactorings etc). ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Gonzalo Odiard SugarLabs - Learning Software for children -- Daniel Narvaez -- Gonzalo Odiard SugarLabs - Learning Software for children -- Daniel Narvaez -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar 0.101.3 (unstable)
Great! So I'll let you know when 0.101.4 is tagged. On 10 March 2014 01:10, Walter Bender walter.ben...@gmail.com wrote: It didn't take me too long to pull together http://wiki.sugarlabs.org/go/0.102/Notes and I am happy to do the same again for the other unstable releases. We need to do some more work for the stable release as per Gonzalo's comments. -walter On Sun, Mar 9, 2014 at 8:04 PM, Daniel Narvaez dwnarv...@gmail.com wrote: The discussion started because Peter would like to have release notes for unstable releases. (Though he might be content with those being just the git logs). On 10 March 2014 01:01, Gonzalo Odiard godi...@sugarlabs.org wrote: I am not thinking in doing it for every unstable release, just for 0.102. I already did it for 0.100, I can volunteer to do it again in 0.102 Gonzalo On Sun, Mar 9, 2014 at 8:58 PM, Daniel Narvaez dwnarv...@gmail.com wrote: The thing is, I don't have time to do that manually for each unstable release. We either need a volunteer to do it or a way to generate it automatically from the log (which was the goal of my suggestion). On 10 March 2014 00:56, Gonzalo Odiard godi...@sugarlabs.org wrote: In the end, we need a summary to the end public, we can prepare it like in the past, based in the commit messages. Gonzalo On Sun, Mar 9, 2014 at 8:41 PM, Daniel Narvaez dwnarv...@gmail.com wrote: On 9 March 2014 22:31, Gaurav Parida gparid...@gmail.com wrote: Keeping the commit messages, will help in knowing the changes done in a release. The documentation aspect of a new release will be easily handled. +1 for the idea. On Mon, Mar 10, 2014 at 2:35 AM, Walter Bender walter.ben...@gmail.com wrote: Just as a rough sketch of what pulling the commit messages would look like, I've set up http://wiki.sugarlabs.org/go/0.102/Notes -walter The mockups look good. It would be great if each one them also has the link to the merge request. In my opinion, the commit messages will be more understandable, if we put some guidelines for them. like preappend the commit messages with with [Feature] / [Bug Fix #] / [Defect] / [Upgrade] from now on... We could include in the release notes only the subject of commits tagged like that. That would avoid to have too many irrelevant implementation details in the notes and also to simply omit commits that are not relevant (like refactorings etc). ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- Gonzalo Odiard SugarLabs - Learning Software for children -- Daniel Narvaez -- Gonzalo Odiard SugarLabs - Learning Software for children -- Daniel Narvaez -- Walter Bender Sugar Labs http://www.sugarlabs.org -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Sugar 0.101.3 (unstable)
Hello, this release marks our feature freeze for 0.102. Now let's focus on bug fixing! Sources: http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.101.4.tar.xz http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.101.3.tar.xz http://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/sugar-artwork-0.101.3.tar.xz Thanks to everyone involved! -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
