You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
this file give you a rough idea about how to draft/purpose a migration in atabse schema..
4
+
5
+
## Migration Rules / Migration Process
6
+
7
+
1. when you wanna change the database scheme, you have before time draft a new pr..
8
+
9
+
2. your new pr should draft a new dtabase scheme file, whn your pr merge in this docs repository. then only you can even write code in codebase releated to migration.
10
+
11
+
3. after, that code changes you have make two prs.. one in passcodes app repo and one in passcodes docs repo... this pr will we be merged together into both individuall repository at once..
This file will provide from when and where, the repository will be able to accept external contribution from other developers and community..
4
-
This will provide you the abstract idea / timeline, that you can look at and see, how much you need to wait, to contribute,
3
+
This file will provide from when and where, the repository will be able to accept external contribution from other developers and community..
4
+
This will provide you the abstract idea / timeline, that you can look at and see, how much you need to wait, to contribute,
5
5
Besides, it help cordinate the contribution process.... Also, we aim to provide you a clear timeline... And lay a path forward..
6
6
7
+
???+ Note
7
8
8
-
> [!NOTE]
9
-
> You can current still contribute to the repository, if you plan to do so... But just keep in mind that, while do so, you may feel like everything is behind you,
10
-
> and fight against you.. and this will slow you down.. also expect, less streamline process and you also expect some of your time waste..
11
-
>
12
-
> But, I will try my best to help as much as possible, on our telegram community.. to get you start on working.. but just keep this document and this entire thing in mind...
9
+
currently though, you can still contribute to the repository, if you plan to do so...
13
10
11
+
but just keep in mind that, while doing so, you will feel like everything is behind you,
12
+
and fighting against you.. and this will slow you down significantly.. expect, a less streamline process and also expect some of your time being wasted..
13
+
14
+
but, I will try my best to help as much as possible, on our telegram community.. to get you start on working.. but just keep this document and this entire thing in your mind...
14
15
15
16
## Steps Required To Cordinate Open Contributing...
16
17
17
-
-[X] Obviously, Idea!! (Aug 1, 2024)
18
+
Passcodes project has to go though this process to be ready for open source & for community contribution.
-[ ] Plan for Google Developer Verification, i mean we will discuss about it. (in december how manage or cordinate with it)
42
47
@@ -46,12 +51,13 @@ Besides, it help cordinate the contribution process.... Also, we aim to provide
46
51
47
52
### Semi Open To Contribute (start of jan 2026)
48
53
49
-
> [!IMPORTANT]
50
-
> The Organisation is from this point, open to receive any contribution from any potential contributors..
51
-
>
52
-
> The reason, it is not fully open to contributing is solely because of this developer verification thing... the thing is I don't want anyone to waste there time contributing to this repository.. because, I might end up not make verification due to some or other reason... and this might result in waste of other developer waste of there valuable time.. because without verification the application might not be release as google wouldn't allow it to install on android devices....
53
-
>
54
-
> Other then this, or If this thing doesn't impact you in anyway then you count the repository as fuly open to contribute but just have note of it..
54
+
!!! Warning
55
+
56
+
The Organisation is from this point, open to receive any contribution from any potential contributors..
57
+
58
+
The reason, it is not fully open to contributing is solely because of this developer verification thing... the thing is I don't want anyone to waste there time contributing to this repository.. because, I might end up not make verification due to some or other reason... and this might result in waste of other developer's valuable time.. because without verification the application might not be release as google wouldn't allow it to install on android devices....
59
+
60
+
Other then this, or If this thing doesn't impact you in anyway then you count the repository as fuly open to contribute but just have a note of it..
55
61
56
62
-[ ] Find Contributor, Also Review & Update The Contribution Workflow & Get Feedback. (end mar 2026)
57
63
@@ -61,9 +67,8 @@ Besides, it help cordinate the contribution process.... Also, we aim to provide
61
67
62
68
---
63
69
64
-
### Open To Contribution
70
+
### 😊😊 Open To Contribution 😊😊
71
+
72
+
Further improvements to contributing workflow will be driven by feedback and contributor's input...
65
73
66
-
> [!NOTE]
67
-
> Further improvements to contributing workflow will driven by feedback and contributor input...
68
-
>
69
-
> As cordinating contribution is a contiguous process and not a task that can not be done...
74
+
As cordinating contribution is a contiguous process and not a task that can not be done...
This is yanked release.. cuz, I forget to update version name in hurry of releasing a new version.
69
+
70
+
Don't use this release (v1.2.0) in any case.... always prefer that release (v1.2.1) over this... because it will create confusion in bug reports like if you use this release and a bug occur... you will not be able to tell whether you are on previous release (v1.1.2) or this release (v1.2.0)... due to same version number in two different release....
71
+
72
+
### Added
73
+
74
+
#### Preview Features
75
+
76
+
-**Jetpack Compose (Preview Feature)**: made a jetpack compose UI that can be used for basic operation. [[@JeelDobariya38]](https://github.com/JeelDobariya38)
77
+
78
+
### Fixed
79
+
80
+
-**Mimetypes For Import Passwords**: fixed csv mimetypes for importing passswords feature for better experience with android file picker.. [[@JeelDobariya38]](https://github.com/JeelDobariya38)
Copy file name to clipboardExpand all lines: docs/user-docs/release-notes.md
+51Lines changed: 51 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,6 +21,57 @@ This release notes are more or less end-user oriented.
21
21
22
22
---
23
23
24
+
## v1.2.1 - Alpha (Jan 31, 2026)
25
+
26
+
```
27
+
Pacakage Name = "com.jeeldobariya.passcodes"
28
+
Min Android = 8.0 (API level 26)
29
+
Max Android = 14 (API level 34)
30
+
Version Code = 4
31
+
Version Name = "v1.2.1-Alpha"
32
+
Master Database Version = "v1"
33
+
```
34
+
35
+
**`TL;DR`: Fix my mistake, by updating the version name that I forget last time....**
36
+
37
+
- Last time (v1.2.0), I forget to update the version so fix it and re-release instantly... (gotta a real-idea of how dangerous "publish" button on github is.... 😂😂😂😂😂)
This is an [yanked release](installing/#explicitly-yanked-release-pure-trash) and should not be used by any user.
57
+
The soley purpose of this release is, just for documenation & serves as a part of project's story...
58
+
59
+
This release is yanked cuz, I launch the app in hurry and forget to do something that need to be done... (forget to update version number)...
60
+
Checkout the release on github for full details...
61
+
62
+
Don't use this release (v1.2.0) in any case.... always prefer that release (v1.2.1) over this... because it will create confusion in bug reports like if you use this release and a bug occur... you will not be able to tell whether you are on previous release (v1.1.2) or this release (v1.2.0)... due to same version number in two different release....
63
+
64
+
**`TL;DR`: Design a new jetpack compose preview ui.. | Improved performance...**
65
+
66
+
- App now has a basic new preview.. jetpack compose ui... that can be used instead of old ui...
67
+
- App provide a toggle to switch between two layouts...
68
+
- Improve file selection menu experience while importing passwords..
69
+
- Perfomance optimization. (due to dependency updates.)
0 commit comments